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 |
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: