Auth failed with com.apple.AuthenticationServices.AuthorizationError error 1000 #9

naveendevs · 2019-12-10T17:39:42Z

I'm testing this on a simulator with iOS 13.2.2 (Sign-in with Apple available)

I get the Apple Sign-in button and the auth popup shows up perfectly.

Upon entering password, I get the following error

Error: The operation couldn’t be completed. (com.apple.AuthenticationServices.AuthorizationError error 1000.)
fn@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:10740:45
getCredentialStateForUser@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:136852:53
_callee2$@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:115753:116
tryCatch@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:2040:23
invoke@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:2215:32
tryCatch@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:2040:23
invoke@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:2116:30
http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:2126:21
tryCallOne@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:11791:16
http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:11892:27
_callTimer@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:38368:17
_callImmediatesPass@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:38404:19
callImmediates@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:38623:33
callImmediates@[native code]
__callImmediates@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:11229:35
http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:11006:34
__guard@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:11212:15
flushedQueue@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:11005:21
flushedQueue@[native code]
invokeCallbackAndReturnFlushedQueue@[native code]

Does it even work on simulators? What am I missing here?

Thank you.

The text was updated successfully, but these errors were encountered:

mikehardy · 2019-12-10T18:53:27Z

Works fine on simulators, I tested it a bunch just last night.

1000 is UNKNOWN error: https://github.com/invertase/react-native-apple-authentication/blob/master/docs/enums/_lib_index_d_.rnappleauth.appleautherror.md

Not sure why, but maybe if you build in Xcode and watch the log it will include information?

Including the code in use vs the babel-ized stack would likely help reproduce

naveendevs · 2019-12-10T19:11:41Z

Thank you for the suggestion.

I got this on xcode debug console.

2019-12-11 00:32:40.430577+0530 Lobstr[15774:1573876] RNAppleAuth -> didCompleteWithAuthorization
2019-12-11 00:32:40.432 [info][tid:com.facebook.react.JavaScript] 000990.949c2950b5f74401b58ec16314387a28.1324


2019-12-11 00:34:07.312435+0530 Lobstr[15774:1573876] RNAppleAuth -> didCompleteWithAuthorization
2019-12-11 00:34:07.346546+0530 Lobstr[15774:1575753] [core] Credential State request returned with error: Error Domain=AKAuthenticationError Code=-7001 "(null)"
2019-12-11 00:34:07.382 [info][tid:com.facebook.react.JavaScript] [Error: The operation couldn’t be completed. (com.apple.AuthenticationServices.AuthorizationError error 1000.)]

And I'm using this code from example

  onAppleButtonPress = async () => {
    console.log('LOGGING')
    const requestOptions = {
      requestedOperation: AppleAuthRequestOperation.LOGIN,
      requestedScopes: [AppleAuthRequestScope.EMAIL, AppleAuthRequestScope.FULL_NAME],
    };
    const { user } = await appleAuth.performRequest(requestOptions);
    console.log(user)

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

    try {
      const credentialState = await appleAuth.getCredentialStateForUser(user);
      if (credentialState === AppleAuthCredentialState.AUTHORIZED) {
      }
    } catch (error) {
      console.log(error)
      if (error.code === AppleAuthError.CANCELED) {
      }
      if (error.code === AppleAuthError.FAILED) {
      }
      if (error.code === AppleAuthError.INVALID_RESPONSE) {
      }
      if (error.code === AppleAuthError.NOT_HANDLED) {
      }
      if (error.code === AppleAuthError.UNKNOWN) {
      }
    }  
  }

Found this on Apple Developer forums, but looks like of no use.
https://forums.developer.apple.com/thread/122983

mikehardy · 2019-12-10T19:19:19Z

Can you re-try this without the requested operation? I am using it successfully, but without the requested operation, and I think the example is the same, and I recall someone else having a related problem? invertase/react-native-firebase#2979 (comment)

Although it didn't seem to help there, so I assign low-probability of fix with that.

For me I am integrating with react-native-firebase and I do not do getCredentialState, I just feed it directly to firebase and they work with the credential. Is it necessary to call that 🤔

The example does it https://github.com/invertase/react-native-apple-authentication/blob/master/example/app.js#L38 - can you reproduce with the example?

naveendevs · 2019-12-10T20:19:55Z

Tried without requestedOperation, didn't work.

What do you feed to firebase? I believe, a token is required from Apple Sign-in call to authenticate.

mikehardy · 2019-12-10T20:24:19Z

No idea if this will be applicable, but here's the ridiculously-too-big method I use, works for me?

  async appleSignIn(link?: boolean): Promise<boolean> {
    try {
      const appleCredential = await AppleAuth.performRequest({
        requestedOperation: AppleAuthRequestOperation.LOGIN,
        requestedScopes: [AppleAuthRequestScope.EMAIL, AppleAuthRequestScope.FULL_NAME],
      });

      console.log(
        'UserStore::appleSignIn - user result is:',
        JSON.stringify(appleCredential, null, 2)
      );

      // FIXME we should really store the uid we get back, looks like:
      //   "uid": "000420.fa782337956f441eb0e23e43d8c337b5.0503" and is all we get in future

      this.removeUserChangeListener();

      if (appleCredential.email) {
        const providers = await this.getProvidersForEmail(appleCredential.email);
        console.log(
          'UserStore::appleSignIn - got providers for email: ',
          JSON.stringify(providers, null, 2)
        );
        // if google.com is not in the providers, it is first login via google.
        let appleProvider = false;
        let passwordProvider = false;
        for (let i = 0; i < providers.length; i++) {
          if (providers[i] === 'apple.com') {
            appleProvider = true;
          } else if (providers[i] === 'password') {
            passwordProvider = true;
          }
        }

        // If there are providers, but not apple, google actually just automatically does it right.
        if (providers.length !== 0 && !appleProvider) {
          if (passwordProvider) {
            console.log(
              'UserStore::appleSignIn -  other providers but google auto-connects if it is password provider'
            );
          } else {
            this.handleCredentialInUse();
            return Promise.resolve(false);
          }
        }

        // If this is the first time we are seeing apple, handle apple privacy
        // Apple has specific requirements before linking non-anonymous
        // FIXME this may be a problem though as email might not come through again?
        // do we need to rely on uid here?
        if (!appleProvider) {
          console.log('UserStore::appleSignIn - verifying user is okay with apple + non-anonymous');
          const choice = await AlertAsync(
            I18NService.translate('LoginApplePrivacyTitle'),
            I18NService.translate('LoginApplePrivacyText'),
            [
              {
                text: I18NService.translate('Cancel'),
                onPress: () => 'Cancel',
              },
              {
                text: 'OK',
                onPress: () => 'OK',
              },
            ],
            {
              cancelable: false,
              onDismiss: () => 'Cancel',
            }
          );
          if (choice === 'Cancel') {
            console.log(
              'UserStore::appleSignIn - user does not want to link apple id + non-anonymous'
            );
            return Promise.resolve(false);
          }
          console.log(
            'UserStore::appleSignIn - user is just fine linking apple id + non-anonymous'
          );
        }
        // If there are no other providers we should ask if they already have an account
        if (
          providers.length === 0 &&
          (!firebase.auth().currentUser?.providerData ||
            firebase.auth().currentUser?.providerData.length === 0)
        ) {
          console.log('UserStore::appleSignIn - no other providers. See if they are sure');
          const choice = await AlertAsync(
            I18NService.translate('LoginFirstLoginTitle'),
            I18NService.translate('LoginFirstLoginText'),
            [
              {
                text: I18NService.translate('LoginFirstLoginOtherAccountsButton'),
                onPress: () => 'Other Accounts',
              },
              {
                text: I18NService.translate('LoginFirstLoginPleaseContinueButton'),
                onPress: () => 'Please Continue',
              },
            ],
            {
              cancelable: false,
              onDismiss: () => 'Please Continue',
            }
          );
          if (choice === 'Other Accounts') {
            console.log('UserStore::appleSignIn - user wants to handle other accounts');
            return Promise.resolve(false);
          }
          console.log(
            'UserStore::appleSignIn - user is just fine continuing and creating new account'
          );

          this.setIsNewUser(true);
        }
      } else {
        console.log('UserStore::appleSignIn - no email present, not first apple sign in?');
      }

      // create a new firebase credential with the token
      const credential = firebase.auth.AppleAuthProvider.credential(
        appleCredential.identityToken,
        appleCredential.nonce
      );
      console.log('UserStore::appleSignIn - credential is', JSON.stringify(credential, null, 2));
      let firebaseUserCredential;
      if (!link) {
        // login with credential
        firebaseUserCredential = await firebase.auth().signInWithCredential(credential);
        Analytics.setAnalyticsUser(firebaseUserCredential.user.uid); // TODO, set our own ID?
        Analytics.setAnalyticsUserProperties({ email: firebaseUserCredential.user.email });
        Analytics.analyticsEvent('successAppleSignIn');
      } else {
        if (!firebase.auth().currentUser) {
          return Promise.resolve(false);
        }
        firebaseUserCredential = await firebase.auth().currentUser?.linkWithCredential(credential);
        Analytics.setAnalyticsUser(firebase.auth().currentUser!.uid); // TODO, set our own ID?
        Analytics.setAnalyticsUserProperties({ email: firebase.auth().currentUser!.email });
        Analytics.analyticsEvent('successAppleLink');
      }

      console.log(
        'UserStore::appleSignIn - firebaseCredential was',
        JSON.stringify(firebaseUserCredential)
      );
      this.userChangedHandler(
        firebaseUserCredential!.user,
        firebaseUserCredential!.additionalUserInfo
      );
      return Promise.resolve(true);
    } catch (error) {
      if (error.code === 'ERR_CANCELLED') {
        // user cancelled the login flow
        console.log('UserStore::appleSignIn - user cancelled');
      } else if (error.code === AppleAuthError.CANCELED) {
        // user cancelled the login flow
        console.log('UserStore::appleSignIn - authentication request failed');
      } else if (
        error.code === 'auth/email-already-in-use' ||
        error.code === 'auth/credential-already-in-use'
      ) {
        console.log('UserStore::appleSignIn - email already in use, instruct on unlink/delete');
        this.handleAccountInUse();
      } else if (error.code === 'auth/account-exists-with-different-credential') {
        this.handleCredentialInUse();
      } else {
        // some other error happened
        console.log(
          'UserStore::appleSignIn - unknown error?' + error,
          JSON.stringify(error, null, 2)
        );
        RX.Alert.show(
          I18NService.translate('ConnectedAccountsConnectionError'),
          I18NService.translate(error.code)
        );
      }
    } finally {
      this.addUserChangedListener();
    }

    return Promise.resolve(false);
  }

