Latest version of app not appearing in Crashlytics

928 views
Skip to first unread message

Hargreaves Lansdown

unread,
Aug 14, 2018, 1:46:05 PM8/14/18
to Firebase Google Group
Hi there

The latest version of our app doesn't appear in the Crashlytics section of the console - both in Firebase and Fabric. Weirdly the Dev and QA versions of the same version do appear but not the Live version. I can't believe we're 100% crash free just yet! We did attempt to move our reporting from Fabric to Firebase exclusively which seemed to work for the Dev and QA versions when we simulated crashes but our released version is missing crashes from the console. 

For example: 
We've got a single project with 3 registered apps. Live, Dev, QA.

I'm pretty sure we followed all the set up instructions correctly. The only other thing to point out is that we disable Crashlytics on start up but turn it on based on a saved user preference shortly afterwards like this:

protected void setCrashlytics(boolean enabled) {
if (enabled) {
final Fabric fabric = new Fabric.Builder(this)
.kits(new Crashlytics())
.debuggable(!BuildConfig.FLAVOR_mode.equals(FlavourType.LIVE)) // Debug if we are not live
.build();

Fabric.with(fabric);

String clientId = mSharedPrefController.getClientId();
if (clientId != null && !clientId.isEmpty()) {
Crashlytics.setUserIdentifier(clientId);
}
}
}


Other than that, the Release (live) version is Proguarded and shrunk that's about the only differences I can think of.

Any ideas? It's concerning that we're not seeing anything in the console. Must be something we've overlooked.

Thanks.

mbon...@google.com

unread,
Aug 14, 2018, 5:12:28 PM8/14/18
to Firebase Google Group
Did you set this up as a new to Firebase Crashlytics project or link the two apps? If the latter, did you keep the Fabric API key in the AndroidManifest.xml or build.gradle? 
Reply all
Reply to author
Forward
0 new messages