Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: [auth/missing-client-identifier] This request is missing a valid app identifier, meaning that Play Integrity checks, and reCAPTCHA checks were unsuccessful. #8013

Closed
IMTPL opened this issue Sep 12, 2024 · 4 comments

Comments

@IMTPL
Copy link

IMTPL commented Sep 12, 2024

We are integrating phone auth in our application.We faced an error while integrating the error problem is [Error: [auth/missing-client-identifier] This request is missing a valid app identifier, meaning that Play Integrity checks, and reCAPTCHA checks were unsuccessful. Please try again, or check the logcat for more details.]

We had also enable Google Play Integrity API & followed the document also

Here's what we integrated into it
android/app/build.gradle
apply plugin: 'com.google.gms.google-services
implementation(platform("com.google.firebase:firebase-bom:33.2.0"))
implementation 'com.google.android.gms:play-services-safetynet:18.0.1'
implementation 'com.google.firebase:firebase-auth'

Code:-
const sendOtp = async () => {
try {
const confirmation = await auth().signInWithPhoneNumber(phoneNumber);
setVerificationId(confirmation.verificationId);
console.log('OTP sent');
} catch (error) {
console.error(error);
}
};
const confirmCode = async () => {
try {
const credential = auth.PhoneAuthProvider.credential(
verificationId,
code,
);
await auth().signInWithCredential(credential);
console.log('Phone authentication successful');
} catch (error) {
console.log(error);
}
};

We integrated into react native version 0.75.3

I completed all the basics check what is needed for these phone auth otp integration

Copy link

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.

@github-actions github-actions bot added the Stale label Oct 10, 2024
@IamMax279
Copy link

same problem, any updates?

@mikehardy
Copy link
Collaborator

@IamMax279 there will not be updates on your project not having a valid app identifier, you have to make sure your app has a valid app identifier.

@github-actions github-actions bot removed the Stale label Oct 19, 2024
@russellwheatley
Copy link
Member

There's plenty of resources to help you debug this particular issue, for example see this stackoverflow thread for potential solutions.

One that I've seen a few times; replace your sha-1 and sha-256 keys (could be incorrect for a few reasons).

  1. run ./gradlew signingReport in android/ directory of your app.
  2. paste keys into the Firebase console for your app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants