Crashlytics fails to track app startup crashes

Describe your environment

• Android Studio version: 2020.3.1 patch 4
• Firebase Component: Crashlytics
• Component version: 17.4.1

Describe the problem

Crashlytics’ uncaught exception handler is printing TimeoutException when tracking crashes that happen in Application.onCreate().

FirebaseCrashlytics  E  Error handling uncaught exception
FirebaseCrashlytics  E  java.util.concurrent.TimeoutException
FirebaseCrashlytics  E      at t8.h0.a(Utils.java:11)
FirebaseCrashlytics  E      at t8.j.G(CrashlyticsController.java:6)
FirebaseCrashlytics  E      at t8.j$b.a(CrashlyticsController.java:1)
FirebaseCrashlytics  E      at t8.p.uncaughtException(CrashlyticsUncaughtExceptionHandler.java:4)
FirebaseCrashlytics  E      at io.sentry.UncaughtExceptionHandlerIntegration.uncaughtException(UncaughtExceptionHandlerIntegration.java:19)
FirebaseCrashlytics  E      at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1073)
FirebaseCrashlytics  E      at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1068)
FirebaseCrashlytics  E      at java.lang.Thread.dispatchUncaughtException(Thread.java:2200)

Steps to reproduce:

1. Integrate Firebase Crashlytics with auto initialisation.
2. Create a custom Application class and throw an exception from there.

Expected: Crashlytics should track crashes that happen in Application class Actual: Crashlytics fails to track crashes that happen in Application class and logs a TimeoutException in that process

Other information: We also use Sentry for crash reporting and it seems to track these crashes just fine

[argzdev]

Thanks for the report, @vibin. Upon reproducing this on version 18.2.8, I also did not receive a crash report on Crashlytics dashboard when the exception happens in the Application class. A minor difference with that, I did not receive a TimeoutException, rather a RuntimeException.

Relevant Code:

public class CustomApplication extends Application {
    @Override
    public void onCreate() {
        super.onCreate();
        throw new RuntimeException("Test Crash");
    }
}

With that said, I’ll notify an engineer and see if what we can do here.

[mrichards]

We believe this was fixed in Crashlytics v18.2.3. Anyone experiencing this issue should update to the latest SDK version using the Firebase BoM (currently BoM v30.4.0). If the problem persists, please open a new GitHub issue. Thanks!