Ok, we have disabled everything but ‘Associated Domains’, ‘Push Notifications’ and ‘Sign In with Apple’. The ‘Sign In with Apple’ capability is giving that initial error I posted about when trying to disable it.
There is a problem with the request entity - The bundle ‘K3PHV8M3R9’ cannot be deleted. Delete all the Apps related to this bundle to proceed
We are using Sign in with Apple, and it was working locally without having the right configuration in app.json. I added the “usesAppleSignIn” key for iOS in app.json. We ended up clearing out most things in the developer account and used a different identifier and I was able to successfully build an .ipa file.
great! keep in mind that during eas feature preview you should always try to use the latest version of eas-cli. we are updating it rapidly and there are sometimes breaking changes
I also had to use your suggested hack EXPO_NO_CAPABILITY_SYNC=1. Not sure what the implications of this are, but I was not able to find a fix via solutions in this thread.
i would say it’s not necessarily a hack but rather a workaround should you encounter a situation where our capability syncing system isn’t able to handle your case, for some reason. you can manually toggle capabilities in the apple developer portal for your identifier if that’s the case.
I resolve this intalling expo-apple-authentication, and add to the plugin area em app.json like plugins: [
[“expo-apple-authentication”],
]
and finally adding in app.json ios: { “usesAppleSignIn”: true, }.
The problens start when I mark ‘login with apple’ in the apple store.