Crashlytics vs Analytics: Two SDKs, Two Different Data Safety Answers

Firebase Crashlytics and Firebase Analytics ship together so often that developers treat them as one declaration. They're not. Crashlytics collects crash logs and stack traces — filed under "Diagnostics" in Data Safety. Analytics collects usage events — filed under "App activity."

Mixing them into a single row is a common rejection trigger, because Google's automated cross-check compares your declared categories against known SDK signatures, and a missing "Diagnostics" row when Crashlytics is present is an easy automated catch.

The fix

Fix: treat every Firebase product as its own line item, even when they share one google-services.json file.

The same check runs automatically when you upload your bundle to the AAB analyzer — permissions, SDK fingerprints, and version info in one pass, free.

Keep going

Data Safety generator →

Turns these answers into a Play-ready CSV.

Data Safety guide →

The full method behind the checks.

Short, specific submission fixes.

Run this check on your own AAB

Free analysis, exports when you need them.

Start free See pricing