Feature - Firebase Analytics & Crashlytics #236
Conversation
Removed orphan general_care_view.dart.
I've tested the branch out, and it appears to have no ill effects. Kind of hard to tell if its doing anything or not 😁 |
@lukesleeman Yep, until there is some data, it's a nice to have thing. But using the simulation code (in there but commented out) one crash type at a time and setting So I've tested all 3 levels of crash locally on Android and iOS for the simulations. Just waiting on crash data to show up in the console ... but its been a while so will go back and check. But if the app isn't talking to Crashlytics then when you goto the Firebase console you only get the setup wizard'. So because we can see the proper Crashlytics console view the app MUST have talked to Crashlytics already. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@workerbee22 So I'd feel much better once we can actual app generated errors, especially app crashes in the console 🙂 |
I'll do a check against the project for which I provided the screen shots ie. these. Perhaps I missed something: Issue: #15 |
Looks good to me! Appreciate for your effort to make it happen! |
OK so nothing in the console yet for Crashlytics from my tests ... investigating. Analytics data coming through fine. |
…ting' into feature/add-analytics-crashreporting
OK PR workflow build all OK. Merging this one. |
Initial implementation of Firebase Analytics (data is also passed to Google Analytics) and Firebase Crashlytics for crash & error reporting. Note this is just the initial implementation.
Changes
Screenshots
No UI changes.
Things to note