{"id":875,"date":"2026-09-16T14:50:31","date_gmt":"2026-09-16T09:20:31","guid":{"rendered":"https:\/\/www.shakebug.com\/blog\/?p=875"},"modified":"2026-09-16T14:54:40","modified_gmt":"2026-09-16T09:24:40","slug":"migrating-from-firebase-crashlytics-to-shakebug-in-react-native","status":"publish","type":"post","link":"https:\/\/www.shakebug.com\/blog\/migrating-from-firebase-crashlytics-to-shakebug-in-react-native\/","title":{"rendered":"Migrating from Firebase Crashlytics to Shakebug in React Native – Shakebug"},"content":{"rendered":"

<\/span>Migrating from Firebase Crashlytics to Shakebug in React Native<\/span><\/h1>\n

This is for React Native teams who’ve already decided Crashlytics isn’t enough on its own \u2014 usually because it has no in-app bug reporting, no session context, and no official React Native SDK at all<\/a>. If you’re still weighing whether to switch, read the Crashlytics vs. Shakebug comparison<\/a> first; this post picks up after that decision and covers the mechanics of actually doing it.<\/p>\n

Migrating means running both SDKs in parallel for a defined window, not deleting Crashlytics on day one. You want to see Shakebug capturing everything Crashlytics does before you pull the older SDK out. The steps below walk through that in order: install Shakebug next to Crashlytics, run both, compare how each one groups the same crash, move your Jira\/Slack\/Linear alerting over, then remove Crashlytics once you’re confident.<\/p>\n

<\/span>Step 1: Install Shakebug alongside Crashlytics<\/span><\/h2>\n

Nothing gets removed in this step. Crashlytics keeps running exactly as it is \u2014 you’re adding a second SDK next to it.<\/p>\n

Install the package:<\/p>\n

npm install shakebug-react-native\r\n# or\r\nyarn add shakebug-react-native<\/code><\/pre>\n
iOS setup.<\/strong> Add the three usage-description keys Shakebug needs for shake-to-report (screenshot, screen recording, and photo attachment) to ios\/YourProjectName\/Info.plist<\/code>:<\/p>\n
<key>NSCameraUsageDescription<\/key>\r\n<string>Used to attach a screenshot to bug reports<\/string>\r\n\r\n<key>NSMicrophoneUsageDescription<\/key>\r\n<string>Used to record audio in screen recordings<\/string>\r\n\r\n<key>NSPhotoLibraryUsageDescription<\/key>\r\n<string>Used to save and attach screen recordings<\/string><\/code><\/pre>\n
Then install pods:<\/p>\n
cd ios && pod install && cd ..<\/code><\/pre>\n
Android setup.<\/strong> Shakebug requires minSdkVersion<\/code> 24 or later. Check android\/build.gradle<\/code>:<\/p>\n
buildscript {\r\n    ext {\r\n        minSdkVersion = 24 \/\/ or later\r\n    }\r\n}<\/code><\/pre>\n
Wrap your app.<\/strong> In App.js<\/code>, wrap your existing tree in ShakebugView<\/code>. Crashlytics doesn’t need any code change here \u2014 it keeps initializing itself the way it already does, through @react-native-firebase\/app<\/code> and your existing GoogleService-Info.plist<\/code> \/ google-services.json<\/code>:<\/p>\n
import React from 'react';\r\nimport ShakebugView from 'shakebug-react-native';\r\n\/\/ your existing Crashlytics import stays exactly as it is\r\nimport crashlytics from '@react-native-firebase\/crashlytics';\r\n\r\nexport default function App() {\r\n  return (\r\n    <ShakebugView\r\n      Android_appkey=\"YOUR_ANDROID_APP_KEY\"\r\n      iOS_appkey=\"YOUR_IOS_APP_KEY\"\r\n    >\r\n      {\/* your existing app tree, Crashlytics untouched *\/}\r\n      <YourExistingApp \/>\r\n    <\/ShakebugView>\r\n  );\r\n}<\/code><\/pre>\n
Crash capture in Shakebug is on by default (allowCrashReport<\/code> defaults to true<\/code>) \u2014 mounting ShakebugView<\/code> is the whole setup, no separate crash-reporting init call. Get your app keys from the Shakebug dashboard under your project’s SDK instructions page after creating a free project \u2014 no credit card needed to get this far.<\/p>\n
If you use NavigationContainer<\/code> in the same file, pass independent<\/code> so it doesn’t fight ShakebugView<\/code> for the navigation ref:<\/p>\n
<ShakebugView Android_appkey=\"YOUR_ANDROID_APP_KEY\" iOS_appkey=\"YOUR_IOS_APP_KEY\">\r\n  <NavigationContainer independent>\r\n    {\/* your app *\/}\r\n  <\/NavigationContainer>\r\n<\/ShakebugView><\/code><\/pre>\n
<\/span>Step 2: Run both in parallel for a defined window<\/span><\/h2>\n
Ship a build with both SDKs live and leave it that way for a couple of full release cycles \u2014 long enough to cover at least one app version rollout end to end. [ESTIMATE \u2014 unverified]<\/span> Two to four weeks is a reasonable starting window for most teams; adjust to your own release cadence rather than treating it as a fixed number.<\/p>\n
What to watch during the window:<\/p>\n