Join us January 15th for an AMA with Champion Achaia Walton, who will be talking about her article on Event-Based Reporting and Measuring Content Groups!
We have an app design with single activity and multiple fragments. Each fragment has its own lifecycle so, onResume() function will be called multiple times when user navigates and interacts with the app. This might report false crashes. The crash tracking at our end is done via crashlytics.
Is there a more targeted way to tag the lifecycle/parent of just the views?
