I then did another Factory Reset and ran the app again. I tried out your suggestion of doing a Factory Reset on the device and it seems to work but not quite as I expected.įirstly, I was a bit worried that doing a Factory Reset would set my altered memory settings back to their original values, however, the Factory Reset didn't touch the memory setting (Hooray!!).Īnyway, the first time I tried running the app after the Factory Reset it worked. I have asked around on the Microsoft MSDN forums about this but the only person who's responded has said that, as far as he has been able to determine, there's no way to force the emulator to do a 'Cold Boot' each time its run (other than switching between VS2019 and VS2017). However, there is no 'wipe user data' option available on this page nor is there, as far as I can see, any other option for forcing a 'Cold Boot' each time the emulator is run. This displays the edit page as shown below: The only way I can alter the settings for the chosen device is to hit the 'Edit' button. The Android Device Manager displays each of the 'emulator' devices available to me, as in this screenshot (The entry highlighted shows the 'device' I've been using for testing): It does have an 'Android Device Manager' option as shown in the following screenshot: First off, my edition of VS2019 doesn't have a 'google emulator manager' in the Tools menu. Is anyone else experiencing the same or similar problems.Īny help/advice would be gratefully received. This situation, for me at least, makes Xamarin development virtually unusable. I also tried uninstalling the app from the emulator before finishing the debugging session but this made no difference to succeeding debug attempts - the emulator still just hung. There is, apparently, no way to force the emulator to do a 'Cold Boot' each time it runs other than switching between VS2017 and VS2019. After it does this the emulator just hangs. However, on all succeeding debug attempts with the same version of VS the emulator doesn't do a 'Cold Boot' but 'restores state' from, I presume, the previous session. When it does a 'Cold Boot' my app is successfully deployed and run in the emulator. I tried switching between VS2017 and VS2019 and found that when I try to debug my app for the first time from either VS2017 or VS2019 the emulator does a 'Cold Boot'. This time the emulator just 'hung' during the deployment process. Further to my last question where VS2019 failed to deploy my Xamarin Forms app to the Android emulator due to 'lack of space', I increased the 'memory' in the emulator settings and tried again.
0 kommentar(er)
