Firebase Crashlytics not reporting crashes in .NET 10 MAUI application and startup crash with iOS linker settings

Vignesh Palthurai 50 Reputation points
2026-09-18T10:37:20.3933333+00:00

Hello @Nancy Vo (WICLOUD CORPORATION) ,

I am facing an issue while integrating Firebase Crashlytics into a .NET 10 / .NET MAUI 10 application using Plugin.Firebase 4.0.0.

Background

I successfully configured Firebase Crashlytics in one .NET MAUI application using the same configuration, and crash reports are being received correctly in the Firebase Crashlytics dashboard.

However, when I apply the same configuration to another MAUI application that uses a different Firebase project, Crashlytics does not receive the crash reports.

Configuration verified

For the second application, I have verified the following:

  • The application has a unique ApplicationId / iOS Bundle ID.

The correct GoogleService-Info.plist from the second Firebase project is included.

GoogleService-Info.plist is configured as a BundleResource.

The plist contains the required <Link>GoogleService-Info.plist</Link> configuration.

CrossFirebase.Initialize(CreateCrossFirebaseSettings()) is called from WillFinishLaunching.

Crashlytics collection is enabled.

The application has been cleaned and rebuilt.

Firebase Crashlytics currently shows:

“App detected. Waiting for a crash to happen.”

According to the recommended configuration, I added the following to the .csproj:

<PropertyGroup Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'ios'">
  <_ExportSymbolsExplicitly>false</_ExportSymbolsExplicitly>
</PropertyGroup>

<ItemGroup Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'ios'">
  <_ReferencesLinkerFlags Include="-u __mh_execute_header" />
</ItemGroup>

There is an additional important observation regarding this issue:

When running the application in Debug mode, the application launches and runs successfully even with these linker settings.

However, when I create an IPA with the same linker configuration and install/run it through BrowserStack, the application crashes during startup.

The application crashes before I can reach the application UI, so I cannot reproduce the issue from within the application or capture the exception through normal application logging.

Because the crash occurs in the IPA/Release scenario, I currently do not have the actual exception or stack trace from the application.

When I remove the two linker configuration sections, the IPA launches successfully, but Firebase Crashlytics still remains in the state “App detected. Waiting for a crash to happen.”

This makes the issue particularly difficult to diagnose because Debug works, while the IPA/Release build crashes only when these linker settings are enabled.

Questions

Could you please help investigate the following?

  1. Why do the _ExportSymbolsExplicitly and _ReferencesLinkerFlags settings cause a startup crash specifically in the IPA/Release build?
  2. Why does the application run successfully in Debug mode with these settings but crash when the IPA is created and executed through BrowserStack?
  3. Are these linker settings still required for .NET 10 / MAUI 10 with Plugin.Firebase 4.0.0?
  4. Is there an alternative configuration for iOS that allows Firebase Crashlytics to work without adding these linker settings?
  5. Could this be related to changes in the .NET 10 / MAUI 10 iOS linker/trimmer/AOT build process?
  6. Since the IPA crashes during startup before I can capture an application-level exception, could you please advise how I can obtain the native iOS crash log or linker/AOT diagnostic information needed to identify the root cause?

The main issue is:

Without the linker settings: the application launches successfully, but Firebase Crashlytics does not receive crashes.

With the linker settings: Debug works, but the IPA/Release build crashes during startup when executed through BrowserStack, preventing me from obtaining the application exception.

Could you please advise on the correct configuration for .NET 10 / MAUI 10 + Plugin.Firebase 4.0.0 + Firebase Crashlytics on iOS?

Thank you.

Developer technologies | .NET | .NET Multi-platform App UI
0 comments

1 answer

Sort by: Oldest
Most helpful Newest Oldest
  1. Nguyen Dam (WICLOUD CORPORATION) 405 Reputation points Microsoft External Staff Moderator
    2026-09-18T10:43:29.4+00:00

    Thank you for reaching out. We are currently looking into this issue and will follow up once we have more information. Since the startup crash occurs on a BrowserStack iOS device, you can obtain the native iOS crash report directly from the affected BrowserStack session:

    1. Open the BrowserStack App Live dashboard and start a session using the affected IPA on a real iOS device.
    2. Reproduce the startup crash during that session.
    3. On the App Live vertical toolbar, select iOS Settings.
    4. Under Crash Logs, select Fetch logs.
    5. BrowserStack will download the crash logs as a ZIP file. Please share the .ips crash report contained in that ZIP, particularly the sections showing the Exception Type, Termination Reason, and crashed thread.

    If the IPA is being run through an automated Appium or App Automate session instead, open the affected session in the BrowserStack dashboard, select the Crash Logs tab, and then select View raw logs or Download logs.

    Please also share the exact command or process used to generate the IPA, along with the .NET SDK, .NET MAUI workload, Xcode, and macOS versions. This information will help us determine whether the crash originates from Crashlytics initialization or the Release linker/AOT configuration.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.