[🐛] Firebase Authentication issue for devices with Android 13,14,15

[ManojKgr1902]

I have implemented Firebase Authentication in my React Native app. While the integration works correctly on most devices, I’m encountering an issue on devices running Android 13, 14, and 15 for the past 1 week and before that it is working fine. Specifically, authentication fails when attempting to register new users.

The authentication process works as expected on devices running Android 10, 11, 12, 13 (some), and the latest Android 16. Additionally, test users that were manually created in the Firebase Console can log in successfully on all devices, so the issue seems isolated to new user registration on Android 13, 14, and 15.

When attempting to register a new user, I receive the following error:

Error sending OTP: [auth/app-not-authorized] This app is not authorized to use Firebase Authentication. Please verify that the correct package name, SHA-1, and SHA-256 are configured in the Firebase Console. [Invalid PlayIntegrity token; does not pass basic integrity.]

I have verified that the package name, SHA-1, and SHA-256 keys are correctly configured in the Firebase Console.

Here are the versions I’m currently using:

react-native: 0.76.2

@react-native-firebase/auth: ^21.11.0

@react-native-firebase/messaging: ^21.12.2

I would appreciate any insights or guidance on how to resolve this issue, particularly around the Play Integrity-related error.

[MichaelVerdon]

Please use the latest versions and let me know if the same issue persists. This issue also seems to be present on Flutterfire which is making me think it could be an issue with the native SDKs https://github.com/firebase/flutterfire/issues/17382.

[mathanraj-oben]

I'm working on both a native Android and a React Native project using Firebase Phone Authentication. Everything was working earlier, but today we encountered this error on both apps: "[auth/app-not-authorized] This app is not authorized to use Firebase Authentication. Please verify that the correct package name, SHA-1, and SHA-256 are configured in the Firebase Console. [Invalid PlayIntegrity token; does not pass basic integrity.]" It seems to be a Firebase issue

[ManojKgr1902]

We have tried with the latest version and also verified by downgrading to previous versions, but the issue still persists. This functionality was working as expected until about a week ago, but we have been consistently encountering the issue since then.

[MichaelVerdon]

This does not seem to be something we can address here, I would recommend reporting it on the native-sdks as I firmly believe it is an issue there as we are a wrapper around the native sdks. I can only suggest messing around with Play Integrity settings and double checking your SHA keys.

[github-actions[bot]]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.