eduzera · 2019-12-11T19:45:06Z

on my simulator i got this AuthorizationError error 1000 but on device it's worked fine

colloquet · 2019-12-12T16:53:29Z

I had the same error, turns out I did not follow the firebase documentation and did not configure Sign In with Apple. After following the instructions it's working for me on both simulator and device.
https://firebase.google.com/docs/auth/ios/apple?authuser=0#configure_sign_in_with_apple

mikehardy · 2019-12-12T17:50:51Z

@colloquet I can't believe you missed one of the 2,431 things to configure in apple + firebase developer console for it to work 😅 (joking of course)

mikehardy · 2019-12-14T18:08:14Z

I got this on the Simulator just now when I attempted apple sign-in for the first time and did not have my apple id set up. It set up the ID correctly but when I went back to the app it did not actually attempt sign-in, it just threw the 1000 error, then I tapped the sign-in button again and it worked. So maybe worth re-trying once when you see this error? unless it maps to other cases - test first of course

dclipca · 2019-12-16T21:37:36Z

I get the same error:
Error: The operation couldn’t be completed. (com.apple.AuthenticationServices.AuthorizationError error 1000.)
I'm testing the app in a simulator. None of the proposed fixes worked out.

havinhthai · 2019-12-17T06:24:59Z

Same error here, I'm reproduce the example without Firebase here but It didn't work.

dclipca · 2019-12-17T13:15:37Z

If the error appears after you perform the login then try to use a real device. It might be the case that it doesn't work on a simulator.

phuoc-insignia · 2019-12-18T07:38:08Z

If the error appears after you perform the login then try to use a real device. It might be the case that it doesn't work on a simulator.

You're right. It works on a real device

dclipca · 2019-12-18T21:55:25Z

If the error appears after you perform the login then try to use a real device. It might be the case that it doesn't work on a simulator.

You're right. It works on a real device

Thank you for confirming this. It seems I will have to get a real device from somewhere.

mikehardy · 2019-12-18T22:58:54Z

Just commenting to say it actually works for me in a simulator? But only the second time - the first time the simulator takes me through the whole "set up your iCloud account on this device" flow, then goes back to the app and I get error 1000. Then (with a valid iCloud account setup), apple sign in works just fine 🤷‍♂

pacozaa · 2019-12-19T09:25:09Z

Got the same error

dclipca · 2019-12-19T18:17:01Z

Just commenting to say it actually works for me in a simulator? But only the second time - the first time the simulator takes me through the whole "set up your iCloud account on this device" flow, then goes back to the app and I get error 1000. Then (with a valid iCloud account setup), apple sign in works just fine 🤷‍♂

I get the error 1000 no matter how many times I try (after the "set up your iCloud account on this device"). Also, I checked the auth on a real device and it works.

pacozaa · 2019-12-20T05:50:40Z

I fix it by configuration in xcode.

TARGETS>Signing & Capabilities>+Capability then search sign in then add it. Problem solved!

@colloquet suggestion is on point for me. Thank you :)

alexxsanchezm · 2019-12-20T18:11:11Z

Yes, In the case of @pacozaa and mine, I was missing adding the SingIn capabilities. Since you have to update XCode to be able to integrate with Apple SignIn. Is not obvious you need to click the + icon on the top to add such capability, In previous versions the capabilities are at glance you just need to check/uncheck.
This time you need to hit + at the top and then a dialog pops up and double click to add any capability, in this case SignIn with Apple.

havinhthai · 2019-12-20T18:12:16Z

@alexxsanchezm Can you test your app on simulator?

havinhthai · 2019-12-20T19:21:10Z

My problem is I only add Sign In Capability to release version, so I can't test on development version.

I fixed it by add Sign In Capability to both of versions.

alexxsanchezm · 2019-12-20T19:43:37Z

My problem is I only add Sign In Capability to release version, so I can't test on development version.

I fixed it by add Sign In Capability to both of versions.

Yes, it works on the simulator as well.
What do you mean by

both versions

havinhthai · 2019-12-20T20:24:12Z

I added Sign In Capability to debug and release version.

dclipca · 2019-12-20T22:20:20Z

I have the same error (I get the error 1000 no matter how many times I try (after the "set up your iCloud account on this device"). Also, I checked the auth on a real device and it works.) but I have the Sign In Capability both in Debug and Release versions. I am not using Firebase.

colloquet · 2019-12-21T04:06:12Z

This is what I have done to fix the problem, it might be helpful in your case as well:

If you have a developer account, under Certificates, Identifiers & Profiles -> Identifiers -> YOUR_APP_BUNDLE_ID

After doing this you might have to update your Provisioning Profile for both development and distribution as well.

In Xcode, make sure Sign in with Apple is enabled:

