[Contribution] [iOS] Firebase Crashlytics

[vhugogarcia]

Firebase Crashlytics is a lightweight, realtime crash reporter that helps you track, prioritize, and fix stability issues that erode our app quality.

Progress made: I have been able to create a new XCode project called: MauiFirebaseCrashlytics, then I created the binding and updated the sample application.

I'm facing the following issues:

• On iOS, the SDK is not starting up correctly, I keep getting the following error message:

  Crashlytics could not find the symbol for the app's main function and cannot start up. This can be resolved 2 ways depending on your setup:
  1. If you have Exported Symbols File set in your Build Settings, add "__mh_execute_header" as a newline in your Exported Symbols File.
  2. If you have -exported_symbols_list in your linker flags, remove it.

• When trying to debug on a physical device (iOS), I get the following error:

  Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_FirebaseCrashlytics", referenced from:
      objc-class-ref in registrar.o
  ld: symbol(s) not found for architecture arm64

For the first error, I following these recommendations from our friend @rolfbjarne https://github.com/xamarin/xamarin-macios/issues/19157#issuecomment-1798534439 by adding the <_ExportSymbolsExplicitly>false</_ExportSymbolsExplicitly> without luck.

I committed my changes to a branch on my fork, once I finish the implementation and do some code clean up, I will be happy to create a PR: https://github.com/vhugogarcia/DotNet.Platform.SlimBindings/tree/firebase-crashlytics

@Redth @aritchie do you have any insight about the issues, I'm facing? 😃

Thanks in advance

[aritchie]

Hi @vhugogarcia - crashlytics has many issues beyond just the binding. .NET stack traces are awful on firebase because it simply wasn't designed for them.

If you choose to continue the binding because it works for you, that's absolutely fine.

There are a few things I see in your native project that don't follow what we're working with. We aren't using the xcframeworks directly. We're using swift package manager which pulls in all the native stuff we need. We also remove anything specific to analytics and linked that in our binding.

[vhugogarcia]

Thanks @aritchie for the feedback! I noticed the XCode project has been merged into a Single project. So, I will update my GitHub fork and start from zero again.

I hope I can get it working soon with slim bindings 😎👍🏻.

[PavloLukianets]

@vhugogarcia did u manage to get it working? I did all the slim bindings part in our other separate project with no problems, however after uploading the dSYMS i still see no crashes, nor fatal errors.

.NET stack traces are awful on firebase because it simply wasn't designed for them.

BTW @aritchie what do u recommend as AppCenter crashlytics substitute? All the Azure stuff that Microsoft recommends or something else like Sentry?

[aritchie]

@PavloLukianets use Sentry

[vhugogarcia]

@PavloLukianets a couple of weeks ago I created an article explaining the differences and why it is recommended Sentry. https://dev.to/vhugogarcia/mastering-error-insights-in-net-maui-sentry-vs-firebase-crashlytics-5aj3 I hope you find it useful.

😎👍