firebase_auth: ios auth error => The request does not contain a client identifier.

[ilu55]

Is there an existing issue for this?

• I have searched the existing issues.

Which plugins are affected?

Auth

Which platforms are affected?

iOS

Description

Face issue for iOS login. All setup is done, but the problem is still there.

In a device based on plugin response error, the request does not contain a client identifier.

When debugging with Xcode and checking the error shows like this => [FirebaseAuth][I-AUT000018] Error getting App Check token; using placeholder token instead. Error: Error Domain=com.google.app_check_core Code=4 "The attestation provider DeviceCheckProvider is not supported on current platform and OS version." UserInfo={NSLocalizedFailureReason=The attestation provider DeviceCheckProvider is not supported on current platform and OS version.}

Reproducing the issue

Enable captcha enterprise and then disable

Firebase Core version

3.15.1

Flutter Version

3.29.2

Relevant Log Output

Flutter dependencies

Expand Flutter dependencies snippet

Replace this line with the contents of your `flutter pub deps -- --style=compact`.

Additional context and comments

No response

[SelaseKay]

Hi @ilu55, kindly provide a minimal example which reproduces this issue.

[ilu55]

Hello @SelaseKay

Yes, both my apps are working fine when initially set up. But after enabling the reCAPTCHA enterprise api faced some issues (the error coming is some internal issue) then I took help from Firebase team and disabled it. Now the issue is coming. The request does not contain a client identifier. Also create new project and add all setup there but still this issue is coming. My both app test and device check is enabled is that cause this issue?

[MichaelVerdon]

Hi, we are saying we want to see a reproducible example so we can see your implementation of how you are using this. Also what version of iOS are you getting this on?

[ilu55]

Hello @MichaelVerdon @SelaseKay

Thanks for the support. Now the issue is solved. So I'm closing this issue.