Hope this post was helpful for you! As usual if you have any comments leave it here or hit me on Twitter Other post you will like! Remember to use adb logcat to check the issue and make sure you are targeting the correct version of Android. You can also set it from right click on project > Options > General > Target framework > Select your framework. Fixing the issueĪndroidUseLatestPlatformSdk was set to true which was forcing the app to look for the latest sdk and the latest sdk I installed was 24!Īfter setting it to false all went well again. t 500 would take the last 500 lines and *:E would filter the log with a priority of E: Error. If you want to do that, you can use the following command: adb logcat -t 500 *:E > logs.txt It’s always useful to be able to output the logs to a text file. The problem was that my VM was running API 23, the app was configured to target API 23 but somehow, when the app ran it was looking for API 24 which caused it to crash.
It was that it couldn’t find ApiLevel_24 but my manifest was configured as followed: After inspecting the logs, I saw the following error message: AndroidRuntime: : Unable to get provider mono.MonoRuntimeProvider: : Unable to find application _24 or ! I wasn’t sure what was going on until I remembered that I could access the logs via adb logcat.
I looked online and all I found was answers which recommended to uninstall the app either through the Android settings or using adb uninstall, clean and rebuild but My application kept closing instantely after being deployed showing the following error: Unfortunately, has stopped. Last week I had an issue suddenly after updating Xamarin.Android and downloading the latest Android sdk 24. Xamarin.Android app instantly closing with error after deployment