This way you always will have a fresh, empty and clean android emulator image.Īn example workflow (Best if you keep it separated workflow, and add it to your own workflow’s run_before):.
I’ve created an environment variable ANDROID_EMULATOR_NAME set it’s value to cachedEmulator and I used it in all the steps, to be easy to change emulator name later on. 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.
I tried to install the Emulator in this VM but, as you said, it doesn't work.For now it seems like, the new avdmanager breaks this how-to. This is not an issue for students that have already upgraded to Catalina/BigSur, as they have more powerful macs where they can run a HighSierra VM I setup to them to run Scratch 1.4. Upgrading to BigSur is not an option to them, as the other app they need to use for their test is Scratch 1.4, a 32bits app. My fear is that, when the exams will get closer, many more students will raise the same problem. I don't know much about HighSierra and Mojave, except for one single student unable to install it.
The Emulator runs fine on Windows 10 and on macs running Catalina and BigSur. During tests students are not allowed to use their smartphones, so the Companion is not an option. However, during this lockdown year, tests are remote so that students have to use their computers at home. The standard setup is the offline AI2Live with the Emulator running on Windows PCs in a lab. My students for their tests have to develop (simple) App Inventor projects. What is the reason behind this really non-standard setup?