Android - Objects.requireNonNull java.lang.NullPointerException - Unable to start activity ComponentInfo{mypackage/com.google.android.gms.auth.api.signin.internal.SignInHubActivity}

[atul-vts]

Describe the bug Hi Team, we've encountered a crash on our Firebase Crashlytics, this is not directly reproducible to us. So we wanted to share it with you so that you can guide us or let us know if it got fixed in any of the upgraded versions.

To Reproduce Steps to reproduce the behavior: Please find the crash log below:

Fatal Exception: java.lang.RuntimeException Unable to start activity ComponentInfo{MYPACKAGE/com.google.android.gms.auth.api.signin.internal.SignInHubActivity}: java.lang.NullPointerException android.app.ActivityThread.performLaunchActivity (ActivityThread.java:3431) android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:3595) android.app.servertransaction.LaunchActivityItem.execute (LaunchActivityItem.java:85) android.app.servertransaction.TransactionExecutor.executeCallbacks (TransactionExecutor.java:135) android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:95) android.app.ActivityThread$H.handleMessage (ActivityThread.java:2066) android.os.Handler.dispatchMessage (Handler.java:106) android.os.Looper.loop (Looper.java:223) android.app.ActivityThread.main (ActivityThread.java:7664) java.lang.reflect.Method.invoke (Method.java) com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:592) com.android.internal.os.ZygoteInit.main (ZygoteInit.java:947)

Caused by java.lang.NullPointerException java.util.Objects.requireNonNull (Objects.java:220) com.google.android.gms.auth.api.signin.internal.SignInHubActivity.onCreate (com.google.android.gms:play-services-auth@@20.1.0:23) android.app.Activity.performCreate (Activity.java:7994) android.app.Activity.performCreate (Activity.java:7978) android.app.Instrumentation.callActivityOnCreate (Instrumentation.java:1309) android.app.ActivityThread.performLaunchActivity (ActivityThread.java:3404) android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:3595) android.app.servertransaction.LaunchActivityItem.execute (LaunchActivityItem.java:85) android.app.servertransaction.TransactionExecutor.executeCallbacks (TransactionExecutor.java:135) android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:95) android.app.ActivityThread$H.handleMessage (ActivityThread.java:2066) android.os.Handler.dispatchMessage (Handler.java:106) android.os.Looper.loop (Looper.java:223) android.app.ActivityThread.main (ActivityThread.java:7664) java.lang.reflect.Method.invoke (Method.java) com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:592) com.android.internal.os.ZygoteInit.main (ZygoteInit.java:947)

Expected behavior The crash shouldn’t occur.

Screenshots It's on Firebase:

Desktop (please complete the following information):

• Gradle version: 7.0.4
• Android Studio version: Android Studio Giraffe | 2022.3.1

[atul-vts]

Any update on this?

[atul-vts]

Hi Team,

Can anyone provide an update on this?

[davidmotson]

Hello, I think this bug may be filed to the wrong repo. If this is a bug on the firebase-auth SDK you should file it here.

Steps to reproduce an issue are very valuable, and without them it may be difficult to resolve this. From a very shallow reading of the stack trace, and missing a lot of context, a debugging step might be to check if the app contains play-services-auth, and if you can replicate by triggering the sign in flow.