How to fix Xamarin Android app instantly closing with error after deployment

Xamarin.Android app instantly closing with error after deployment

Last week I had an issue suddenly after updating Xamarin.Android and downloading the latest Android sdk 24.

My application kept closing instantely after being deployed showing the following error:

Unfortunately, [App name] has stopped.

img

I looked online and all I found was answers which recommended to uninstall the app either through the Android settings or using adb uninstall <package name>, clean and rebuild but nothing did it. It was still crashing.

1. Scoping the issue

I wasn’t sure what was going on until I remembered that I could access the logs via adb logcat. After inspecting the logs, I saw the following error message:

AndroidRuntime: java.lang.RuntimeException: Unable to get provider mono.MonoRuntimeProvider: java.lang.RuntimeException: Unable to find application Mono.Android.Platform.ApiLevel_24 or Xamarin.Android.Platform!

It was that it couldn’t find ApiLevel_24 but my manifest was configured as followed:

<uses-sdk android:minSdkVersion="21" android:targetSdkVersion="23" />

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.

Notes:

It’s always useful to be able to output the logs to a text file. If you want to do that, you can use the following command:

adb logcat -t 500 *:E > logs.txt

-t 500 would take the last 500 lines and *:E would filter the log with a priority of E: Error. Finally it will pipe it to a logs.txt.

2. Fixing the issue

The problem was in the csproj file.

AndroidUseLatestPlatformSdk was set to true which was forcing the app to look for the latest sdk and the latest sdk I installed was 24! After setting it to false all went well again.

You can also set it from right click on project > Options > General > Target framework > Select your framework.

menu

Conclusion

Remember to use adb logcat to check the issue and make sure you are targeting the correct version of Android. Hope this post was helpful for you! As usual if you have any comments leave it here or hit me on Twitter @Kimserey_Lam.

Other post you will like!

Comments

  1. Anonymous5 January 2017 at 18:41

    Kimserey, thank you so much for taking the time to blog this. I was having the same issue recently after upgrading my SDK's.

    ReplyDelete
  2. Richard21 September 2017 at 23:12

    Thanks a lot, this happend at my work and no one has idea of whats on going on.

    ReplyDelete
  3. Dan14 January 2018 at 15:12

    I was having the same error as soon as I would launch the app. It worked fine in the emulator, but instantly crashed on my real Android device. For me the fix was to make sure "Shared Runtime" in the Android project properties was not checked, as per this post: https://forums.xamarin.com/discussion/25780/unfortunately-app-name-has-stopped/ Thanks though!

    ReplyDelete

Post a Comment

Popular posts from this blog

Microsoft Orleans logs warnings and errors

Microsoft Orleans logs warnings and errors Microsoft Orleans is a framework which helps building distributed system by implementing the actor model together with the concept of virtual actors, taking care of availability and concurrency. If you are unfamiliar with Microsoft Orleans, you can look at my previous blog post explaining the benefits of Microsoft Orleans . Even though Orleans promises to abstract the distributed system problems, there are instances where errors arise without us being able to understand what is going on. Lucky us, the logs are well documented… but only for those who can decrypt them. Today I will go through some of the errors and warnings which can be seen from silo and client so that you too can undestand what is going on. Enjoy! The code used to produce those errors can be found on my GitHub https://github.com/Kimserey/orleans-cluster-consul . 1. Client logs Logs on client appears with address {ip}:0 . 1.1. Can’t find implementation of interface An un...
Keep reading

A complete SignalR with ASP Net Core example with WSS, Authentication, Nginx

SignalR with ASP Net Core SignalR is a framework from ASP NET Core allowing us to establish a two way communication between client and server. This two way communication allows the client to send messages to the server but more importantly allows the server to push messages to the client. SignalR makes use of Websocket when available else it falls back to SSE or pulling. Today we will focus on how to setup SignalR to work with WSS, Websocket secure and how we can authenticate the user requesting to connect to our SignalR hub via Webscoket. Getting started with SignalR SSL encryption for Websocket Secure WSS Websocket Authentication with Identity Server 4 SignalR behind Nginx 1. Getting started with SignalR The Hubs are the main components of SignalR. It is an abstraction of a two way communication available for both client and server. Public functions from the hub can be called from the server code and can be called from the client. The frontend NPM package @aspnet/signalr ...
Keep reading

SDK-Style project and project.assets.json

SDK-Style project and project.assets.json Last week I encountered an issue with MSBuild while trying to run it from command line. The issue did not appear when using VisualStudio right click + build but only appeared when using msbuild.exe CLI directly with a clean project. Assets file 'C:\[...]\obj\project.assets.json' not found. Run a NuGet package restore to generate this file. When I first saw the error, few questions came to my mind which I will share today in 3 points: Overview of project.assets.json Slim SDK-Style project Mixing SDK-Style project and old projects Special shoutout to @enricosada who provided me with all the answers regarding the SDK-Style project. 1. Overview of project.assets.json project.assets.json lists all the dependencies of the project. It is created in the /obj folder when using dotnet restore or dotnet build as it implicitly calls restore before build, or msbuid.exe /t:restore with msbuild CLI. To simulate dotnet build (re...
Keep reading