Firebase Release Monitoring Not Updating for Android in .NET MAUI (net9.0)

Question

Hello,

I am working on a .NET MAUI (net9.0) project.

For Android, I am using the following NuGet packages:

<ItemGroup Condition="'$(TargetFramework)' == 'net9.0-android'">
	  <PackageReference Include="Plugin.Maui.CurrentActivity" Version="1.0.0.61" />
	    <PackageReference Include="Xamarin.AndroidX.Fragment.Ktx" Version="1.8.2" />
	    <PackageReference Include="Xamarin.AndroidX.Activity" Version="1.9.1" />
	    <PackageReference Include="Xamarin.AndroidX.Activity.Ktx" Version="1.9.1" />
		<PackageReference Include="Plugin.Firebase" Version="3.0.0" />
		<PackageReference Include="Plugin.Firebase.Crashlytics" Version="3.0.0" />
	</ItemGroup>

For iOS, I am using:

	<ItemGroup Condition="'$(TargetFramework)' == 'net9.0-ios'">
	  <PackageReference Include="BTProgressHUD" Version="2.1.1" />
	  <PackageReference Include="AdamE.Firebase.iOS.Analytics" Version="11.8.0" />
	  <PackageReference Include="AdamE.Firebase.iOS.CloudMessaging" Version="11.8.0" />
	  <PackageReference Include="AdamE.Firebase.iOS.Core" Version="11.8.0" />
	  <PackageReference Include="AdamE.Firebase.iOS.Crashlytics" Version="11.8.0" />
	</ItemGroup>

Issue

• Firebase Release Monitoring is working correctly for iOS.
• However, for Android, new releases are not appearing in Firebase Release Monitoring.
• Crash reporting also does not seem to reflect updated release versions.
• I have attached a screenshot for reference.

Question

Is there any additional configuration required for Android in .NET MAUI (net9.0) to enable Firebase Release Monitoring properly?

Any guidance would be greatly appreciated.

Thanks in advance

Answer 1

Hi @nandu kathmandi ,

Thanks for reaching out.

I would recommend verifying on the Android side of your .NET MAUI (net9.0) project:

• The google-services.json file not included properly
• ApplicationVersion not incremented
• Package name mismatch
• Testing only Debug builds
• ProGuard/R8 stripping Firebase classes

1. Ensure google-services.json is properly configured

For Android, Firebase relies on the google-services.json file being correctly included in the project:

• Place the file under: Platforms/Android/google-services.json
• Include it in your .csproj:

<ItemGroup Condition="'$(TargetFramework)' == 'net9.0-android'">
  <GoogleServicesJson Include="Platforms\Android\google-services.json" />
</ItemGroup>

2. Verify version tracking configuration

Firebase Release Monitoring depends on Android’s versionCode and versionName. In your .csproj, make sure these are set and incremented with every release:

<PropertyGroup Condition="'$(TargetFramework)' == 'net9.0-android'">
  <ApplicationVersion>42</ApplicationVersion>
  <ApplicationDisplayVersion>2.3.0</ApplicationDisplayVersion>
</PropertyGroup>

• ApplicationVersion -> maps to versionCode
• ApplicationDisplayVersion -> maps to versionName

Firebase uses these values to track different versions of your app. Each time you publish a new build, these values need to change so Firebase can distinguish releases.

3. Confirm Firebase initialization in MauiProgram.cs

When using Plugin.Firebase, explicit initialization is required on Android. For example:

#if ANDROID
builder.UseFirebaseApp();
builder.UseFirebaseCrashlytics();
#endif

4. Verify AndroidManifest package name

In Platforms/Android/AndroidManifest.xml, ensure your package name exactly matches:

• The package registered in Firebase Console
• The package in google-services.json

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
          package="com.yourcompany.yourapp">

Any mismatch will prevent Firebase from associating crash reports and releases correctly.

5. Test using a signed Release build

Firebase Release Monitoring typically tracks Release builds, not Debug builds. Build and test using:

dotnet build -c Release -f net9.0-android

Or publish a signed AAB/APK. Debug builds often do not report version information correctly, which could explain missing releases in Firebase.

6. Check ProGuard/R8 configuration (if using code shrinking)

If code linking or shrinking is enabled, Firebase classes might get removed. Add a Platforms/Android/proguard.cfg file:

-keep class com.google.firebase.** { *; }
-keep class com.google.android.gms.** { *; }
-dontwarn com.google.firebase.**
-dontwarn com.google.android.gms.**

And reference it in your .csproj:

<PropertyGroup Condition="'$(Configuration)|$(TargetFramework)' == 'Release|net9.0-android'">
  <AndroidLinkMode>SdkOnly</AndroidLinkMode>
  <AndroidEnableProguard>true</AndroidEnableProguard>
  <ProguardConfiguration>Platforms\Android\proguard.cfg</ProguardConfiguration>
</PropertyGroup>

7. Package consistency

Ensure all Plugin.Firebase packages are compatible and aligned. In your case, both Plugin.Firebase and Plugin.Firebase.Crashlytics are at version 3.0.0, which is correct. For reference, the Plugin.Firebase GitHub provides platform-specific setup instructions.

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

Answer 2

To troubleshoot the issue with Firebase Release Monitoring not updating for Android in your .NET MAUI (net9.0) project, consider the following steps:

1. Ensure Proper Initialization: Make sure that Firebase is properly initialized in your Android project. This typically involves calling FirebaseApp.InitializeApp(context) in your MainActivity.
2. Check Dependencies: Verify that all required Firebase dependencies are included and correctly configured in your project. Ensure that the versions of the Firebase packages you are using are compatible with each other and with .NET MAUI.
3. ProGuard/R8 Configuration: If you are using ProGuard or R8 for code shrinking, ensure that you have the necessary rules to keep Firebase classes. This can prevent Firebase from functioning correctly if certain classes are removed during the build process.
4. Manifest Configuration: Ensure that your AndroidManifest.xml is correctly configured with the necessary permissions and metadata for Firebase. This includes the google-services.json file being placed in the correct directory and referenced properly.
5. Testing on Real Device: Sometimes, Firebase features may not work as expected on emulators. Test your application on a real device to see if the issue persists.
6. Check Logs: Use logcat to check for any errors or warnings related to Firebase when you run your application. This can provide insights into what might be going wrong.
7. Firebase Console: Ensure that your Firebase project is set up correctly in the Firebase Console, and that you are looking at the correct project and app.

If you have followed these steps and the issue persists, consider checking the official documentation for any additional configuration steps specific to the Firebase packages you are using.

---

References:

• What's new in .NET MAUI for .NET 9