firebase analytics question.

[안정민]

hi
I have a few questions, so leave me an e-mail.
plz help

1. Does the "app_exception" event count include both crashes and ANRs, or is it limited to only pure exception events?
2. Under what circumstances does the "app_exception" occur and get added to the counts?
3. Is there any way I could closely examine the details of each "app_exception" event? (i.e. Crashltics)
4. Does the "app_exception" count increase even when it is resolved with a "try-catch"?
5. Does a high "app_exception" record indicate a high likelihood of crashes or ANRs?
6. Would you say it's normal to have 1.2 million  of app_exception events per day?
7. Upon inspecting the classpath, the presence of "(not set)" is noticed. What exactly does this indicate?
8. Does the fact that my application exposes ads through push notifications indicate "(not set)" in Question 7?
9. What factors contribute to the disparities between the results obtained from Google Analytics and Firebase Analytics?
10. Does the number of installed users in Google Play Store also include installations from other stores like One Store, or is it solely based on installations from Google Play Store?


thank you

I'll wait for your reply

[Ray Gamma]

• The "app_exception" event in Firebase Analytics is designed to track uncaught exceptions which usually result in a crash of your application. ANR (Application Not Responding) situations are typically not included unless your specific implementation catches and reports them as unhandled exceptions.
• The "app_exception" event is automatically triggered when an uncaught exception (crash) occurs in your app. In other words, when an exception is thrown in your app but is not caught and handled by any code in your app, this event is triggered and gets added to the count.
• To closely examine the details of each "app_exception" event, you would typically use a tool like Firebase Crashlytics. It provides detailed insights about the crashes, including stack traces, affected devices, and Android OS versions, which can help in debugging.
• If an exception is handled with a "try-catch" block, it typically doesn't result in an "app_exception" event unless you explicitly log it. The purpose of "try-catch" is to gracefully handle exceptions without crashing the app.
• Yes, a high "app_exception" record generally indicates a high likelihood of crashes. However, it doesn't directly link to ANRs unless they're reported as exceptions.
• Whether it's normal to have 1.2 million "app_exception" events per day would depend on the user base and context of your application. If you have a massive active user base, it might be reasonable. However, in general, it's a large number, and I'd recommend looking into your crash reports to improve the app's stability.
• The "(not set)" value in Google Analytics is typically used when there is no information available to populate a given field. In the context of classpaths, it might mean that certain events are not associated with any specific class or the class information is not available at the time of the event.
• The fact that your application exposes ads through push notifications should not directly cause "(not set)" values in classpath reporting. These two aspects are generally unrelated.
• Disparities between Google Analytics and Firebase Analytics results can stem from several factors. Some common ones include: different user identification methodologies, session definitions, data processing latency, filters applied, and the way these platforms handle bots and spam.
• The number of installed users reported in Google Play Store only includes installations from the Google Play Store. Installations from other stores like One Store, Amazon App Store, etc., are not included in Google Play's statistics.

I hope this helps answer your questions. If you need further clarifications or have additional questions, feel free to ask!

2023년 8월 4일 금요일 오후 11시 46분 46초 UTC+9에 안정민님이 작성: