MAUI .Net10 app crashing on startup only when installed from Google Play

Question

MAUI .Net10 app crashing on startup only when installed from Google Play

ByteDigger 5

Hi all,

I've just upgraded VS to 2026, which I use to develop mobile MAUI project. That involved targeting .Net 10 (.NET MAUI Tools 18.0.345 (fbde6c01f0)) instead of .Net 9. in the MAUI project.

The Android app works perfectly in debug or release mode when run in an emulator or a device connected to my PC. But if I distribute the application via the Google store and install it on a mobile phone, it will crash on startup (... I briefly see the splash screen).

I see the below error in logcat. I've tried to disable trimming. I've added various console debug statements to MainActivity (... and other places) but nothing's logged, which leads me to believe the app is crashing very early in the launch process.

Has anybody experienced similar issues? How did you go about troubleshooting?

Thanks.

02-03 16:54:45.016 Sony XQ-CC54 Info 23180 MonoDroid java.lang.UnsatisfiedLinkError: No implementation found for void crc6488302ad6e9e4df1a.MauiApplication.n_onCreate() (tried Java_crc6488302ad6e9e4df1a_MauiApplication_n_1onCreate and Java_crc6488302ad6e9e4df1a_MauiApplication_n_1onCreate__) - is the library loaded, e.g. System.loadLibrary?

at crc6488302ad6e9e4df1a.MauiApplication.n_onCreate(Native Method)

at crc6488302ad6e9e4df1a.MauiApplication.onCreate(MauiApplication.java:17)

at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1317)

at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7017)

at android.app.ActivityThread.-$$Nest$mhandleBindApplication(Unknown Source:0)

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

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

at android.os.Looper.loopOnce(Looper.java:205)

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

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

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

at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)

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

Melissa Warrington 6 Reputation points

2026-02-20T15:37:22.1233333+00:00

Hi @ByteDigger I am having the same issue, were you able to resolve this? Thanks in advance.
UBMike 5 Reputation points

2026-02-24T03:03:20.76+00:00

Hi Melissa and all, I was able to move forward somewhat... In a nutshell, after spending a huge amount of time trying to fix this by changing linker and other builder switches (... none of which helped) I stopped troubleshooting, as I had other things to do.

One thing I've noticed a few weeks ago while investigating the issue, was that removing some Nuget packages would make the issue go away. While I could replace most of the Nuget packages with others, one of them was critical for me (Plugin.Firebase.CloudMessaging)...

Anyways, I came back looking into this problem a few days ago and I thought as a first thing to update VS to the vary last build (18.3.1). Then I've re-built my application (with the Firebase nuget deployed), uploaded to the Play store and surprisingly it wouldn't crash any longer.

I then tried to re-add another Nuget that I was using (GitVersion.MsBuild) and after doing so the app started crashing again when downloaded from the appstore. So, for now I won't be using this particular Nuget, although it would be great to figure out why it's causing the problem...

BTW, I've re-enabled all possible linker/optimizers in my project to shrink the binary size again and that doesn't seem to make a difference. The application is still working when downloaded from the Play store.

I hope this help. As a first step I'd suggest to update VS to the latest version. If that doesn't help try to remove Nuget pkgs until you manage to get the application to start up. I know the process is very time intensive but I can't see any other option to figure out the root cause of the problem...
Melissa Warrington 6 Reputation points

2026-02-25T15:24:40.2566667+00:00

Thanks for taking the time to reply @ByteDigger

I managed to get this working by rolling back the version of JetBrains Rider I was using, not an ideal solution but it has allowed me to get a working build of the app onto the Play store for now until I find out what the issue is.

2 answers

Your answer

Melissa Warrington 6 Reputation points

2026-02-20T15:37:22.1233333+00:00

Hi @ByteDigger I am having the same issue, were you able to resolve this? Thanks in advance.
UBMike 5 Reputation points

2026-02-24T03:03:20.76+00:00

Hi Melissa and all, I was able to move forward somewhat... In a nutshell, after spending a huge amount of time trying to fix this by changing linker and other builder switches (... none of which helped) I stopped troubleshooting, as I had other things to do.

One thing I've noticed a few weeks ago while investigating the issue, was that removing some Nuget packages would make the issue go away. While I could replace most of the Nuget packages with others, one of them was critical for me (Plugin.Firebase.CloudMessaging)...

Anyways, I came back looking into this problem a few days ago and I thought as a first thing to update VS to the vary last build (18.3.1). Then I've re-built my application (with the Firebase nuget deployed), uploaded to the Play store and surprisingly it wouldn't crash any longer.

I then tried to re-add another Nuget that I was using (GitVersion.MsBuild) and after doing so the app started crashing again when downloaded from the appstore. So, for now I won't be using this particular Nuget, although it would be great to figure out why it's causing the problem...

BTW, I've re-enabled all possible linker/optimizers in my project to shrink the binary size again and that doesn't seem to make a difference. The application is still working when downloaded from the Play store.

I hope this help. As a first step I'd suggest to update VS to the latest version. If that doesn't help try to remove Nuget pkgs until you manage to get the application to start up. I know the process is very time intensive but I can't see any other option to figure out the root cause of the problem...
Melissa Warrington 6 Reputation points

2026-02-25T15:24:40.2566667+00:00

Thanks for taking the time to reply @ByteDigger

I managed to get this working by rolling back the version of JetBrains Rider I was using, not an ideal solution but it has allowed me to get a working build of the app onto the Play store for now until I find out what the issue is.

Answer 1

Jack Dang (WICLOUD CORPORATION) 14,955 Microsoft External Staff Moderator

Hi @ByteDigger ,

Thanks for reaching out.

It seems the crash may be happening because the app’s native code isn’t being loaded properly in the version distributed via Google Play. The UnsatisfiedLinkError for MauiApplication.n_onCreate() generally indicates that the native library containing that method isn’t present in the packaged APK/AAB.

You could try the following steps to see if they help address the problem:

Set Linker behavior to “Link SDK assemblies only” rather than “Link All” to reduce the chance of critical native code being trimmed.

https://learn.microsoft.com/en-us/dotnet/android/building-apps/build-properties

<PropertyGroup>
  <AndroidLinkMode>SdkOnly</AndroidLinkMode>
</PropertyGroup>

Make sure your build includes the correct ABIs (arm64-v8a, armeabi-v7a) under Android package settings.
Build a Release APK or AAB and install it directly on a device using adb install to see if it launches properly before publishing.

If the issue continues, further investigation of the packaged AAB and native libraries may be needed to pinpoint the exact cause.

Hope this helps! If my answer was helpful - kindly follow the instructions here so others with the same problem can benefit as well.

Melissa Warrington 6 Reputation points

2026-02-22T23:05:57.2733333+00:00

Hi Jack, I am having the same problem as ByteDigger. To identify if it was an issue with my project I created a new .NET 10 MAUI project and tried running it on an emulator and on a physical device but the outcome was the same.

I would appreciate if you could advise where I go from here. I've provided my workloads below. Please let me know if you need anymore information.

Workload version: 10.0.103

Installed Workload Id Manifest Version Installation Source

android 36.1.30/10.0.100 SDK 10.0.100

ios 26.2.10197/10.0.100 SDK 10.0.100

maui 10.0.20/10.0.100 SDK 10.0.100

maui-android 10.0.20/10.0.100 SDK 10.0.100

maui-ios 10.0.20/10.0.100 SDK 10.0.100
Jack Dang (WICLOUD CORPORATION) 14,955 Reputation points Microsoft External Staff Moderator

2026-02-23T08:09:31.1033333+00:00
Hi Melissa Warrington,

At this stage, I would suggest trying the following to narrow it down further:

Repair or reinstall workloads
dotnet workload repair dotnet workload update
This helps rule out any partial or inconsistent MAUI 10 workload installation.

Clear build artifacts completely: Delete the bin and obj folders manually, then rebuild in Release mode.

Disable AOT explicitly (if enabled): In your .csproj, temporarily add:
<RunAOTCompilation>false</RunAOTCompilation>
Then rebuild and test again.

Test the generated AAB locally: Use bundletool to install the AAB locally and verify whether the crash only occurs when installed via Google Play’s split APK mechanism.

If the issue persists after these checks, especially in a clean project, it may indicate a regression in the current .NET 10 MAUI Android tooling. In that case, capturing a minimal repro project and reporting it to the MAUI team would be the next logical step.
AspiringApollo 21 Reputation points

2026-02-24T11:08:53.9133333+00:00

I am also getting this error. However, it is on all release builds, whether created locally or in CI/CD Pipeline. I haven't made any changes to anything, it has just randomly became an issue. Please investigate this issue folks. Any advice would be greatly appreciated.
Melissa Warrington 6 Reputation points

2026-02-25T17:10:51.08+00:00

Are you using JetBrains rider by any chance? I fixed this issue after 3 days of trying to resolve it by downgrading my version to 2025.2.5.
Michael Le (WICLOUD CORPORATION) 11,080 Reputation points Microsoft External Staff Moderator

2026-03-03T09:43:46.1766667+00:00

Hello @ByteDigger ,

It's been a while since we last heard from you. Hope things are going well.

If you're still interested or have any questions, feel free to reach out whenever it works best for you.
UBMike 5 Reputation points

2026-03-03T22:54:30.2433333+00:00

Hi Michael, I didn't realize I had 2 handles... See my reply above on Feb 24th as UBMike. I'll need to figure out how to login as bytedigger again :)

Answer 2

The issue you're encountering with your MAUI .NET 10 app crashing on startup when installed from the Google Play Store, specifically the UnsatisfiedLinkError, suggests that there may be a problem with the native libraries not being loaded correctly. Here are some troubleshooting steps you can consider:

Ensure Native Libraries are Included: Make sure that the native libraries your application depends on are included in the APK. Sometimes, during the build process, certain libraries may not be packaged correctly.
Check for ProGuard/R8 Configuration: If you're using code shrinking (trimming), ensure that your ProGuard or R8 configuration is not stripping out necessary native methods. You might need to add rules to keep the required classes and methods.
Verify Application Permissions: Ensure that your application has the necessary permissions defined in the Android manifest, especially if the library requires specific permissions to function.
Test Different Build Configurations: Since the app works in debug and release modes on an emulator or connected device, try creating a signed APK and testing it on a physical device to replicate the issue.
Check for ABI Compatibility: Make sure that the APK is built for the correct ABI (Application Binary Interface) that matches the device architecture. If the device architecture is not supported, it could lead to crashes.
Logcat Analysis: Since you're not seeing any logs, ensure that you have proper logging enabled and check the logcat output for any other errors or warnings that might give you more context about the crash.
Disable Fast Deployment: If you haven't already, consider disabling Fast Deployment by setting EmbedAssembliesIntoApk = True in your project file. This can help with issues related to native crashes.

If these steps do not resolve the issue, consider filing an issue with detailed logs and information on the MAUI GitHub repository for further assistance.

References:

Share via

MAUI .Net10 app crashing on startup only when installed from Google Play

2 answers

Your answer