Hope this helps.

amitbravo · 2020-01-09T07:34:39Z

I am testing on real device since beginning
I am using firebase and I am having same message. no hope.
"react": "16.9.0",
"react-native": "0.61.5",
"@invertase/react-native-apple-authentication": "^0.1.1",
"react-native-firebase": "^5.6.0",

Xcode Version 11.2.1 (11B500)
Device : iphone SE , OS 13.3
OSX : Catalina 10.15.2

appleAuth.isSupported returns true though.

Firebase

I cleaned build folder, deleted drived data folder, reinstalled app into the device. no luck

colloquet · 2020-01-12T01:47:18Z

@amitbravo I noticed your screenshot only show you have added Sign In with Apple capability for your release build, can you check if it is also enabled under “All” or “Debug”?

amitbravo · 2020-01-13T09:39:47Z

@colloquet thank you. it was unchecked at debug, its added and now working fine.

RodolfoGS · 2020-01-17T03:48:19Z

@amitbravo I noticed your screenshot only show you have added Sign In with Apple capability for your release build, can you check if it is also enabled under “All” or “Debug”?

Thank you, I had the same issue.

Jalson1982 · 2020-02-04T10:14:42Z

Anybody has an issue on IOS Simulator like this. I have pop up open asking me to choose should I share my email or hide and then button Continue with a password. On next screen I enter password from my apple ID and nothing happens. Is something wrong on my side or it is simulator issue?

goul4rt · 2020-08-17T14:04:59Z

After banging my head against this for 2 hours, I figured out what is happening (at least for me).
I was also having the problem where apple sign in was not working in the simulator, but was working on the device in debug and release builds.

I tried reseting my simulator, and signed in with iCloud again through settings; no luck.
I tried resetting again and signed in to iCloud with another apple ID and it worked.
I reset a 3rd time and signed in to iCloud with my original apple ID and it didn't work.

So..... I went to https://appleid.apple.com/account/manage and scrolled down to where it shows my Devices that are signed in with this ID. I clicked on "Simulator" and chose "Remove from Account".

I went back to my simulator, tried to signin with apple and it prompted me for the 2-factor code. I entered it, then my password, and it worked.

So the problem seems to have been the association between my Simulator device and my Apple ID. I have no idea what could have caused this -- Time, too many signins to different devices when testing, Entropy, Chaos Theory or perhaps it's just Apple's way of keeping its faithful app developers on our toes :)

This works fine. Help me a lot, ty!

mikehardy · 2020-08-17T15:45:32Z

@SnowLew can you please propose a docs PR (you can do it just using the web UI on github) to save everyone else the trouble 🙏 🙏

Very interesting @dchersey - thanks for reporting that! Could you hit the edit button (top right corner) on the README and maybe add it to this section? https://github.com/invertase/react-native-apple-authentication/blob/master/README.md#troubleshouting - this one gets people a lot!

lorenjohnson · 2020-08-17T21:34:37Z

After banging my head against this for 2 hours, I figured out what is happening (at least for me).
I was also having the problem where apple sign in was not working in the simulator, but was working on the device in debug and release builds.

I tried reseting my simulator, and signed in with iCloud again through settings; no luck.
I tried resetting again and signed in to iCloud with another apple ID and it worked.
I reset a 3rd time and signed in to iCloud with my original apple ID and it didn't work.

So..... I went to https://appleid.apple.com/account/manage and scrolled down to where it shows my Devices that are signed in with this ID. I clicked on "Simulator" and chose "Remove from Account".

I went back to my simulator, tried to signin with apple and it prompted me for the 2-factor code. I entered it, then my password, and it worked.

So the problem seems to have been the association between my Simulator device and my Apple ID. I have no idea what could have caused this -- Time, too many signins to different devices when testing, Entropy, Chaos Theory or perhaps it's just Apple's way of keeping its faithful app developers on our toes :)

