-
Notifications
You must be signed in to change notification settings - Fork 16
L.3 Customize Reports
Unlike the native SDK, Crashlytics does not start automatically on the AIR side. You're not loosing anyting though! just a simple Crashlytics.init();
call after FirebaseCore is successfuly initialized will start it anyhow. But the good thing is that you will have control on when you wish Crash reports to be collected.
For more fine-grained control of your crash reports, for example, you can enable opt-in reporting for privacy-minded users, add logs to track down pesky bugs, and more.
Note: You can't stop Crashlytics reporting once you've initialized it in an app session. To opt-out of reporting after you've initialized Crashlytics, users have to restart your app.
Custom keys help you get the specific state of your app leading up to a crash. You can associate arbitrary key/value pairs with your crash reports, and see them in the Firebase console.
You can pass key values as String, Number, int or Boolean
Crashlytics.log("key1", 1); //int
Crashlytics.log("key2", 1.2); // Number
Crashlytics.log("key3", true); // Boolean
Crashlytics.log("key4", false);// Boolean
Crashlytics.log("key5", "String");
Note: Re-setting a key updates its value.
To diagnose an issue, it’s often helpful to know which of your users experienced a given crash. Crashlytics includes a way to anonymously identify users in your crash reports.
To add user IDs to your reports, assign each user a unique identifier in the form of an ID number, token, or hashed value:
Crashlytics.userIdentifier = "1234567890";
If you need to clear a user identifier after you set it, reset the value to a blank string.
Crash Insights helps you resolve issues by comparing your anonymized stack traces to traces from other Firebase apps and letting you know if your issue is part of a larger trend. For many issues, Crash Insights even provides resources to help you debug the crash.
Crash Insights uses aggregated crash data to identify common stability trends. If you’d prefer not to share your app's data, you can opt-out of Crash Insights from the Crash Insights menu at the top of your Crashlytics issue list in the Firebase console.
Enjoy building Air apps – With ♥ from MyFlashLabs Team
Introduction to Firebase ANEs collection for Adobe Air apps
Get Started with Firebase Core in AIR
- Prerequisites
- Add Firebase to your app
- Add the Firebase SDK
- Init Firebase Core
- Available ANEs
- Managing Firebase iid
Get Started with Authentication
- Add Authentication
- Init Authentication
- Manage Users
- Phone Number
- Custom Auth
- Anonymous Auth
- State in Email Actions
- Email Link Authentication
Get Started with FCM + OneSignal
- Add FCM ANE
- Init FCM ANE
- Send Your 1st Message
- Send Msg to Topics
- Understanding FCM Messages
- init OneSignal
- Add Firestore
- Init Firestore
- Add Data
- Transactions & Batches
- Delete Data
- Manage the Console
- Get Data
- Get Realtime Updates
- Simple and Compound
- Order and Limit Data
- Paginate Data
- Manage Indexes
- Secure Data
- Offline Data
- Where to Go From Here
Get Started with Realtime Database
- Add Realtime Database
- Init Realtime Database
- Structure Your Database
- Save Data
- Retrieve Data
- Enable Offline Capabilities
Get Started with Remote Config
- Add Storage ANE
- Init Storage ANE
- Upload Files to Storage
- Download Files to Air
- Use File Metadata
- Delete Files