Phone Auth not working in iOS 16 simulator.

[Archetapp]

Description

For our app, in order to login, we use Phone Authentication. When testing on any OS below iOS16 in the iOS Simulator, it works perfectly for both test numbers and live phone numbers.

But now with iOS16, it throws the following error:

"Error Domain=FIRAuthErrorDomain Code=17048 "Token mismatch" UserInfo={NSLocalizedDescription=Token mismatch, FIRAuthErrorUserInfoNameKey=INVALID_APP_CREDENTIAL}"

I've tried it in both Sandbox, Production & Unknown APNs environments, but nothing fixes it.

Reproducing the issue

Submit a number to Phone Authentication

 finalPhone = "+" + "12345678910"
        PhoneAuthProvider.provider(auth: Auth.auth()).verifyPhoneNumber(finalPhone, uiDelegate: nil) {
            verificationID, error in
            if let error = error {
                print(error)
                completion(false)
                return
            } else {
                UserDefaults.standard.set(verificationID, forKey: "authVerificationID")
                completion(true)
            }
        }

Firebase SDK Version

master

Xcode Version

14.0

Installation Method

Swift Package Manager

Firebase Product(s)

Authentication

Targeted Platforms

iOS

Relevant Log Output

No response

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[morganchen12]

@Archetapp are you able to use phone auth successfully via our sample app?

[google-oss-bot]

Hey @Archetapp. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[tomas-petrovcin]

Having the same issue (using via react-native-firebase).

As @Archetapp described, it works fine with previous iOS versions - doesn't work since developer beta iOS 16, now tested on stable release with same results

It works on devices, but I think it might be because it uses verification via notification, whereas simulator defaults to recaptcha. Seems to me it might be that recaptcha isn't able to open on new version of Safari or something like that.

We could test that by enforcing recaptcha on device as well as see if it fails, but I am not sure how I could do that.

Error from react-native-firebase, comment says // this fails for some browsers. :(

cc @morganchen12

[morganchen12]

Looks like this is caused by APNS support in the simulators in iOS 16+. The Auth SDK is trying to use APNS instead of captcha since it's available, but #9968 needs to be resolved before this can work successfully. (Thanks to Rosalyn for investigating.)

Would you prefer if we forced captcha on simulators or just used APNS?

[scottsmithdev]

So, in my case, we're not getting any response back at all. It just keeps on spinning. We've tried on iOS 15 & 16 simulators.

        .package(url: "https://github.com/firebase/firebase-ios-sdk",
                 from: "9.2.0"),

[scottsmithdev]

So, in my case, we're not getting any response back at all. It just keeps on spinning. We've tried on iOS 15 & 16 simulators.

        .package(url: "https://github.com/firebase/firebase-ios-sdk",
                 from: "9.2.0"),

Ok, we actually got it to work by going into Info.plist and adding FirebaseAppDelegateProxyEnabled with a value of NO. This disables swizzling, which Firebase actually relies on for some features -- so be warned. Look into it first. If your features aren't part of those that need swizzling, then try this out.

[tomas-petrovcin]

Thanks for answering @morganchen12.
I am fine with using notifications on sim, once it's supported.
But shouldn't it revert to recaptcha when it fails like this?
Also for testing it would be actually nice if we could switch between the two methods manually and test both scenarios separately.