THANK YOU! Removing and re-adding the Simulator on my Apple Developer account was the solution for me as well.

goul4rt · 2020-08-26T19:14:40Z

@SnowLew can you please propose a docs PR (you can do it just using the web UI on github) to save everyone else the trouble 🙏 🙏

Very interesting @dchersey - thanks for reporting that! Could you hit the edit button (top right corner) on the README and maybe add it to this section? https://github.com/invertase/react-native-apple-authentication/blob/master/README.md#troubleshouting - this one gets people a lot!

I will write doc for this error and request a PR. thank you!

Edit: @mikehardy I've send a PR adding some solutions for this issue. (readme)

MandipGiri · 2020-09-02T12:02:57Z

After banging my head against this for 2 hours, I figured out what is happening (at least for me).
I was also having the problem where apple sign in was not working in the simulator, but was working on the device in debug and release builds.

I tried reseting my simulator, and signed in with iCloud again through settings; no luck.
I tried resetting again and signed in to iCloud with another apple ID and it worked.
I reset a 3rd time and signed in to iCloud with my original apple ID and it didn't work.

So..... I went to https://appleid.apple.com/account/manage and scrolled down to where it shows my Devices that are signed in with this ID. I clicked on "Simulator" and chose "Remove from Account".

I went back to my simulator, tried to signin with apple and it prompted me for the 2-factor code. I entered it, then my password, and it worked.

So the problem seems to have been the association between my Simulator device and my Apple ID. I have no idea what could have caused this -- Time, too many signins to different devices when testing, Entropy, Chaos Theory or perhaps it's just Apple's way of keeping its faithful app developers on our toes :)

This worked for after trying so many solutions and enabling everything as per docs. Thanks

ryansaam · 2020-10-16T18:58:42Z

Just a note for iOS 14+ and xcode 12+ as of now this seems to be a big issue.
https://developer.apple.com/forums/thread/651533

I'm currently having this problem so I'm downgrading to iOS 13.5 sim for testing.

avbeladiya · 2020-10-20T08:22:18Z

Working on my iPad with ios 14 and xcode 12 but not on mobile devices when i run with diawi and also from testflight.

avbeladiya · 2020-10-20T08:24:14Z

@ryansaam does downgrading ios to 13.5 works ?

mikehardy · 2020-10-20T14:09:26Z

works on every ios14 iPhone real device I've tested it on. 11, SE, 7
I don't know what diawi is but you need to test it on a real device you are holding in your hands I think.

ryansaam · 2020-10-20T14:38:53Z

@avbeladiya I also don't know what diawi is but I can confirm testing in a simulator running iOS 13.5 works for me. The problem also seems to be that if you upload a build to App Store Connect (using sign in with apple) they're rejecting it. So I'm also uploading iOS 13.5 builds. However an unrelated problem is messing that up too https://developer.apple.com/forums/thread/118719

Singh-KiaTec · 2020-10-23T15:36:24Z

ICOULD needs to logged in aswell. . Else you might always see error 1000

ZaikinaEvgeniya-2 · 2020-12-25T07:54:23Z

This happen also if you use not right signature from you apple (password)

CallmeKingsley · 2021-01-31T13:07:52Z

you guys might need to do this also https://dev.to/aryaminus/how-to-sign-in-with-apple-on-react-and-react-native-using-node-5g0b

EnginYilmaz · 2021-05-29T17:37:04Z

Anyone suffer from this problem like me can use iOS version 13.5 and iPhone 11 to overcome this problem, starting React native debugging with this command. Offcourse other versions may work but I tested and confirm the below command.
npx react-native run-ios --simulator="iPhone 11 (13.5)"

iqbalhusen · 2021-07-12T15:10:44Z

In my case, the "Sign In with Apple" capability is missing. Sorry, I am new to iOS development. What do I need to do in order to make this capability available on my app?

EnginYilmaz · 2021-07-12T15:16:10Z

