upload to TestFlight failed

#1

[13:54:14] Ensuring the app exists on App Store Connect, this may take a while…
[13:54:41] Uploading the app to Testflight, hold tight…
[13:54:54]: Login to App Store Connect (barondesmond@gmail.com)
[13:54:56]: Login successful
[13:54:56]: Ready to upload new build to TestFlight (App: 1451620439)…
[13:55:03] Failed to upload the standalone app to the app store.
[13:55:03] undefined method start_with?' for nil:NilClass [13:55:03] Error: undefined methodstart_with?’ for nil:NilClass
at _callee2$ (/expo-cli@2.7.1/src/commands/upload/utils.js:53:11)
at tryCatch (/usr/local/lib/node_modules/expo-cli/node_modules/regenerator-runtime/runtime.js:62:40)
at Generator.invoke [as _invoke] (/usr/local/lib/node_modules/expo-cli/node_modules/regenerator-runtime/runtime.js:296:22)
at Generator.prototype.(anonymous function) [as next] (/usr/local/lib/node_modules/expo-cli/node_modules/regenerator-runtime/runtime.js:114:21)
at step (/usr/local/lib/node_modules/expo-cli/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)
at /usr/local/lib/node_modules/expo-cli/node_modules/babel-runtime/helpers/asyncToGenerator.js:28:13

I can’t figure out why the app runs in the expo but bombs when uploaded to TestFlight

Baron

0 Likes

#2

Hey @barondesmond,

I’ve relayed this internally but can you run expo diagnostics and share the log that’s printed out here?

Cheers,
Adam

0 Likes

#3

Expo CLI 2.9.0 environment info:
System:
OS: macOS 10.14.3
Shell: 3.2.57 - /bin/sh
Binaries:
Node: 10.15.1 - /usr/local/bin/node
npm: 6.4.1 - /usr/local/bin/npm
IDEs:
Xcode: /undefined - /usr/bin/xcodebuild
npmPackages:
expo: ^32.0.0 => 32.0.4
react: 16.5.0 => 16.5.0
react-native: https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz => 0.57.1
react-navigation: ^3.0.9 => 3.1.4
npmGlobalPackages:
expo-cli: 2.9.0

0 Likes

#4

It looks weird, have you ever run xcode? I think you need to run it at least once.

0 Likes

#5

I have loaded it, and I have used it in the past but I had to install a new version/OS as last time I did an app was 6 years ago and then I only ran the simulator. I will run my previous project that I had done via the xcode.

Baron

0 Likes

#6

Probably some disconnect between xcode and expo.
sh-3.2# expo install:ios
Can’t determine id of Simulator app; the Simulator is most likely not installed on this machine { Error: Command failed: osascript -e id of app “Simulator”
0:2: execution error: Can’t get application “Simulator”. (-1728)

at ChildProcess.exithandler (child_process.js:294:12)
at ChildProcess.emit (events.js:189:13)
at maybeClose (internal/child_process.js:970:16)
at Socket.stream.socket.on (internal/child_process.js:389:11)
at Socket.emit (events.js:189:13)
at Pipe._handle.close (net.js:600:12)

killed: false,
code: 1,
signal: null,
cmd: ‘osascript -e id of app “Simulator”’ }
[09:56:02] Simulator not installed. Please visit https://developer.apple.com/xcode/download/ to download Xcode and the iOS simulator. If you already have the latest version of Xcode installed, you may have to run the command sudo xcode-select -s /Applications/Xcode.app.

its suggestion doesn’t work either.

Baron

1 Like

#7

Expo CLI 2.9.0 environment info:
System:
OS: macOS 10.14.3
Shell: 3.2.57 - /bin/sh
Binaries:
Node: 10.15.1 - /usr/local/bin/node
npm: 6.4.1 - /usr/local/bin/npm
IDEs:
Xcode: 10.0/10A255 - /usr/bin/xcodebuild
npmPackages:
expo: ^32.0.0 => 32.0.4
react: 16.5.0 => 16.5.0
react-native: https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz => 0.57.1
react-navigation: ^3.0.9 => 3.1.4
npmGlobalPackages:
expo-cli: 2.9.0

fixed the xcode problem. it was installed in the Downloads instead of Applications. Now the simulator works.
[12:22:17] ::ffff:10.111.0.41 - - [06/Feb/2019:18:22:17 +0000] “GET /assets/./assets/images/icon.png HTTP/1.1” 200 - “-” “Expo/2.10.0.105122 CFNetwork/976 Darwin/18.2.0”

[12:22:25] ::ffff:10.111.0.41 - - [06/Feb/2019:18:22:25 +0000] “GET /assets/./assets/images/splash.png HTTP/1.1” 200 - “-” “Expo/2.10.0.105122 CFNetwork/976 Darwin/18.2.0”

