UnsatisfiedLinkError in Android 8.0

I received quite a number of crash reported in my Xamarin.Android app reported in Play Console with the following stack trace:

java.lang.UnsatisfiedLinkError

at mono.android.Runtime.register (Native Method)

at md5dd7a5194eb3bf67181b6a5c267c0f7e7.PushNotificationMessagingService. (PushNotificationMessagingService.java:15)

at java.lang.Class.newInstance (Native Method)

at android.app.ActivityThread.handleCreateService (ActivityThread.java:3470)

at android.app.ActivityThread.-wrap4 (Unknown Source)

at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1748)

at android.os.Handler.dispatchMessage (Handler.java:108)

at android.os.Looper.loop (Looper.java:206)

at android.app.ActivityThread.main (ActivityThread.java:6733)

at java.lang.reflect.Method.invoke (Native Method)

at com.android.internal.os.Zygote$MethodAndArgsCaller.run (Zygote.java:240)

at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:845)

I have no idea what crashed. The only thing it point to is the push notification services in the app with no additional information. They happen on Android 8.0 and above devices only. Android 8.0 above doesn’t required any special permission to receive notification. No similar crash reported in App Center (I use App Center as my crash reporting tool). Search online doesn’t return me anything meaningful. So I just ignore the error since no user complain anything to me.

Then today I found out that Android 8.0 and above required channel id when showing notification else it will crash in the background. Oh, snap, this is the problem! If you have simiar crash stack trace, this is probably the answer: https://blog.xamarin.com/android-oreo-notification-channels/

Ooiks's Blog

The blog where I share my thoughts, knowledges and experiences with the world

UnsatisfiedLinkError in Android 8.0

Leave a Reply Cancel reply

Share this:

Like this:

Related

Leave a Reply Cancel reply