Hello! I am running expo on a PC with Windows 10! I am able to successfully build Android APKs and used to successfully build iPhone IPAs but am recently running into build issues for iOS. All my previous (successful) iOS builds were with expo-cli 2.6.14 and I upgraded to expo-cli 2.11.7 recently. As the transcripts below show, both my 2.11.7 and 2.6.14 iOS builds are running into issues! I seem to proceed a little further with 2.6.14 but it throws a status code 400 error before quitting.
I have checked that “Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux” is set per instructions.
I need help, please, on what to try next! Thank you!
The following transcripts are generated with EXPO_DEBUG set to true.
With expo-cli 2.11.7
$ expo build:ios -c
Checking if there is a build in progress…
Removed existing credentials from expo servers
Please enter your Apple Developer Program account credentials. These credentials are needed to manage certificates, keys and provisioning
profiles in your Apple Developer account.
The password is only used to authenticate with Apple and never stored.
? Apple ID: …my_appleID_here…
? Password (for …my_appleID_here…): [hidden]
- Trying to authenticate with Apple Developer Portal…?[2K?[1G?[?25h?[31m×?[39m Authentication with Apple Developer Portal failed!
?[31mProcess exited with non-zero code: 127?[39m
?[31m?[90mError: Process exited with non-zero code: 127?[31m?[39m
?[31m?[90m at ChildProcess.child.on (C:\Users\Surven\AppData\Roaming\npm\node_modules\expo-cli\node_modules@expo\spawn-async\build\spawnAsync.js:39:21)?[31m?[39m
?[31m?[90m at ChildProcess.emit (events.js:182:13)?[31m?[39m
?[31m?[90m at ChildProcess.cp.emit (C:\Users\Surven\AppData\Roaming\npm\node_modules\expo-cli\node_modules\cross-spawn\lib\enoent.js:40:29)?[31m?[39m
?[31m?[90m at maybeClose (internal/child_process.js:962:16)?[31m?[39m
?[31m?[90m at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)?[31m?[39m
?[?25h
After downgrading to expo-cli 2.6.14 (which used to successfully build before in previous versions):
$ expo build:ios -c
There is a new version of expo-cli available (2.11.7).
You are currently using expo-cli 2.6.14
Run npm install -g expo-cli
to get the latest version
[07:52:19] Making sure project is set up correctly…
[07:52:21] Your project looks good!
[07:52:21] Checking if current build exists…
[07:52:22] Did you know that Expo provides over-the-air updates?
[07:52:22] Did you know that Expo provides over-the-air updates?Please see the docs (https://docs.expo.io/versions/latest/guides/configuring-ota-updates) and check if you can use them instead of building your app binaries again.
[07:52:22] No currently active or previous builds for this project.
[07:52:22] Removed existing credentials from expo servers
[07:52:22] If you get errors about
‘Maximum number of certificates generated’ or ‘duplicate profiles’
then consider using the flags --revoke-apple-dist-certs, --revoke-apple-push-certs,
and --revoke-apple-provisioning-profile or go to developer.apple.com
and revoke those credentials manually
[07:52:22] We do not have some credentials for you, pushP12,pushPassword,provisioningProfile,certP12,certPassword
? How would you like to upload your credentials?
I will provide all the credentials and files needed, Expo does limited validation
We need your Apple ID/password to ensure the correct teamID and appID
Note: Expo does not keep your Apple ID or your Apple password.
? What’s your Apple ID? …my_appleID_here…
? Password? [hidden]
[07:53:20] Validating Credentials…
[07:53:20] Running: bash.exe -c PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin "/mnt/c/Users/Surven/AppData/Roaming/npm/node_modules/expo-cli/node_modules/@expo/traveling-fastlane-linux/traveling-fastlane-1.6.2-linux-x86_64/validate_apple_credentials" "…my_appleID_here… xxxx-xxxx-xxxx-xxxx"
[07:53:24] Only 1 team associated with your account, using Team ID: DMLWGBX88X
[07:53:24] Running: bash.exe -c PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin "/mnt/c/Users/Surven/AppData/Roaming/npm/node_modules/expo-cli/node_modules/@expo/traveling-fastlane-linux/traveling-fastlane-1.6.2-linux-x86_64/app_management" "verify …my_appleID_here… xxxx-xxxx-xxxx-xxxx DMLWGBX88X com.easyiotsolutions.expoLawnManagement @surven/expoLawnManagement false"
[07:53:27]
WARNING! In this mode, we won’t be able to make sure your certificates,
or provisioning profile are valid. Please double check that you’re
uploading valid files for your app otherwise you may encounter strange errors!
Make sure you’ve created your app ID on the developer portal, that your app ID
is in app.json as bundleIdentifier
, and that the provisioning profile you
upload matches that team ID and app ID.
[07:53:27] Please provide the path to your push notification cert P12
? Path to P12 file: C:\Users\Surven\Documents\reactnative\EXPOLAWN\packageExpoLawnManagement190308\aps.p12
? P12 password: [hidden]
[07:53:52] Please provide the path to your .mobile provisioning profile
? Path to your .mobile provisioning Profile C:\Users\Surven\Documents\reactnative\EXPOLAWN\packageExpoLawnManagement190308\JointProfile.mobileprovision
[07:54:08] Please provide your distribution certificate P12:
? Path to P12 file: C:\Users\Surven\Documents\reactnative\EXPOLAWN\packageExpoLawnManagement190308\ios_distribution.p12
? P12 password: [hidden]
[07:54:35] Error while gathering & validating credentials
[07:54:35] Error: Request failed with status code 400
[07:54:35] Request failed with status code 400
[07:54:35] Error: Request failed with status code 400
at createError (C:\Users\Surven\AppData\Roaming\npm\node_modules\expo-cli\node_modules\xdl\node_modules\axios\lib\core\createError.js:16:15)
at settle (C:\Users\Surven\AppData\Roaming\npm\node_modules\expo-cli\node_modules\xdl\node_modules\axios\lib\core\settle.js:17:12)
at IncomingMessage.handleStreamEnd (C:\Users\Surven\AppData\Roaming\npm\node_modules\expo-cli\node_modules\xdl\node_modules\axios\lib\adapters\http.js:236:11)
at IncomingMessage.emit (events.js:187:15)
at endReadableNT (_stream_readable.js:1094:12)
at process._tickCallback (internal/process/next_tick.js:63:19)