You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 18, 2024. It is now read-only.
expo build:ios expects the EXPO_APPLE_PASSWORD env variable, whereas expo upload:ios expects the EXPO_APPLE_ID_PASSWORD env variable. Unless there's a reason to have these be two different keys, it would avoid confusion to use the same one in both scenarios
Since this would be a breaking change, we can wait to fix this until we are about ready to ship a new major version. It's an easy change to make, but could cause a headache for people who are accustomed to the current workflow
The text was updated successfully, but these errors were encountered:
expo build:ios expects the EXPO_APPLE_PASSWORD env variable, whereas expo upload:ios expects the EXPO_APPLE_ID_PASSWORD env variable. Unless there's a reason to have these be two different keys, it would avoid confusion to use the same one in both scenarios
Since this would be a breaking change, we can wait to fix this until we are about ready to ship a new major version. It's an easy change to make, but could cause a headache for people who are accustomed to the current workflow
I vote for this as well. Now we are managing 2 different keys in 3 projects. Couldn't we gracefully deprecate it? Make it work for x amount of expo-cli versions whilst showing a warning message?
expo build:ios
expects theEXPO_APPLE_PASSWORD
env variable, whereasexpo upload:ios
expects theEXPO_APPLE_ID_PASSWORD
env variable. Unless there's a reason to have these be two different keys, it would avoid confusion to use the same one in both scenariosSince this would be a breaking change, we can wait to fix this until we are about ready to ship a new major version. It's an easy change to make, but could cause a headache for people who are accustomed to the current workflow
The text was updated successfully, but these errors were encountered: