amplify-js: SignInWithApple and Amplify not working user is never authenticated (I have all lastest updates for all)

I’m going to close this issue for now then since you were able to get it working but please re-open and give us any new details if you experience any unstable behavior with Sign In With Apple with either Web or Native at any point during your development.

I will and big thanks to you too! 😃

@rapgithub sorry about the confusion, the federatedSignIn is an overloaded method, by passing different forms of parameters it behaves differently. case1: no parameter - user pool federation Auth.federatedSignIn(). This simply opens up a new page of the user pool “Hosted UI”. case2: directly go to third party login page - still user pool federation Auth.federatedSignIn({provider: 'SignInWithApple'}). The above two cases allow you to federate the customer into the user pool. case3: identity pool federation.

Auth.federatedSignIn(
  'appleid.apple.com',
  {  
     token: APPLE_ID_TOKEN,
     expires_at: expires_at
  },
  user
)

In this case, you need to directly set the federation in identity pool (by clicking the “edit button” of the identity pool). User federate into identity pool directly has nothing to do with user pool. This is also the only path where you get the credentials when the promise gets resolved (e.g. by calling then). You can follow this https://docs.aws.amazon.com/cognito/latest/developerguide/apple.html#set-up-apple-1.javascript to setup apple idp in your identity pool. The above 3 are the only valid syntax, the call does not accept a syntax like

 Auth.federatedSignIn(
          {
            provider: 'SignInWithApple',
            token: accessToken,
            expires_at: expires_at
          }, user)

I would suggest you to try the case3 approach, using appleid.apple.com as the first argument. The error you get back Token is not from a supported identity provider of this identity pool is very likely due to some misconfiguration of the identity pool.

I will try to use 3case and see what happens! if not working and stay saying undefined then the error comes from the cognito user pools somewhere, I doubt it but it is the only thinking now! Also it will be helpful in amplify documentation add how to use apple sign in correctly with auth.federatedSignIn since many are posting wrong info regarding this because the documentation is incomplete now!

Appreciated your time to reply! I will get back to you soon with my test! thanks

Hi there! I found the issue that was not an issue itself was a clear documentation and how to use apple sign in in amplify correctly when using it with mobile or web.

Using this it works only for web!

Auth.federatedSignIn({ provider: 'SignInWithApple' });

my code was always fine this way below but documentation in amazon / amplify is misleading and confusing! they must state to use “appleid.apple.com” that way first thing!

        Auth.federatedSignIn(
          "appleid.apple.com",
          {
            token: identityToken,
            expires_at: expires_at
          }, user)
          .then(credentials => {
...

Second thing in cognito federated identities nobody knows which ID to use for Apple the service ID or Bundle ID. It is confusing in amplify that does not mention which one to use there it only says in a small text in amazon in the link you sent me above that for web use the bundle id while for native apps use the service ID…

So it is misleading to show enter “Apple Services ID” in federated identities -> Authentication providers -> Apple when it must say enter “Apple Services ID (for native iOS apps)” or “Bundle ID (for web)”.

it must say so:

now I get the credentials this way correctly! Credentials are not anymore undefined! the amplify error on the console was misleading to find out the issue!

It will be useful to provide in amplify a clear sample of apple sign in code in javascript as it is explained well for google and facebook with the right information using it this way to bypass the HostedUI and get credentials!

        Auth.federatedSignIn(
          "appleid.apple.com",
          {
            token: identityToken,
            expires_at: expires_at
          }, user)
          .then(credentials => {
...

My error was using the Apple Service ID when it says Apple Service ID in federated identities -> Authentication providers -> Apple and using my Apple Bundle ID solved the issue!

Please provide clear information in amplify for the apple sign in and with the samples! and add Apple Bundle ID / Apple Service ID as shown below will help a lot:

The information must be clear anywhere in amazon documentation online and also in amplify! so nobody spend so many days to find errors that are not there! Many people making mistakes writing wrong information due to missing clear information regarding this topic!

Thanks a lot for your hard work to help solve this issue! in my case was only Use the Bundle ID instead and solved! errors from amplify are not helping too much to find the real reason of errors!

THANKS!

@rapgithub sorry about the confusion, the federatedSignIn is an overloaded method, by passing different forms of parameters it behaves differently.

case1: no parameter - user pool federation Auth.federatedSignIn(). This simply opens up a new page of the user pool “Hosted UI”.

case2: directly go to third party login page - still user pool federation Auth.federatedSignIn({provider: 'SignInWithApple'}).

The above two cases allow you to federate the customer into the user pool.

case3: identity pool federation.

Auth.federatedSignIn(
  'appleid.apple.com',
  {  
     token: APPLE_ID_TOKEN,
     expires_at: expires_at
  },
  user
)

In this case, you need to directly set the federation in identity pool (by clicking the “edit button” of the identity pool). User federate into identity pool directly has nothing to do with user pool.

This is also the only path where you get the credentials when the promise gets resolved (e.g. by calling then).

You can follow this https://docs.aws.amazon.com/cognito/latest/developerguide/apple.html#set-up-apple-1.javascript to setup apple idp in your identity pool.

---

The above 3 are the only valid syntax, the call does not accept a syntax like

 Auth.federatedSignIn(
          {
            provider: 'SignInWithApple',
            token: accessToken,
            expires_at: expires_at
          }, user)

I would suggest you to try the case3 approach, using appleid.apple.com as the first argument. The error you get back Token is not from a supported identity provider of this identity pool is very likely due to some misconfiguration of the identity pool.

thank you I hope it can be solved! I stay tuned for updates! thanks