Fabric to Firebase Migration FAQ¶
Q: What happens when I disable Fabric Answers analytics?
A: By turning off Answers, no more data will come through to your dashboard that is reported by the Answers service. This includes all the data on fabric.io pages powered by Answers, such as Retention, Growth, Latest Release, Events, and others, as well as the crash-free users and crash-free sessions rates that you can find on the Crashlytics page. If you’re migrating to Firebase and looking for an analytics solution, we recommend Google Analytics, a powerful tool with cross-product integration and robust features.
Q: Will I see my old Answers data?
A: Unfortunately, your previous Answers events data will not migrate with you onto Firebase. You can see still access historical Answers data for up to 90 days on your Fabric Dashboard, giving you the ability to download the data in a .csv file directly from the Dashboard.
Q: Will I see my old Crashlytics data?
A: If you complete the click-through migration successfully, you should see all your crashes appear in the Firebase console and continue to be sent to both Fabric and Firebase. No data export or work on your side is needed for this.
Q: Why aren’t my crash-free metrics lining up?
A: Fabric and Firebase use different SDKs to calculate the crash-free user statistics and metrics such as active users. On Fabric, that is powered by Answers whereas on Firebase it’s powered by Google Analytics, which also changes the way the metric is calculated in the first place.
Fabric and Firebase use different SDKs to calculate crash-free user statistics and metrics such as active users. In Fabric, this is powered by Fabric Analytics whereas in Firebase it’s powered by Google Analytics, which also results in differences in the reported metrics.
Several things may cause Fabric Analytics to discard events that might have led to a session. If an app rapidly transitions between foreground and background states, Fabric Analytics will not report separate sessions for each period of time the app spent in the foreground if it spent less than 30 seconds in the intervening background states. Also, if something occurs that prevents a background event from being detected, Fabric Analytics will not consider the prior foregrounding event as part of a session.
However, with Firebase, a user_engagement event is necessary to define activity. A user_engagement event is triggered when a user interacts with the app for a minimum duration, which can be controlled using the setMinimumSessionDuration() method call, but by default is set to 10 seconds. Analytics counts multiple app foregrounds/backgrounds as part of the same session as long as they are within 30 minutes of each other, versus the 30 seconds of Fabric Analytics. Again, in Analytics, this 30 minutes is default but customizable.
Frequently, Fabric Analytics counts more sessions and users than Google Analytics because it requires the app to have less time in foreground and background before a session/active user is officially captured and counted. This leads to small discrepancies in higher-volume apps and potentially larger discrepancies in low-volume apps with perhaps only several users and sessions per day.
Q: How do I change my Fabric Answers events to Google Analytics for Firebase events?
Q: How do I find all the features I used to use on Fabric now that I’m on Firebase?
A: We’ve created a number of helpful resources to make the transition as easy as possible:
-Check out the Firebase feature guide for more information on finding what you’re used to seeing on the Fabric dashboard.
-We also recommend taking a look at our sample app for a guide on implementation details and feature parity.
-If you’re having trouble, feel free to reach out to firstname.lastname@example.org for questions on the migration or anything Crashlytics-related.
Q: Where can I find the integrations and service hooks on Firebase like I did for Fabric?
A: The team has built out explicit support in the Firebase console for integrations with Slack, Jira, PagerDuty, and BigQuery. These can be viewed by navigating to the Firebase console, selecting the settings gear near Project Overview, and clicking on the Integrations tab in the Project Settings. You can extend these integrations or build out support for integrations with other services with Cloud Functions.
Q: Can I remove/change my Fabric API key after migrating to Firebase?
A: No, If you’ve completed the click-through Fabric migration flow to migrate to Firebase, you should leave your old Fabric API key in your app for now. Once the new Firebase Crashlytics SDKs are available and Fabric has officially been deprecated, old Fabric references will go away, so stay put with your configuration as-is for now.
Q: I linked my Fabric app to a Firebase project, and then deleted the Firebase project. How do I relink the Fabric app?
A: You will have to restore the deleted project and unlink it before you can permanently delete. To do this, go to the Resource Manager console, select the organization that the project was in from the dropdown in the upper left (next to the filter bar), and at the very bottom left corner of the page there is a button, “Resources pending deletion.” Click that, Select the project with Fabric links in it, and click “Restore” at the top of the page. Once the project is restored, visit the Project Settings -> Integrations -> Fabric page, and use the “Unlink Fabric app” button for each linked Fabric app. Now the project may be re-deleted, and you can try to re-link the Fabric app to the new Firebase project.
Q: What will happen if I don’t migrate by the deprecation date?
A: If you choose not to migrate your apps to Firebase before the deprecation date on March 31st, 2020, this will result in your app data being deleted in accordance with the Fabric Data Processing and Security Terms. You won’t be able to retrieve the last data or apps or migrate them to Firebase after this date.