.NET MAUI (.NET 10) Firebase Analytics and Crashlytics not working – Crashlytics build ID is missing

Question

.NET MAUI (.NET 10) Firebase Analytics and Crashlytics not working – Crashlytics build ID is missing

Reka Ravi 5

I am trying to integrate Firebase Analytics and Crashlytics into a .NET MAUI (.NET 10) Android application, but I am facing a runtime exception related to Crashlytics.

Steps I followed:

Created a new .NET MAUI project

Created a Firebase project and added an Android app

Ensured the ApplicationId matches the package name

Added google-services.json to: Platforms/Android/google-services.json

Set Build Action to GoogleServicesJson

Installed the following NuGet packages:

Plugin.Firebase

  Plugin.Firebase.Analytics
  
     Plugin.Firebase.Crashlytics

Configuration:

ApplicationId in .csproj: com.companyname.firebasepocapp

Package name in AndroidManifest.xml: com.companyname.firebasepocapp

Error:

At runtime, I get the following exception:

Java.Lang.RuntimeException: Unable to get provider 
com.google.firebase.provider.FirebaseInitProvider: 
java.lang.IllegalStateException: 
The Crashlytics build ID is missing.

What I have tried:

Verified google-services.json placement and build action

Ensured package names match

Cleaned and rebuilt the solution

Questions:

Is additional Android Gradle configuration required for Crashlytics in .NET MAUI (.NET 10)?

Does Plugin.Firebase fully support Crashlytics for .NET 10?

Is there any required initialization code or setup missing for Analytics and Crashlytics?

Any guidance or working setup example would be helpful.

Environment:

.NET MAUI (.NET 10)

Android target

Visual Studio 2026

Plugin.Firebase (latest available version)

0 comments

1 answer

Your answer

Answer 1

Varsha Dundigalla(INFOSYS LIMITED) 4,785 Microsoft External Staff

Thank you for reaching out.
Crashlytics stops the app from starting because its Android setup is not fully completed when used through Plugin.Firebase.

No extra Android Gradle files need to be added manually like in a native Android app. However, Crashlytics still expects certain Android build information to be available. In a MAUI project, this information is provided only when the plugin’s Android requirements are fully met. If that setup is incomplete, Crashlytics cannot continue during app startup.

Plugin.Firebase works with .NET 10, but it is a third‑party library and does not work automatically. Crashlytics support depends on following all Android‑specific setup steps required by the plugin. When those steps are missed, the app stops during launch.

Adding google-services.json alone is not enough. Crashlytics needs additional Android configuration that happens at build time, before any application code runs. That is why adding or changing C# code does not help in this situation.

Once all Android configuration required by Plugin.Firebase for Crashlytics is completed, Crashlytics initializes correctly and the app starts normally.

In summary, this behavior happens due to incomplete Firebase Crashlytics configuration through Plugin.Firebase on Android and completing the plugin’s required setup resolves it.

Please let us know if you require any further assistance, we’re happy to help. If you found this information useful, kindly mark this as "Accept Answer". So that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

Reka Ravi 5 Reputation points

2026-04-06T07:40:55.45+00:00

Thank you for your response.

I understand that the issue is caused by incomplete Android configuration for Firebase Crashlytics when using Plugin.Firebase in a .NET MAUI project. However, the current explanation is still quite general and does not clearly describe the exact steps required.

Could you please provide a detailed, step-by-step guide for properly configuring Firebase Crashlytics on Android when using Plugin.Firebase with .NET MAUI?

Specifically, I would appreciate clarification on:

What exact Android build configurations are required beyond adding google-services.json

Whether any Gradle properties, build targets, or MSBuild settings must be defined in the MAUI project

If any additional metadata, permissions, or manifest changes are required in AndroidManifest.xml

How Crashlytics initialization is triggered during build/runtime in this setup

Any required versions or compatibility constraints between Plugin.Firebase, .NET (e.g., .NET 8/10), and Firebase services

A minimal working example or official sample project demonstrating a correct setup

Right now, it is unclear what specific configuration is missing, and without concrete steps it is difficult to resolve the issue.

A precise checklist or documentation reference would be very helpful.

Thank you for your support.
Varsha Dundigalla(INFOSYS LIMITED) 4,785 Reputation points Microsoft External Staff

2026-04-07T09:54:27.6433333+00:00
Thank you for reaching out.

In this setup, the behavior happens because Firebase Crashlytics depends on a build‑time step that creates a build ID. In a native Android project, this build ID is generated automatically by the Firebase Gradle plugin during the build. In a .NET MAUI Android project, the build system is different. MAUI uses MSBuild instead of Gradle, so the Firebase Gradle plugin is not executed in the same way.

Because of that difference, the build‑time step that generates the Crashlytics build ID may not run. When Crashlytics starts during app launch and does not find that build ID, it stops immediately, which leads to the startup failure you are seeing.

To make Crashlytics work in a MAUI Android project using Plugin.Firebase, additional configuration is required beyond just adding google-services.json. The Firebase configuration file must be placed correctly, but that alone is not sufficient. Crashlytics also relies on Android‑specific resources and build‑time metadata that are normally produced by Gradle. Plugin.Firebase tries to bridge this gap, but it cannot fully reproduce native Android behavior in all cases.

Because of this limitation, correct configuration is required, and even then, some scenarios—especially with newer frameworks like .NET 10 may still show this behavior. This is a known limitation when using Crashlytics outside a native Gradle‑based Android build.

There is no single end‑to‑end official document that covers Firebase Crashlytics setup specifically for .NET MAUI. The correct setup is based on combining the following references:

Plugin.Firebase Crashlytics documentation, which describes the required Android setup and current limitations: https://github.com/TobiasBuchholz/Plugin.Firebase/blob/development/docs/crashlytics.md The Plugin.Firebase GitHub repository and its sample projects, which are the best working reference for how the plugin expects things to be configured: https://github.com/TobiasBuchholz/Plugin.Firebase

Firebase’s official Crashlytics documentation for Android, which explains the build‑time behavior Crashlytics expects in general: https://firebase.google.com/docs/crashlytics/get-started?platform=android

Together, these sources explain both why the build ID is required and why it may be missing in MAUI projects. Plugin.Firebase provides partial support to enable Crashlytics in MAUI, but it does not guarantee full parity with native Android builds. As a result, careful configuration is needed, and in some environments the limitation may still remain.

If the issue persists even after following all documented configuration steps, there are a couple of practical options to consider. Some teams choose to stay on .NET 8, where Crashlytics behavior with Plugin.Firebase has been observed to be more stable in real‑world usage. Others, especially when Crashlytics is business‑critical, choose to integrate Firebase Crashlytics using native Android tooling instead of a cross‑platform wrapper, so the full Gradle‑based build process runs without these limitations.

In summary, this behavior is caused by a missing build‑time step required by Crashlytics. That step is normally handled by Gradle, which MAUI does not use. Plugin.Firebase helps bridge the gap, but it cannot fully cover all Crashlytics build‑time requirements in every scenario.

Please let us know if you require any further assistance, we’re happy to help. If you found this information useful, kindly mark this as "Accept Answer". So that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

Share via

.NET MAUI (.NET 10) Firebase Analytics and Crashlytics not working – Crashlytics build ID is missing

Steps I followed:

Configuration:

Error:

What I have tried:

Questions:

1 answer

Your answer