Firebase Crashlytics on iOS devices cannot communicate (not integrated)

[firdiansyah26]

Hello everyone, I'm having a problem installing the @react-native-firebase/crashlytics module on my iOS device. I have added GoogleService-Info.plist (Figure 1) along with the configuration in the AppDelegate.m (Figure 2) and Podfile (Figure 3) files. But on the Firebase Crashlytics web there is still loading continuously without any error messages (figure 4), and firebase.json (figure 5), any solution? (I'm using objective-c)

Thank You

Detail
Figure 1 (GoogleService-Info.plist)

Figure 2 (AppDelegate.m)

Figure 3 (Podfile)

Figure 4 (Firebase Crashlytics UI web)

Figure 5 (Firebase.json)

[mikehardy]

This is very frustrating yes! If I remember correctly this happens when you are doing crashlytics without analytics. I might be wrong, but I think if you do create a test screen with a button that calls the crash function, then restart the app (that's when it actually sends it! the next time it runs is the first chance it gets...) then wait a bit, it should show up. If it is a debug build you will also need to to make sure your firebase.json has the right stuff: #3879 (comment)

If you do all that...you should get past this screen and see a crash in the console. If nothing else works you might temporarily try installing the analytics package as well

I am sorry I can't locate the upstream issue where this is discussed so I do not have a great pointer on it with hard facts, but if I am right that it is just an interaction with crashlytics and analytics hopefully a test crash gets you past it so the above helps

[firdiansyah26]

I've implemented Firebase Analytics but it's still the same ._.

[mikehardy]

@firdiansyah26 did you do a test crash and make sure it would upload?

[firdiansyah26]

@mikehardy yes, I have used crash tests using crashlytics().crash() from import crashlytics from '@react-native-firebase/crashlytics';, but still nothing has changed

[williamhaley]

First time Crashlytics user with RNFirebase having the same issue. I can't get any crash reports/errors/exceptions to show up in Firebase. I've been trying for several days with no luck. I generated an Ad-Hoc .ipa archive with the Release configuration and am purposefully triggering crashes with...

crashlytics().recordError(new Error('test'));
crashlytics().crash();

...but nothing ever appears in the Crashlytics console in Firebase. I had followed the rnfirebase app and rnfirebase crashlytics setup guides, tried using the simulator + a physical device with the Release config, explicitly killed the app to make sure it's not attached to the debugger [source], setting DWARF with dSYM File [source], nothing seems to work in all my troubleshooting. I can't see anything in the Crashlytics dashboard aside from the infinite, "Add the SDK, then build, run, and crash your app", loading indicator. The console never advances beyond that.

Even with the release build I have the following firebase.json in case that knocks something loose, but no joy.

{
  "react-native": {
    "crashlytics_debug_enabled": true
  }
}

The library seems to be installed properly. The AppDelegate [FIRApp configure]; seems to work, and I'm able to use the Crashlytics API in React Native without any runtime issues. I feel like I'm missing something basic, but it's unfortunately been driving me bonkers in the mean time.

[firdiansyah26]

Hi @williamhaley, yes, I feel it, easy to implement on Android but not on iOS, I've tried uninstalling the bundler package in the firebase console, and restarting the installation following the existing document, but nothing happened, the console crashlytics still shows loading. Is your iOS app running Firebase Crashlytics successfully now?

[williamhaley]

Unfortunately not @firdiansyah26. I'm still in the midst of trying to get it to work. The next thing I plan to try is simply working with a generic iOS Crashlytics setup and triggering a crash directly from Objective-C. My hope/thinking is that I can 1) verify I can get anything to work with Crashlytics in a more vanilla form and 2) maybe if that succeeds, subsequent RNFirebase errors will start getting logged.

[firdiansyah26]

Thank you for sharing @williamhaley, I also plan to ask the iOS developer this, hoping to get input on this issue, good luck!.

[mikehardy]

I'm sorry I don't have a solid solution on this one, but I'm definitely listening - I have seen what you describe before I just don't recall anyone posting solid steps to get past it. Very interested in the experience after a vanilla iOS implementation - my hunch is there is either something basic we're missing (like perhaps a temporary analytics integration of some sort is necessary but you have to do something specific within the two packages) or that upstream really has an issue. Either way, I'm listening intently and we can document whatever findings result

[williamhaley]

Hmm 🤔 Can you try setting [[FIRCrashlytics crashlytics] setCrashlyticsCollectionEnabled:false]; (false) and triggering a bunch of crashes? Eventually you should see a number of unsent crash reports.

40 unsent reports are available. Checking for upload permission.

That would at least indicate that Crashlytics is properly seeing and collecting crashes locally, even if it's not transmitting them.

I sometimes found it was tricky to trigger a crash appropriately in Debug mode. I had to make sure the debugger was not attached (stop the app in Xcode then launch the app manually).

[mikehardy]

@williamhaley has good advice here to just verify for sure that logging is happening but I think this may be a separate problem related to projects that were on Fabric originally (if I'm following the thread - if that issue is already resolved, sorry)

[firdiansyah26]

still same, maybe you can correction my code *cmiiw

1. AppDelegate.m
   

2. Podfile
   

3. Build Phase
   

4. Scheme
   

5. Test Crash Function
   

6. Firebase Json
   

[williamhaley]

@firdiansyah26 Can you try purposefully crashing your app in AppDelegate.m? Make sure the debugger's detached (press stop) then launch your app manually (just by tapping the icon on your phone) to run and crash it. You can throw this error in the bottom of didFinishLaunchingWithOptions in your AppDelegate.m.

// This is the same type of exception that gets thrown in JS by calls to crashlytics().crash();
@throw NSInternalInconsistencyException;

Also, I find that these log messages are most helpful. Do you ever see these?

2020-09-13 22:49:32.101200-0500 THEAPP[4057:573254] 6.30.0 - [Firebase/Crashlytics][I-CLS000000] Automatic data collection is enabled.
2020-09-13 22:49:32.101694-0500 THEAPP[4057:573254] 6.30.0 - [Firebase/Crashlytics][I-CLS000000] Unsent reports will be uploaded at startup

I have a tough time re-creating reliable crashes on my end. It seems like exceptions I throw from Objective-C or Swift show up quickly so at least those are mostly reliable (even though the stack traces seem to take hours to appear at times), but (for reasons unclear or due to lack of understaning on my part) exceptions thrown from JS/React code either never show up or take a long time to populate in the dashboard.

From what I can tell it's no fault of react-native-firebase. Rather, Crashlytics seems to take forever to sometimes show my errors, and their UI seems to be inconsistent as I debug which complicates things. I have to admit, although it's nice to have everything in one spot with Firebase + Crashlytics, I'm probably going to move to Bugsnag. I've used them in the past and they have a few features I'm missing. Good luck!

[firdiansyah26]

Hi @williamhaley, yes I saw a message in the console, I also repeated the steps in the documentation and applied it to a new project, but it's the same, loading is still running which indicates the integration has not been successful. Maybe for iOS it will be like now and I will ask another discussion forum regarding this matter, hopefully there are suggestions for this problem. Thank you for your help sir!

[mikehardy]

These are very recent APIs, note that we support them as of recently as well: #4009

But it's supposed to be enabled with this: { "react-native": { "crashlytics_disable_auto_disabler": true, "crashlytics_debug_enabled": true } } from the linked comment above

Perhaps things moved yet again with regard to defaults

It is still a pending work item for me to have crashlytics turned on by default in debug and release so it works out of the box, and then document how to disable it, as opposed to this current state where you have to turn on like 3 toggles to get debug crashes to upload.

That has not gotten done in weeks though, so if you're still in there and you know where the settings are in our code, if you could do a PR to have iOS log crashes by default, in debug too, that would clearly help a lot of people 🙏

[williamhaley]

Will do! I've been digging into the source and learning a lot about RNFirebase. I'll post my notes when I have something conclusive or am ready to get a PR together.

[williamhaley]

See #4236 where I think I did the appropriate work to get iOS crash collection enabled by default. I actually hadn't previously seen crashlytics_disable_auto_disabler until you mentioned it here. I wasn't sure what I was looking for in #4009. Did you mean #3879? I only just found that now (whoops!) and see that a lot of people have already trod on the ground I walked today. Darn, hopefully the work I did is worthwhile based on previous design conversations.

[firdiansyah26]

Case is closed

The configuration in my code is like this

1. package.json
   "@react-native-firebase/crashlytics": "^8.4.1" => "@react-native-firebase/crashlytics": "8.3.0"

2. Podfile
   $FirebaseSDKVersion = '6.30.0'

3. Info.plist
   <key>FirebaseCrashlyticsCollectionEnabled</key> set => <true/>

Thank you for your contribute for this case, @williamhaley @mikehardy