iOS build fails. I have tried from various AppleIds, istore and enterprise account, various computers (mac and pc with ubuntu subsystem), and same result with same error message
My exp version: 57.2.1
Node.js version 13.3.0 but I downgraded to 12 and error still persists.
I have run “set EXPO_DEBUG=true” at the prompt to get more error information, here is the what happens:
c:\Users******\BabyPhoto>exp build:ios -c --apple-enterprise-account
…
[13:12:27] Your project looks good!
…
? How would you like to upload your credentials?
Expo handles all credentials, you can still provide overrides
…
[13:13:06] Validating Credentials…
[13:13:06] Running: bash.exe -c PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /mnt/c/Users/****/AppData/Roaming/npm/node_modules/exp/node_modules/@expo/traveling-fastlane-linux/traveling-fastlane-1.5.0-linux-x86_64/validate_apple_credentials “AppDevelopment@mediclinic.co.za PASSWORD HIDDEN FROM POST]”
getaddrinfo: Name or service not known
getaddrinfo: Name or service not known
getaddrinfo: Name or service not known
getaddrinfo: Name or service not known
getaddrinfo: Name or service not known
[13:15:42] Error while gathering & validating credentials
[13:15:42] Error: Reason:Unknown reason, raw:“Could not receive latest API key from iTunes Connect, this might be a server issue.”
[13:15:42] Reason:Unknown reason, raw:“Could not receive latest API key from iTunes Connect, this might be a server issue.”
[13:15:42] Error: Reason:Unknown reason, raw:“Could not receive latest API key from iTunes Connect, this might be a server issue.”
at Object._callee4$ (C:\exp@57.2.1\src\commands\build\auth.js:134:11)
at tryCatch (C:\Users*\AppData\Roaming\npm\node_modules\exp\node_modules\regenerator-runtime\runtime.js:62:40)
at Generator.invoke [as _invoke] (C:\Users*\AppData\Roaming\npm\node_modules\exp\node_modules\regenerator-runtime\runtime.js:296:22)
at Generator.prototype. [as next] (C:\Users*\AppData\Roaming\npm\node_modules\exp\node_modules\regenerator-runtime\runtime.js:114:21)
at step (C:\Users*\AppData\Roaming\npm\node_modules\exp\node_modules\babel-runtime\helpers\asyncToGenerator.js:17:30)
at C:\Users*****\AppData\Roaming\npm\node_modules\exp\node_modules\babel-runtime\helpers\asyncToGenerator.js:28:13
at processTicksAndRejections (internal/process/task_queues.js:97:5)
…And here is the latest “exp diagnostics”…:
Environment:
OS: Windows 10
Node: 13.3.0
Yarn: Not Found
npm: 6.4.1
Watchman: Not Found
Xcode: N/A
Android Studio: Version 3.2.0.0 AI-181.5540.7.32.5056338
Packages: (wanted => installed)
expo: ^35.0.0 => 35.0.0
react: 16.8.3 => 16.8.3
react-native: https://github.com/expo/react-native/archive/sdk-35.0.0.tar.gz => 0.59.8
Diagnostics report:
\Warning: .end() was called twice. This is not supported in superagent
(node:9284) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
[13:35:41] Request failed with status code 500
[13:35:41] Error: Request failed with status code 500
at createError (C:\Users\peterh\AppData\Roaming\npm\node_modules\exp\node_modules\axios\lib\core\createError.js:16:15)
at settle (C:\Users*\AppData\Roaming\npm\node_modules\exp\node_modules\axios\lib\core\settle.js:17:12)
at IncomingMessage.handleStreamEnd (C:\Users*\AppData\Roaming\npm\node_modules\exp\node_modules\axios\lib\adapters\http.js:236:11)
at IncomingMessage.emit (events.js:224:7)
at endReadableNT (_stream_readable.js:1206:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)