I am assuming you are also using invertase library for adding sign up - sign in capability with React Native for iOS development. I would follow this document to accomplish this task https://rnfirebase.io/#3-ios-setup to install and https://rnfirebase.io/auth/social-auth#apple to use it. I hope it helps.

iqbalhusen · 2021-07-12T15:20:13Z

I am assuming you are also using invertase library for adding sign up - sign in capability with React Native for iOS development. I would follow this document to accomplish this task https://rnfirebase.io/auth/social-auth#apple hope it helps.

Yes, I am using the library "@invertase/react-native-apple-authentication": "^2.1.2"

Sorry but the link you provided doesn't mention anything about the problem i am mentioning. Also, I am not using Firebase.

EnginYilmaz · 2021-07-12T15:20:53Z

I re-visited the link yes. Sorry for the delay. But Invertase is a library for adapting firebase easily with React Native

MuhammadAbdullah54321 · 2022-03-15T19:30:42Z

Anybody has an issue on IOS Simulator like this. I have pop up open asking me to choose should I share my email or hide and then button Continue with a password. On next screen I enter password from my apple ID and nothing happens. Is something wrong on my side or it is simulator issue?

I am still facing this issue
I have done all the configuration required as suggested above ... added sign in capability as well in both debug and release mode

I am using iOS 14.4 simulator

mikehardy · 2022-03-15T20:36:35Z

Hey @MuhammadAbdullah54321 👋 - nothing you do on an ios14 simulator is valid unfortunately. ios13 is the only simulator I've seen work with apple sign in. Real devices work. The issue here pinned to the repo issue list has it #141

khagesh · 2022-06-20T11:20:04Z

Anybody has an issue on IOS Simulator like this. I have pop up open asking me to choose should I share my email or hide and then button Continue with a password. On next screen I enter password from my apple ID and nothing happens. Is something wrong on my side or it is simulator issue?

@Jalson1982 Were you able to fix this issue?

mikehardy · 2022-06-20T17:31:11Z

@khagesh there is no fix. You must use ios13 simulator if you test this on the simulator

khagesh · 2022-06-21T08:57:58Z

@mikehardy ok. Sorry for commenting on closed thread. I thought the issue for continue with password keep loading is separate from what was being discussed above. I will use ios13 simulator

WinfoodDev · 2022-06-28T20:42:38Z

I'm using the emulator and I'm having the same problem as @khagesh. As soon as I enter the Apple ID and password, I click Confirm, the app simply does not advance and a loading appears as if it was doing some process. The IOS version options I have on my Mac is 12.4 or 15.4. I tried to use 13.0, but I didn't find this version to use in the simulator to test on the iPhone

mikehardy · 2022-06-28T21:24:00Z

@WinfoodDev

I tried to use 13.0, but I didn't find this version to use in the simulator to test on the iPhone

You have to manually download it. It's inside Xcode preferences (then maybe make a new simulator definition using it stackoverflow can probably help you)

You can also try the Xcode 14 beta, the iOS 16 emulators in there work (finally!)

WinfoodDev · 2022-06-29T14:20:44Z

Thank you very much, @mikehardy ! It finally worked, after more than a week of trying to find a solution! My client was already starting to freak out hahaha... Now I just hope it works on a real device haha 😄

mikehardy · 2022-06-29T14:30:28Z

As there is one day left before notoriously "we'll reject your app for almost anything, and kind of randomly" apple app reviewers start applying this criteria - do pay attention to it as well - #282 - I haven't even handled this one myself, it looks generally like a big mess 😩

jeffala · 2023-06-19T13:50:06Z

@colloquet Thank you for much, my problem was that the capability was not added for debug. THANK YOU!

Ernestanior · 2023-09-07T04:01:59Z

If you are developing, make sure you also need to turn on "Sign in with Apple" in debug since turn on in ALL only work in release.

bell-steven mentioned this issue Aug 24, 2020

doc: Update troubleshooting error 1000 #131

