Fabric.io: new app does not show up in the dashboard

crashlytics crashlytics-android google-fabric
svzi picture svzi · May 18, 2017 · Viewed 10.2k times · Source

For some reason we needed to change the package-id of our existing android application. We already use Fabric for Crashlytics.

I'm trying to bring that new app up in the Fabric dashboard, but it's not showing there, despite the device log showing no issues (as fas as I can see): device log

Any ideas why the new package-id isn't visible in our dashboard?

Best, Sven

Answer

Jake Lee picture Jake Lee · Dec 5, 2018

I experienced a very similar issue to this when building an app with multiple flavours. The solution is to manually specify the package name, and not let Fabric try to automatically grab it, as it tries very hard to "stick" your old package name.

There is a full post available (disclaimer: my site), but essentially you need to use:

    Fabric.with(
        Fabric.Builder(this)
            .kits(Crashlytics())
            .appIdentifier(BuildConfig.APPLICATION_ID)
            .build()
    )

Related questions

Fabric's Crashlytics with Firebase can't be disabled for DEBUG builds

I have an app that utilises Fabric's Crashlytics via Firebase. The following is the first thing executed in my Applications onCreate CrashlyticsCore crashlyticsCore = new CrashlyticsCore.Builder() .disabled(BuildConfig.DEBUG) .build(); Fabric.with(this, new Crashlytics.Builder().core(crashlyticsCore).build()); Nonetheless, …

Read More
Firebase Crashlytics not reporting crashes when manually enabled

Crashlytics works just fine without opt-in reporting. But it stops reporting anything as soon as I set up opt-in reporting according to the tutorial. Specifically, I added the following content to AndroidManifest.xml <meta-data android:name="firebase_crashlytics_collection_…

Read More
Log Non-fatal errors on Crashlytics

On iOS it's possible to use recordError(error) to log non-fatal errors on Crashlytics but apparently this feature is not available for Android. The only alternative I found is to use logException(e). I manage errors on my app and …

Read More