[12:23:12] Opening iOS simulator

[12:23:25] ::ffff:10.111.0.41 - - [06/Feb/2019:18:23:25 +0000] “GET /node_modules/expo/AppEntry.bundle?platform=ios&dev=false&minify=true&hot=false&assetPlugin=%2FUsers%2Fbarondesmond%2FDocuments%2Ftimeclock%2Fnode_modules%2Fexpo%2Ftools%2FhashAssetFiles.js HTTP/1.1” 200 - “-” “Expo/2.10.0.105122 CFNetwork/976 Darwin/18.2.0”

[12:28:08] Finished building JavaScript bundle in 344348ms.

4 hours later…

sh-3.2# expo build:ios

[12:36:46] Checking if there is build in progress…

[12:36:51] Publishing to channel ‘default’…

[12:36:54] Building iOS bundle

[12:36:54] Building Android bundle

[12:38:45] Analyzing assets

[12:39:00] Uploading assets

[12:39:01] No assets changed, skipped.

[12:39:02] Processing asset bundle patterns:

[12:39:02] - /Users/barondesmond/Documents/timeclock/**/*

[12:39:02] Uploading JavaScript bundles

[12:39:06] Published

[12:39:06] Your URL is

https://exp.host/@barondesmond/timeclock

[12:39:06] Checking if this build already exists…

[12:39:06] Building…

[12:39:06] Build started, it may take a few minutes to complete.

[12:39:06] You can check the queue length at

[12:39:06] You can monitor the build at

|[12:39:07] Waiting for build to complete. You can press Ctrl+C to exit.

[12:41:08] Successfully built standalone app: https://expo.io/artifacts/3da554c0-ca1d-4992-9bae-0650f876e62b

sh-3.2# expo upload:ios

[12:41:38] Downloading build from https://exp-shell-app-assets.s3.us-west-1.amazonaws.com/ios/%40barondesmond/timeclock-b3c5f158-a85b-4799-808c-38cb480034a1-archive.ipa

Downloading [==================================================================================================================================================================] 100% 0.0

? What’s your Apple ID? barondesmond@gmail.com

? Password? [hidden]

[12:42:08] Ensuring the app exists on App Store Connect, this may take a while…

[12:42:23] Uploading the app to Testflight, hold tight…

[12:42:25]: Login to App Store Connect (barondesmond@gmail.com)

[12:42:26]: Login successful

[12:42:27]: Ready to upload new build to TestFlight (App: 1451620439)…

[12:42:36]: Going to upload updated app to App Store Connect

[12:42:36]: This might take a few minutes. Please don’t interrupt the script.

[12:43:10]: [Transporter Error Output]: Please sign in with an app-specific password. You can create one at appleid.apple.com. (-22910)

[12:43:10]: Transporter transfer failed.

[12:43:10]:

[12:43:10]: Please sign in with an app-specific password. You can create one at appleid.apple.com. (-22910)

[12:43:10]:

[12:43:10]: Your account has 2 step verification enabled

[12:43:10]: Please go to https://appleid.apple.com/account/manage

[12:43:10]: and generate an application specific password for

[12:43:10]: the iTunes Transporter, which is used to upload builds

[12:43:10]:

[12:43:10]: To set the application specific password on a CI machine using

[12:43:10]: an environment variable, you can set the

[12:43:10]: FASTLANE_APPLE_APPLICATION_SPECIFIC_PASSWORD variable


Please provide your Apple Developer Program account credentials

The login information you enter will be stored in your macOS Keychain


[12:43:10] Failed to upload the standalone app to the app store.

[12:43:10] Missing password for user barondesmond@gmail.com, and running in non-interactive shell

[12:43:11] Error: Missing password for user barondesmond@gmail.com, and running in non-interactive shell

at _callee2$ (/expo-cli@2.9.0/src/commands/upload/utils.js:53:11)

at tryCatch (/usr/local/lib/node_modules/expo-cli/node_modules/regenerator-runtime/runtime.js:62:40)

at Generator.invoke [as _invoke] (/usr/local/lib/node_modules/expo-cli/node_modules/regenerator-runtime/runtime.js:296:22)

at Generator.prototype.(anonymous function) [as next] (/usr/local/lib/node_modules/expo-cli/node_modules/regenerator-runtime/runtime.js:114:21)

at step (/usr/local/lib/node_modules/expo-cli/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)

at /usr/local/lib/node_modules/expo-cli/node_modules/babel-runtime/helpers/asyncToGenerator.js:28:13

So in essence Its fixed. Now onto the next problem. I don’t like two factor authorization.

Baron

0 Likes

upload to TestFlight
closed #8

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.

0 Likes