Merged

Auth failed with com.apple.AuthenticationServices.AuthorizationError error 1000 #9

Auth failed with com.apple.AuthenticationServices.AuthorizationError error 1000 #9

Comments

naveendevs commented Dec 10, 2019 • edited Loading

mikehardy commented Dec 10, 2019

naveendevs commented Dec 10, 2019

mikehardy commented Dec 10, 2019

naveendevs commented Dec 10, 2019

mikehardy commented Dec 10, 2019

eduzera commented Dec 11, 2019

colloquet commented Dec 12, 2019

mikehardy commented Dec 12, 2019

mikehardy commented Dec 14, 2019

dclipca commented Dec 16, 2019

havinhthai commented Dec 17, 2019

dclipca commented Dec 17, 2019

phuoc-insignia commented Dec 18, 2019

dclipca commented Dec 18, 2019

mikehardy commented Dec 18, 2019

pacozaa commented Dec 19, 2019

dclipca commented Dec 19, 2019 • edited Loading

pacozaa commented Dec 20, 2019

alexxsanchezm commented Dec 20, 2019

havinhthai commented Dec 20, 2019

havinhthai commented Dec 20, 2019

alexxsanchezm commented Dec 20, 2019

havinhthai commented Dec 20, 2019

dclipca commented Dec 20, 2019 • edited Loading

colloquet commented Dec 21, 2019 • edited Loading

amitbravo commented Jan 9, 2020 • edited Loading

colloquet commented Jan 12, 2020

amitbravo commented Jan 13, 2020

RodolfoGS commented Jan 17, 2020

Jalson1982 commented Feb 4, 2020

goul4rt commented Aug 17, 2020

mikehardy commented Aug 17, 2020

lorenjohnson commented Aug 17, 2020

goul4rt commented Aug 26, 2020 • edited Loading

MandipGiri commented Sep 2, 2020

ryansaam commented Oct 16, 2020

avbeladiya commented Oct 20, 2020

avbeladiya commented Oct 20, 2020

mikehardy commented Oct 20, 2020 • edited Loading

ryansaam commented Oct 20, 2020 • edited Loading

Singh-KiaTec commented Oct 23, 2020

ZaikinaEvgeniya-2 commented Dec 25, 2020

CallmeKingsley commented Jan 31, 2021

EnginYilmaz commented May 29, 2021 • edited Loading

iqbalhusen commented Jul 12, 2021

EnginYilmaz commented Jul 12, 2021 • edited Loading

iqbalhusen commented Jul 12, 2021

EnginYilmaz commented Jul 12, 2021 • edited Loading

MuhammadAbdullah54321 commented Mar 15, 2022

mikehardy commented Mar 15, 2022

khagesh commented Jun 20, 2022

mikehardy commented Jun 20, 2022

khagesh commented Jun 21, 2022

WinfoodDev commented Jun 28, 2022

mikehardy commented Jun 28, 2022 • edited Loading

WinfoodDev commented Jun 29, 2022

mikehardy commented Jun 29, 2022

jeffala commented Jun 19, 2023

Ernestanior commented Sep 7, 2023

naveendevs commented Dec 10, 2019 •

edited

Loading

dclipca commented Dec 19, 2019 •

edited

Loading

dclipca commented Dec 20, 2019 •

edited

Loading

colloquet commented Dec 21, 2019 •

edited

Loading

amitbravo commented Jan 9, 2020 •

edited

Loading

goul4rt commented Aug 26, 2020 •

edited

Loading

mikehardy commented Oct 20, 2020 •

edited

Loading

ryansaam commented Oct 20, 2020 •

edited

Loading

EnginYilmaz commented May 29, 2021 •

edited

Loading

EnginYilmaz commented Jul 12, 2021 •

edited

Loading

EnginYilmaz commented Jul 12, 2021 •

edited

Loading

mikehardy commented Jun 28, 2022 •

edited

Loading