Still having Apple Authentication error #2764
Comments
|
I opened this issue to update the workaround.md expo/fyi#187 |
|
Sorry I missed your issue from yesterday. I do think I'm having the same one so we can close this if its a duplicate. I let Expo folks decide. And actually I was able to find an iOS device to log into but it would be nice to have the SMS fixed so you don't have to use a work specific device. Thanks! |
|
Tried the workaround still no luck :( |
|
Quick reminder that you can use a mac as your Apple device too. Again, we were able to reproduce this error and fixed against the repro so we no longer have any ability to test against the problem and it is seemingly fixed. I'd recommend clearing your local caches and trying again. #2698 (comment) |
Do you mean fixed with a device or fixed with SMS. Just wanted to clarify because the SMS still doesn't work, although the workaround does. |
After clearing the caches and using 14.1.0, I'm unable to sign in with SMS 2FA. I have multiple devices set up for device 2FA, but eas cli never asks for it. EDIT: It finally updated. But the device 2FA is far less preferred. |
|
Tried with both SMS an device code and it is till the same. |
|
Yup this was working now it's back |
|
I'm still having this issue as well, but @tinkerer's workaround helped me get up and running again. Same situation and seems easy to reproduce — I'm signed into Apple with my personal account on my computer, but am using a different Apple account to build my project. I'm never asked to select a verification method, even after deleting If I sign out of Apple (from System Settings) and sign in as the same profile I want to build the project with, it works as normal and prompts me for setting a verification method. The other workaround that has worked is using the If I go into XCode, I am signed into both Apple accounts there as well, but the CLI still doesn't work unless the account on the device matches the account building the project. |
this worked for me thanks |
This worked for me. I had to signed out of my personal Apple account, log in into my Apple work account, and the build works fine as expected. After that, I tried to logout of the work account, and re-login into my personal account on the same machine. Until now, build works as expected. I guess they need just the initial login verification? hoping EAS team find a more sustainable approach to this problem as it has been cropped up time and time again. |
|
Issue still persists on my end. I have updated eas cli to 14.2.0 and cleared caches. There was another release over the weekend of 12/13 , but I still get the error. Expo seriously needs to get it together here. This should have been resolved 3 versions ago! |
|
this just started happening to me, never saw this issue once and did a build successfully just this past friday. i cannot do the workaround because i do not own any apple devices besides the ipad received from my customer which i use to test the app, and it appears the apple account linked to it is not able to be changed. is there really not anything else i can do? can i not manually pull some key or something right through app store connect in my browser or anything like that? |
|
I'm having the same issue here. Not sure what to do. Workaround doesn't work. |
|
SMS 2FA was fixed for the repro we had internally after |
szdziedzic
added
eas build
and removed
needs review
This comment was marked as spam.
This comment was marked as spam.
|
I'm also experiencing this issue still. Not sure if this is what you're looking for, but I logged in with my browser at http://idmsa.apple.com (redirects to account.apple.com) and compared the headers to the expo cli. They're quite different, especially since the browser accepts text and the cli accepts json, but here you go: CLI Browser Happy to troubleshoot further if I left out too much information. I see the CLI makes 4 requests:
The browser makes 2 requests:
This may be a red-herring, but when the issue began for me last week, I tried logging into https://idmsa.apple.com/appleauth/auth in the browser and I was getting the exact same error "Verification codes can't be sent...". I contacted Apple Dev Support and sent them the headers, etc, and it was resolved the next day, but the Expo CLI issue remains. |
|
After a reboot of my machine (Windows) I was able to submit! |
|
Experienced this for the first time just now, with Had the different accounts on personal/dev mentioned above. Was able to build after logging into my computer with my dev account instead of personal and selecting 'device' instead of sms when rebuilding. |
|
I got it working after deleting the |
|
I found the weirdest fix that worked for me.
|
|
Same issue over here, Deleting the |
Thanks - for anyone else reading, try adding |
|
For me personally, it took me a couple weeks to figure out the right work around for myself. Of course it ended up being the first recommended work-around suggested, but i didnt fee l like trying that lol. it WAS that i was logged in to Icloud on my mac with my personal apple account, but needed to be logged in via my work apple account to receive the code. |
|
@Bay102 that is currently the case for me still. I am logged into personal account, separate from the work one I use in Expo. |
|
@spenavajr this allowed you to build on the separate account ?
|
|
@Bay102 Yup.
…On Thu, Jan 9, 2025 at 5:14 PM Bay ***@***.***> wrote:
@spenavajr <https://github.com/spenavajr> this allowed you to build on
the separate account ?
Thanks - for anyone else reading, try adding --non-interactive to your eas
build line & you should be set. Worked for me at least.
—
Reply to this email directly, view it on GitHub
<#2764 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AW4YTM6322MYWCZHV2WB23T2J3YEDAVCNFSM6AAAAABTOJ6XQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBRGM2DCNZSGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@Bay102 unfortunately now I am stuck again, at |
|
@spenavajr time to try the logging into the correct apple account ? Or have you already tried that? PS if you have not tried yet ( idk if you have to ) but I chose 'device' when it prompts the authentication method. |
this worked for me |
Build/Submit details page URL
https://expo.dev/accounts/alleyhector1981/projects/astrosnax
Summary
I'm still receiving the same authentication error from closed issue #2698 indicating that Apple cannot send verification to my phone number. I don't have an Apple device to use that workaround.
Managed or bare?
Managed
Environment
Enabled experimental React Native Directory checks. Unset the EXPO_DOCTOR_ENABLE_DIRECTORY_CHECK environment variable to disable this check.
✔ Check package.json for common issues
✔ Check Expo config for common issues
✔ Check native tooling versions
✔ Check if the project meets version requirements for submission to app stores
✔ Check for common project setup issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for app config fields that may not be synced in a non-CNG project
✔ Check for issues with Metro config
✔ Check npm/ yarn versions
✖ Validate packages against React Native Directory package metadata
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules use compatible support package versions for installed Expo SDK
Detailed check results:
The following issues were found when validating your dependencies against React Native Directory:
No metadata available: @apollo/client, graphql, react-native-fit-image
Advice:
Error output
Reproducible demo or steps to reproduce from a blank project
This happens when either running
eas buildoreas submitthough the debug output for eas submit is just the Apple security related above.The text was updated successfully, but these errors were encountered: