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

I had the same with .NET Android (MonoGame, not MAUI) and what solved it for me is:

<AndroidEnableMarshalMethods>false</AndroidEnableMarshalMethods>

By the way, you don't have to publish to Google Play every time to reproduce the issue: just make a clean local Release build and it fails with exactly the same error.

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:

1. 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>

2. Make sure your build includes the correct ABIs (arm64-v8a, armeabi-v7a) under Android package settings.
3. 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.

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:

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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:

• Android emulator troubleshooting
• What's new in .NET MAUI for .NET 10