I've been hitting the null reference on one of my dev boxes as well. I haven't tried switching language, but I've found that repairing my installation usually fixes it for a while. Unfortunately, fixing it just reveals another problem, which is that the emulator is not internet-connected. In general, I've not been able to use the Android emulator since moving that box to Creators Edition. I don't know whether it's related to that or not, but it's turning into a huge problem for me. There are three failure modes: 1) not starting due to immediate null reference, 2) starting, but without a network connection, and 3) starting, but then printing a fatal message (sorry, I don't have the exact text) that the emulator is unable to determine a network IP address (this one leaves the emulator in the 'OS is starting' state forever). I find myself rotating amongst those three failure modes by repairing my VS2017 installation, and messing with the emulator by adding/removing an externally-connected virtual switch. I have not yet found a way to make the emulator boot up and have an internet connection on this box. I have confirmed that the problem comes back immediately as soon as the emulator is stopped. ![]() As long as it continues to run, VS is able to deploy to it and debug, over and over again. Once it is stopped, VS can no longer start it, but immediately pops up this dialog: and logs this null reference exception instead: 1> Garrys mod not working on osx 2017. Starting deploy 5' KitKat (4.4) XXHDPI Phone. 1>Starting emulator 5' KitKat (4.4) XXHDPI Phone. 1>An error occured. See full exception on logs for more details. The Visual Studio Emulator for Android fits nicely into your existing Android development environment, with APK and file installation that is as simple as dragging and dropping items on the emulator screen. ![]() 1>Object reference not set to an instance of an object. ========== Deploy: 0 succeeded, 1 failed, 0 skipped ========== This makes the Visual Studio Emulator for Android really useless, since it can only be launched once, and never works again until the installation is repaired. Not to mention the misspelling and bad grammar in the log message. BTW, does anyone know where to find the 'full exception on logs for more details' that's mentioned in the above message?
0 Comments
Leave a Reply. |