performRequest hangs ios14 Simulator -> App Store Rejection (use ios13 or ios16 simulator)

[se09deluca]

[:point_down: SEE COMMENTS BELOW TO UNDERSTAND STATUS / GET YOUR APP APPROVED 👇]

Hi,
i've been experiencing this error from iOS 14.

I'm using @invertase/react-native-apple-authentication@1.1.2 as i don't need Apple Signin for Android.

Although, in past AppleStore reviewers rejects my app randomly, probably depending on who tests the app, this time there's no way to make it accepts.

const appleAuthRequestResponse = await appleAuth.performRequest({ requestedOperation: AppleAuthRequestOperation.LOGIN, requestedScopes: [AppleAuthRequestScope.EMAIL, AppleAuthRequestScope.FULL_NAME], });

It's a pity, this package works perfectly for real devices!
Could you suggest me, what to do? It's a problem experienced only in my case or not only?

My React Native info

System:
OS: macOS 10.15.6
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 671.25 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 12.13.1 - /usr/local/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 6.14.3 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 14.0, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
Android SDK:
API Levels: 23, 25, 26, 27, 28, 29
Build Tools: 28.0.3, 29.0.0, 29.0.2, 29.0.3
System Images: android-19 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
IDEs:
Android Studio: 4.0 AI-193.6911.18.40.6626763
Xcode: 12.0/12A7209 - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.5 => 0.61.5
npmGlobalPackages:
create-react-native-module: 0.16.0
react-native-cli: 2.0.1

[ferran9908]

Same Issue. How do we circumvent this?

[mikehardy]

That's odd, I have gotten it to work, and while I am currently working through a different apple store rejection it is related to a subsequent network load failing.

Honestly - and this is just supposition and I'm a bit frustrated by it and other issues I and others have with the apple testers - I think their network is crap. I think it's slow, and lossy, and drops connections. It's the only underlying reason I can think of for the variety of failures I see related to App Store approval.

[mikehardy]

Two things, to move on from my frustration comment, and start fixing this:

1. Do not remain on old versions. It does not matter what you need or don't need. Bugfixes always come in new versions.
2. Can you reproduce this on the simulator on your local machine? Stated differently: Can you build and run the example from master on your machine, and it authenticates correctly on your local machine in an ios14 simulator? Because this works for me

[rafaismyname]

Currently facing the same issue.
It was working on simulator before I upgrade from 1.1.2 to 2.0.1. Also I upgraded Xcode from 11 to 12 (as well as iOS to 14).
No console output with any errors.

Update:
I rolled back to 1.1.2 to, hopefully, get it back working on simulators, but it still hangs after authentication and performRequest never gets resolved. I guess by that that the issue might have to do with iOS 14 or Xcode 12.

[gkothe]

Same problem, perform request does not resolve. It gets stuck on the password. I tried to enable and disable "sing in with apple" at sugested here => #117, but made no difference.
IOS 14 e xcode 12.
tried with 1.1.2 and 2.01.
I cant get to the log "appleAuthRequestResponse"

[dburdan]

I also ran into this with iOS 14 but I think the issue is upstream. If I'm logged into iCloud in my iOS 14 simulator and go to icloud.com in Safari, the "Continue with Password" dialog that appears will also fail.

Curious if the icloud.com process fails for you all as well.

[ferran9908]

Same problem, perform request does not resolve. It gets stuck on the password. I tried to enable and disable "sing in with apple" at sugested here => #117, but made no difference.
IOS 14 e xcode 12.
tried with 1.1.2 and 2.01.
I cant get to the log "appleAuthRequestResponse"

From what I've seen, I get the same issue in the iOS 14 Simulator but not in the iOS 13 Simulator with the same code.

But then, I'm able to go past this screen on a physical iOS 14 device.

This makes testing the app harder. Is there any fix for this?

[mikehardy]

UPDATE - this works on iOS16 simulators (finally) so there is hope once Xcode 14 - which includes iOS16 simulator - is out of beta.. Until then:

There is no fix. I reproduce the problem.
For now assume the iOS14 simulator is broken.
The code works on iOS13 simulators. It works on iOS 13 and 14 real devices.

There is nothing we can do, I don't think except wait for a fix.

Simulators from iOS14.0 through iOS 15.x are all broken for sign in with apple.

Instruct app reviewers to use an iOS13 simulator or real device to test it until iOS16 comes out

[anthlasserre]

Hey @se09deluca
Just found what's going wrong. I had the same bug too since a recent upgrade of the lib and RN.
I think some call changed.

Previously I did:

import appleAuth, {
  AppleAuthRequestOperation,
  AppleAuthRequestScope,
  AppleAuthCredentialState,
} from '@invertase/react-native-apple-authentication';
...
const { user, email, fullName } = await appleAuth.performRequest({
  requestedOperation: AppleAuthRequestOperation.LOGIN,
  requestedScopes: [AppleAuthRequestScope.EMAIL, AppleAuthRequestScope.FULL_NAME],
});
...
if (credentialState === AppleAuthCredentialState.AUTHORIZED) {
    // @XXX Waiting Apple Review
}
...

But theses elements are not exported from the lib: [AppleAuthRequestOperation, AppleAuthRequestScope, AppleAuthCredentialState]. I just checked and you have now to pass by appleAuth directly like showed in README.
Implement the Login Process

Like this:

import appleAuth from '@invertase/react-native-apple-authentication';
...
const { user, email, fullName } = await appleAuth.performRequest({
    requestedOperation: appleAuth.Operation.LOGIN,
    requestedScopes: [appleAuth.Scope.EMAIL, appleAuth.Scope.FULL_NAME],
});
...
if (credentialState === appleAuth.State.AUTHORIZED) {
    // @XXX Waiting Apple Review
}
...

[mikehardy]

@anthlasserre I believe you are conflating things. Certainly there were changes from v1.x of this lib to recently released v2.x but I for instance am using TypeScript. I'm not having any export or symbol declaration issues. I am using the symbols correctly because Typescript makes it so there is no other way. Yet I still reproduce the problem on simulator.

[artmerlop]

There is no fix. I reproduce the problem.
For now assume the iOS14 simulator is broken.
The code works on iOS13 simulators. It works on iOS 13 and 14 real devices.

There is nothing we can do, I don't think.

If someone attempted it with Xcode 12.2beta or iOS simulators >=14.1 that would be instructive.

If anyone has anything new to add that will help, otherwise further "me too" posts won't advance the conversation - you can just use reactions if it's affecting you, but it's a known problem at this point

@mikehardy I tested it on Xcode 12.2 beta and iOS 14.2 simulator, same issue.

[artmerlop]

@mikehardy if you download iOS 13.6 simulator on Xcode > 12 you can test everything.