Add Crashlytics to your React Native iOS app
Bruno Barbieri
9616

Everything worked out great, only thing was that I had trouble seeing data in my Fabric dashboard from my release build on my own phone . I happened upon these instructions from the desktop Fabric app in order to confirm proper onboarding of Crashlytics:

`http://screencast.com/t/6OXvqxJAMYBf`

The screen prior to the above provided an Objective C snippet adding a force crash button to a View. Since I couldn’t think of a React Native way of doing this in JS, I just copied and pasted this part of their snippet…:

[[Crashlytics sharedInstance] crash];

… under the step in this blog post where we added:

[Fabric with:@[[Crashlytics class]]];

Once I returned to running the app in Xcode again (in the Fabric instructions), I removed the above line to let the data arrive at the dashboard it seems and subsequent JS specific logging started arriving afterwards. I’m no sure if the force crash coerced the dashboard to start picking up reporting somehow, or there was just a lag in data arriving during my initial attempts, but either way, I’m adding this here so you too can at least confirm your onboarding.

Lastly, I asked this Stackoverflow question to fill in a gap when it comes to how / where to setup your source map bundling in Xcode for only your prod release:

`http://stackoverflow.com/questions/35959527/where-to-add-source-map-command-in-xcode-for-my-production-build-when-adding-sou`

I am seeing an accurate file name and even method name, but not accurate line number. It’s off by 96 lines. So if anyone can think of the whys here, please chime in, but I’ll take this over cryptic Objective C thread errors any day!

Great article, thank you so much!

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.