# Instructions for apple sign in not clear enough, receiving an error

**URL:** <https://community.auth0.com/t/instructions-for-apple-sign-in-not-clear-enough-receiving-an-error/32512>\
**Category:** Get Help\
**Tags:** auth0\
**Created:** [October 17, 2019, 9:04pm UTC](https://community.auth0.com/t/instructions-for-apple-sign-in-not-clear-enough-receiving-an-error/32512 "2019-10-17T21:04:17Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![jose1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jose1/32/16854_2.png) [@jose1](https://community.auth0.com/u/jose1)\
**Post date:** [October 17, 2019, 9:04pm UTC](https://community.auth0.com/t/instructions-for-apple-sign-in-not-clear-enough-receiving-an-error/32512/1 "2019-10-17T21:04:17Z")

</div>

I’ve followed the instructions here:

> <https://github.com/auth0/docs/blob/f527c834751cbded45568f1f97b2ccba035bec37/articles/connections/apple-setup.md>

and on the auth0 website to setup apple sign in, however how iOS client keeps receiving this error:

**Exchange Failed: Grant type urn:ietf:params:oauth:grant-type:token-exchange with subject\_token\_type [http://auth0.com/oauth/token-type/apple-authz-code](http://auth0.com/oauth/token-type/apple-authz-code) is not enabled for this client**

I also want to know, if the Web Domain we should be providing apple is the custom domain that should be pointing to {app}.auth0.com.

---

<div class="post-metadata">

**Author:** ![jose1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jose1/32/16854_2.png) [@jose1](https://community.auth0.com/u/jose1)\
**Post date:** [October 17, 2019, 9:09pm UTC](https://community.auth0.com/t/instructions-for-apple-sign-in-not-clear-enough-receiving-an-error/32512/2 "2019-10-17T21:09:51Z")

</div>

I’m also curious to know the approach people took to verify their custom domain with apple… this means most of the time having login downtime while you unpoint the domain from auth0 and verify the file etc

---

<div class="post-metadata">

**Author:** ![ron.hsu](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ron.hsu/32/12835_2.png) [@ron.hsu](https://community.auth0.com/u/ron.hsu)\
**Post date:** [October 17, 2019, 9:21pm UTC](https://community.auth0.com/t/instructions-for-apple-sign-in-not-clear-enough-receiving-an-error/32512/3 "2019-10-17T21:21:06Z")

</div>

You should provide the custom domain. Also, most if not all of the callback url settings in the Auth0 dashboard accept multiple urls, so you shouldn’t have to un-point anything.

---

<div class="post-metadata">

**Author:** ![jose1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jose1/32/16854_2.png) [@jose1](https://community.auth0.com/u/jose1)\
**Post date:** [October 17, 2019, 9:27pm UTC](https://community.auth0.com/t/instructions-for-apple-sign-in-not-clear-enough-receiving-an-error/32512/4 "2019-10-17T21:27:19Z")

</div>

Thanks Ron, however, I’m talking about the custom domain. Our domain is currently pointing to auth0, in order to verify with apple we have to unpoint it and serve the file, during which time the login is unusable. Does that make sense?

But yup, that’s what I used anyways, the custom domain, and getting this not very helpful error ☹

---

<div class="post-metadata">

**Author:** ![ron.hsu](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ron.hsu/32/12835_2.png) [@ron.hsu](https://community.auth0.com/u/ron.hsu)\
**Post date:** [October 17, 2019, 9:38pm UTC](https://community.auth0.com/t/instructions-for-apple-sign-in-not-clear-enough-receiving-an-error/32512/5 "2019-10-17T21:38:49Z")

</div>

Hm, I don’t think I follow. I don’t recall having to un-point anything or any kind of downtime. The verification I believe is independent of the login url settings.

What setting are you changing for the re-pointing?

---

<div class="post-metadata">

**Author:** ![jose1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jose1/32/16854_2.png) [@jose1](https://community.auth0.com/u/jose1)\
**Post date:** [October 17, 2019, 9:54pm UTC](https://community.auth0.com/t/instructions-for-apple-sign-in-not-clear-enough-receiving-an-error/32512/6 "2019-10-17T21:54:04Z")

</div>

No settings, just the custom domain is a CNAME pointing to the auth0 domain, I don’t see how you’d have that and at the same time use your domain in a server to serve the file 🙂

But I don’t mean to distract the post from its original issue, the weird error

---

<div class="post-metadata">

**Author:** ![jose1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jose1/32/16854_2.png) [@jose1](https://community.auth0.com/u/jose1)\
**Post date:** [October 20, 2019, 7:01pm UTC](https://community.auth0.com/t/instructions-for-apple-sign-in-not-clear-enough-receiving-an-error/32512/7 "2019-10-20T19:01:52Z")

</div>

Does anyone have any idea? Should I send a support ticket?

---

<div class="post-metadata">

**Author:** ![luisjesus](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/luisjesus/32/14170_2.png) [@luisjesus](https://community.auth0.com/u/luisjesus)\
**Post date:** [October 23, 2019, 3:42pm UTC](https://community.auth0.com/t/instructions-for-apple-sign-in-not-clear-enough-receiving-an-error/32512/8 "2019-10-23T15:42:44Z")

</div>

I’m having the same issue, did you manage to fix it @jose1?

---

<div class="post-metadata">

**Author:** ![jose1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jose1/32/16854_2.png) [@jose1](https://community.auth0.com/u/jose1)\
**Post date:** [October 24, 2019, 8:28pm UTC](https://community.auth0.com/t/instructions-for-apple-sign-in-not-clear-enough-receiving-an-error/32512/9 "2019-10-24T20:28:32Z")

</div>

@luisjesus nope, not yet, still not able to implement this… noone seems to know what to do

---

<div class="post-metadata">

**Author:** ![david.laroue](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/david.laroue/32/13072_2.png) [@david.laroue](https://community.auth0.com/u/david.laroue)\
**Post date:** [October 30, 2019, 6:27pm UTC](https://community.auth0.com/t/instructions-for-apple-sign-in-not-clear-enough-receiving-an-error/32512/10 "2019-10-30T18:27:32Z")

</div>

Hey [jose1](http://community.auth0.com/u/jose1)

We ran into the same issue and discovered there is a different set of configurations you need to enable for Native iOS users going through this flow.

If you go to Applications → (Your iOS Application client) → scroll to the bottom to `Show Advanced Settings` → and open up the `Device settings` tab you’ll see a toggle to enable native flow for apple sign in. This should do the trick, you’ll need to provide the Team and App Id.

 ![31%20AM](https://global.discourse-cdn.com/auth0/original/3X/d/5/d5f37ee7b122a688f9f418d6045a69cabd16b3bf.png)

---

<div class="post-metadata">

**Author:** ![dev41](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dev41/32/12814_2.png) [@dev41](https://community.auth0.com/u/dev41)\
**Post date:** [March 16, 2020, 3:20pm UTC](https://community.auth0.com/t/instructions-for-apple-sign-in-not-clear-enough-receiving-an-error/32512/11 "2020-03-16T15:20:15Z")

</div>

I have the same issue.

Following the instructions here [Add Sign In with Apple to Native iOS Apps](https://auth0.com/docs/connections/apple-siwa/add-siwa-to-native-app) and also successfully testing the connection as described here [https://auth0.com/docs/connections/apple-siwa/test-siwa-connection](https://auth0.com/docs/connections/apple-siwa/test-siwa-connection) I can’t get it running inside of my Ionic app following this documentation: [Authentication API Explorer](https://auth0.com/docs/api/authentication#token-exchange-for-native-social)

I always get a 401

```
{
    "error": "access_denied",
    "error_description": "Unauthorized"
}

```

The logs do not include any usefull information and I’m kindof stuck now.

---

<div class="post-metadata">

**Author:** ![Odysseas](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/odysseas/32/17418_2.png) [@Odysseas](https://community.auth0.com/u/Odysseas)\
**Post date:** [July 17, 2020, 9:05am UTC](https://community.auth0.com/t/instructions-for-apple-sign-in-not-clear-enough-receiving-an-error/32512/12 "2020-07-17T09:05:09Z")

</div>

Hi all, I am stuck at the same spot as @dev41

@dev41 Did you manage to solve it?

Connection testing is successful.

I always get a 401 when this is included in headers: headers: { ‘content-type’: ‘application/x-www-form-urlencoded’ }, but a 403 when the previous is not included.

I request that the Auth0 support help us a bit more, cause the error we get is too generic and cannot help in solving this issue. Auth0 should have a much better support, especially on paid plans!

Thanks.

---

<div class="post-metadata">

**Author:** ![piercifani](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/piercifani/32/13242_2.png) [@piercifani](https://community.auth0.com/u/piercifani)\
**Post date:** [October 30, 2020, 10:06am UTC](https://community.auth0.com/t/instructions-for-apple-sign-in-not-clear-enough-receiving-an-error/32512/13 "2020-10-30T10:06:56Z")

</div>

Anyone figure this one out?

---

<div class="post-metadata">

**Author:** ![JAYSH89](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jaysh89/32/55513_2.png) [@JAYSH89](https://community.auth0.com/u/JAYSH89)\
**Post date:** [March 9, 2024, 4:11pm UTC](https://community.auth0.com/t/instructions-for-apple-sign-in-not-clear-enough-receiving-an-error/32512/14 "2024-03-09T16:11:47Z")

</div>

Anyone managed to find a solution for this. I am running in to the same issue, not being able to exchange the authorization code for Auth0 tokens.
