Why Does My Firebase UI Google Authentication Fail with 'Code: 10, Message: 10' After Play Store Release?

Firebase UI Authentication with Google Fails with "Code: 10, Message: 10" Error

Encountering issues with Google authentication in your Firebase-based chat app? Users are experiencing a cryptic "code:10 message:10" toast upon attempting to sign in when downloading your app from the Play Store, even though it functions smoothly in debug mode.

Seeking a Solution

Despite adding the SHA1 fingerprint, the problem persists. How can you resolve this authentication snag?

Unveiling the Fix

The key to resolving this issue lies in obtaining three vital keys:

1. Debug Key: Follow the instructions here.
2. Release Key: Find details here.
3. Google Play App Signing Key: Information can be found here.

Importance of Multiple Keys

All three keys play crucial roles in ensuring a seamless sign-in process:

• The debug key is utilized for development and debugging purposes.
• The release key is employed when building the APK to be published on the Play Store.
• The Google Play App signing key is automatically generated by Google Play when publishing your app.

Additional Tips

Refer to the following resource for more insights:

• [Google Firebase Authentication: Authentication with Custom ACRA Accounts](https://firebase.google.com/docs/auth/android/custom-account)

By implementing these key-related steps, you should be able to eliminate the "code:10 message:10" error in your Firebase UI Google authentication.

The above is the detailed content of Why Does My Firebase UI Google Authentication Fail with 'Code: 10, Message: 10' After Play Store Release?. For more information, please follow other related articles on the PHP Chinese website!