Google Sign in failing due to SharedElementCallback

Question

I have used pretty much the boilerplate from firebase and google sign on documentation. I get the dialog for choosing the account to log in from, and then it fails. I have updated my google play services. And also regenerated my sha1 keys. One thing that I have noticed is that android studio keeps giving me back the old key when executing the signingreport task, tho I have generated keys twice after that, and also updated on the firebase console.

Gist of the main activity on github

E/dalvikvm: Could not find class 'android.support.v4.app.ActivityCompat$SharedElementCallback23Impl', referenced from method android.support.v4.app.ActivityCompat.setEnterSharedElementCallback
E/dalvikvm: Could not find class 'android.support.v4.app.ActivityCompat$SharedElementCallback21Impl', referenced from method android.support.v4.app.ActivityCompat.setEnterSharedElementCallback
E/dalvikvm: Could not find class 'android.support.v4.app.ActivityCompat$SharedElementCallback23Impl', referenced from method android.support.v4.app.ActivityCompat.setExitSharedElementCallback
E/dalvikvm: Could not find class 'android.support.v4.app.ActivityCompat$SharedElementCallback21Impl', referenced from method android.support.v4.app.ActivityCompat.setExitSharedElementCallback

Have you added/imported the `SharedElementCallback23Impl` library/class? — Alex Mamo, Jan 10 '19 at 11:21
I have not used the class explicitly in the code. I think some function or class that I have used calls it in turn, so I shouldn't have to import it right? — anushka, Jan 10 '19 at 12:57
Yes, even after explicitly importing it, it crashes in the same way — anushka, Jan 10 '19 at 13:31

score 0 · Accepted Answer · answered Jan 10 '19 at 14:00

So, because android studio was showing me the wrong, originally generated key when running the signingreport task from gradle, I tried generating new keys but that wasn't working. And then I found this which explained how to find the debug keystore in android studio and set it up. My android studio was taking its keys from the .android directory in my home directory while I was generating keys in a different directory. After configuring the keys through this, I also got an error saying the key strength was very less, but that was easy to solve(just add the -keyalg RSA argument while generating keys.

And then when I launched the app it said that due to CA certificates being no longer valid I should uninstall and install again. And voila, it worked.

Google Sign in failing due to SharedElementCallback

1 Answers1