With caching it doesn’t matter how long your workflow will run, android emulator’s boot time always will be the same. The workflow in ( How to speed up Android emulator heavy workflows) works very well, but only if your workflow average full build time is more than 4-5 minutes, because then there is enought time in the background for the emulator to be able to boot.
Well, that’s not bad but, let’s try now with some caching! +-+ ( How to speed up Android emulator heavy workflows) It’s result was a great amount of time saved, in my example from the original 581 seconds I’ve managed to successfully decrease it to 432 seconds. The last try to speed up android emulator was making it’s booting happen in the background while other steps can run with it paralell. The two steps Bitrise.io Cache:Pull and Bitrise.io Cache:Push now helps a lot of users to speed up their build times, and caching emulator snapshots seems to be a good idea as it usually takes couple of minutes to boot up an arm Android emulator. Please follow the written below if you are still using emulator as executable to create and use your emulator. For now it seems like, the new avdmanager breaks this how-to.
