Firebase Crashlytics

Ship crash reports and non-fatal events to your Firebase project, with runtime opt-in / opt-out from your web app.

Firebase Crashlytics integration sends anonymous crash reports and non-fatal events to your Firebase project, so you can spot stability issues in production.

How to Enable:

1. Set up Firebase for your app and drop google-services.json into AndroidStudioSourceCode/app/.
2. In Config.java, turn tracking on:

   public static final boolean TRACKING_EVENT = true;
           

TRACKING_EVENT = false disables all tracking-related features, including Crashlytics event logging and the starttracking:// / endtracking:// triggers.

Runtime Opt-In / Opt-Out from Your Web App:

WebViewGold respects a per-user tracking flag that is persisted on the device. Use the standard tracking triggers to change it at runtime:

<a href="starttracking://">Enable analytics & crash reports</a>
<a href="endtracking://">Disable analytics & crash reports</a>

When the user is opted out, Crashlytics collection is turned off — nothing is uploaded.

What Is Reported:

• Unhandled crashes (stack traces, device model, OS version).
• Non-fatal exceptions logged internally by the app shell.
• No personal user data is attached by default.

Where to View the Reports: Open your Firebase Console → Crashlytics dashboard. Reports usually appear within a few minutes of a crash.

Notes: Crashlytics initialization is best-effort — if Firebase is misconfigured, the app still runs normally. Consider adding a consent screen (GDPR / CCPA) before calling starttracking:// for the first time.