I'm becoming familiar with the Firefox for Android code, and it seems like there's a number of possible scopes for this change. 1. [GeckoView](https://searchfox.org/mozilla-central/source/mobile/android/geckoview/src/main/java/org/mozilla/geckoview): adding crash reporting here may best achieve the desired outcome, depending on how you look at it. We could get crash pings from _anyone_ using GeckoView (which may be projects other than Fenix). On one hand, this would cover all Gecko crashes, but on the other, some people using GeckoView may not like telemetry being built-in. However, it could be opt-in. It's worth noting that if we want to capture _other_ (non-Gecko) crashes in Fenix, maybe those could be reported separately (e.g. as a separate crash "product" than GeckoView), which may lend itself better to debugging/metrics tracking. `geckoview` doesn't currently contain Glean, however `geckoview-omni` does. 2. [Android Components lib-crash](https://github.com/mozilla-mobile/firefox-android/tree/main/android-components/components/lib/crash): the crash library already supports Sentry and Socorro as services, so adding a Glean service here would be appropriate. This is also where the crash count Glean metric is already integrated. One might consider this equivalent to (1) in some regards, since an app writer (and Fenix) may opt-in by using lib-crash (as long as they're aware it exists). 3. [Fenix](https://github.com/mozilla-mobile/fenix): adding crash pings directly to Fenix would be fairly straightforward. The codebase already uses Glean, sends a number of pings, and has [existing logic](https://github.com/mozilla-mobile/fenix/blob/main/app/src/main/java/org/mozilla/fenix/home/intent/CrashReporterIntentProcessor.kt) managing crash events. However, currently crash reporting in Fenix is done through (2), so putting it directly in the Fenix code is likely not the best approach.
Bug 1810951 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I'm becoming familiar with the Firefox for Android code, and it seems like there's a number of possible scopes for this change. 1. [GeckoView](https://searchfox.org/mozilla-central/source/mobile/android/geckoview/src/main/java/org/mozilla/geckoview): adding crash pings here may best achieve the desired outcome, depending on how you look at it. We could get crash pings from _anyone_ using GeckoView (which may be projects other than Fenix). On one hand, this would cover all Gecko crashes, but on the other, some people using GeckoView may not like telemetry being built-in. However, it could be opt-in. It's worth noting that if we want to capture _other_ (non-Gecko) crashes in Fenix, maybe those could be reported separately (e.g. as a separate crash "product" than GeckoView), which may lend itself better to debugging/metrics tracking. `geckoview` doesn't currently contain Glean, however `geckoview-omni` does. 2. [Android Components lib-crash](https://github.com/mozilla-mobile/firefox-android/tree/main/android-components/components/lib/crash): the crash library already supports Sentry and Socorro as services, so adding a Glean service here would be appropriate. This is also where the crash count Glean metric is already integrated. One might consider this equivalent to (1) in some regards, since an app writer (and Fenix) may opt-in by using lib-crash (as long as they're aware it exists). 3. [Fenix](https://github.com/mozilla-mobile/fenix): adding crash pings directly to Fenix would be fairly straightforward. The codebase already uses Glean, sends a number of pings, and has [existing logic](https://github.com/mozilla-mobile/fenix/blob/main/app/src/main/java/org/mozilla/fenix/home/intent/CrashReporterIntentProcessor.kt) managing crash events. However, currently crash reporting in Fenix is done through (2), so putting it directly in the Fenix code is likely not the best approach.
I'm becoming familiar with the Firefox for Android code, and it seems like there's a number of possible scopes for this change. 1. [GeckoView](https://searchfox.org/mozilla-central/source/mobile/android/geckoview/src/main/java/org/mozilla/geckoview): adding crash pings here may best achieve the desired outcome, depending on how you look at it. We could get crash pings from _anyone_ using GeckoView (which may be projects other than Fenix). On one hand, this would cover all Gecko crashes, but on the other, some people using GeckoView may not like telemetry being built-in. However, it could be opt-in. I expect the only crashes that could be reported would be non-fatal ones. It's worth noting that if we want to capture _other_ (non-Gecko) crashes in Fenix, maybe those could be reported separately (e.g. as a separate crash "product" than GeckoView), which may lend itself better to debugging/metrics tracking. `geckoview` doesn't currently contain Glean, however `geckoview-omni` does. 2. [Android Components lib-crash](https://github.com/mozilla-mobile/firefox-android/tree/main/android-components/components/lib/crash): the crash library already supports Sentry and Socorro as services, so adding a Glean service here would be appropriate. This is also where the crash count Glean metric is already integrated. One might consider this equivalent to (1) in some regards, since an app writer (and Fenix) may opt-in by using lib-crash (as long as they're aware it exists). 3. [Fenix](https://github.com/mozilla-mobile/fenix): adding crash pings directly to Fenix would be fairly straightforward. The codebase already uses Glean, sends a number of pings, and has [existing logic](https://github.com/mozilla-mobile/fenix/blob/main/app/src/main/java/org/mozilla/fenix/home/intent/CrashReporterIntentProcessor.kt) managing crash events. However, currently crash reporting in Fenix is done through (2), so putting it directly in the Fenix code is likely not the best approach.