Firebase-ios-sdk: Crashlytics for Mac Catalyst

[steipete]

As per https://github.com/firebase/firebase-ios-sdk/issues/3144#issuecomment-540622435 I'm opening a new ticket to request a status update for the availability of Crashlytics for Mac Catalyst.

We have our app in production for a month now (pdfviewer.io), and the absence of a crash reporting service is hurting us. This is more critical to us than any other service. Apple's Crash Reporting also doesn't seem to work, so we're essentially blind, and do not want to move to a different crash service, since iOS and Android are also covered by Crashlytics currently. (if so, we'd move everything to have a unified experience, but I doubt that's necessary since you already publicly committed to shipping a Catalyst SDK)

Happy to help and/or play beta tester for such an SDK (@steipete on Twitter, DMs are open)

Thanks!

[samedson]

Hey @steipete thank you for reaching out! Sorry I was slow to responding here.

I definitely understand the pain here while we work on supporting Catalyst apps. This is vital for shipping apps safely and we're working on it. We really appreciate the excitement and everyone’s patience around this, and we’ll let you know when it’s ready for beta testing / use.

[DanilaVladi]

Would like to join this also with Vectornator. @danilaVladi On Twitter

[benrosen78]

Hi, would love to help test this out in SongShift. @benmrosen on Twitter

[MDittmann]

Would also love to see this working

[appfrilans]

Would love this as well!

[tmm1]

See also https://www.bitbuildr.com/tech-blog/mac-catalyst-porting-an-app-using-crashlytics-firebase

[stevekellogg]

@samedson , I see your reply here from a couple of weeks ago. Thanks for letting us know you're working on it. Will we be able to use Crashlytics App Distribution on Catalyst apps when you folks complete your work?

[gabors]

Would love to see support for Mac catalyst apps added as well as soon as possible.
Same as OP we would prefer keeping working with Crashlytics as our iOS, tvOS and Android app versions have been using this lovely framework for a while.

[carlo-]

Did anyone succeed in using the new FirebaseCrashlytics framework that was just merged? Everything compiles correctly for me, and Crashlytics seems to submit reports without errors, but nothing shows up in the Firebase console (even after several hours). Any ideas?

[samedson]

Hey @carlo-, can you tell us more about how you set it up?

A couple things that may be helpful:

• It's necessary to have the Crashlytics run script set up for catalyst to work: "${PODS_ROOT}/FirebaseCrashlytics/run". If this wasn't in your Xcode project before, try adding it, building, and then incrementing your build version or number (to make sure you get new SDK settings).

• Make sure you're including a new, different GoogleService-info.plist file from your iOS app, and make sure the app has started the onboarding process in the Firebase Crashlytics dashboard. Eg. this is what my Build Phases looks like:

[carlo-]

My setup is configured as you described. When registering the app on Firebase, I've used the bundle id with the maccatalyst. prefix, was that correct?

[samedson]

Yes! Having the maccatalyst prefix is fine (though not required).

A few more suggestions:

• Can you double check that Debug information format is set to "DWARF with dSYM File" in Build Settings?
• Make sure that when you cause a crash, the Xcode debugger isn't attached. Eg. Click Run, click Stop, and then run the app from your phone / simulator home screen
• In addition, can you turn on debug logs by adding -FIRDebugEnabled to the list of run arguments in "Edit Scheme" > Arguments Passed On Launch, and seeing if there's any errors?

If none of these work, try refreshing the page in the Firebase console and seeing if there's any missing dSYMs.

[carlo-]

@samedson thank you for your help! ~Unfortunately I'm already doing all three points as well. According to the Firebase console the dSYMs are not missing, I even tried to upload them manually with the same results.~ Edit: it turns out running the app in the Debug configuration was causing Firebase to ignore the reports 🤦‍♂️in Release everything works fine!

[samedson]

Great! Glad you were able to get up and running.