Not able to build standalone iOS

#1

I am not able to make a standalone build. I am not able to make out what is the exact problem and how can I solve it by looking at the logs. Can you please help. The logs are as follows

Modifying NSBundle configuration at /private/tmp/turtle/24655be6-6788-41f7-a880-fe002195386c/archive/Release/ExpoKitApp.xcarchive/Products/Applications/ExpoKitApp.app…
▼running gulp task
Using shell config: { isShell: true,
manifestUrl: ‘https://exp.host:443/@rashmi/foodie’,
releaseChannel: ‘default’,
testEnvironment: ‘none’,
isSplashScreenDisabled: true }
Configuring iOS Launch Screen…
[stderr] 2018-05-08 10:38:21.147 ibtoold[80091:443606] WARNING: Unhandled destination metrics: (null)
[stderr] 2018-05-08 10:38:21.182 ibtoold[80091:443606] WARNING: Unhandled destination metrics: (null)
[stderr] 2018-05-08 10:38:21.414 ibtoold[80091:443606] WARNING: Unhandled destination metrics: (null)
[stderr] 2018-05-08 10:38:21.414 ibtoold[80091:443606] WARNING: Unhandled destination metrics: (null)
[stderr] 2018-05-08 10:38:21.415 ibtoold[80091:443606] WARNING: Unhandled destination metrics: (null)
[stderr] 2018-05-08 10:38:21.415 ibtoold[80091:443606] WARNING: Unhandled destination metrics: (null)
[stderr] 2018-05-08 10:38:21.416 ibtoold[80091:443606] WARNING: Unhandled destination metrics: (null)
[stderr] 2018-05-08 10:38:21.417 ibtoold[80091:443606] WARNING: Unhandled destination metrics: (null)
[stderr] 2018-05-08 10:38:21.422 ibtoold[80091:443606] WARNING: Unhandled destination metrics: (null)
[stderr] 2018-05-08 10:38:21.422 ibtoold[80091:443606] WARNING: Unhandled destination metrics: (null)
[stderr] 2018-05-08 10:38:21.422 ibtoold[80091:443606] WARNING: Unhandled destination metrics: (null)
[stderr] 2018-05-08 10:38:21.423 ibtoold[80091:443606] WARNING: Unhandled destination metrics: (null)
[stderr] 2018-05-08 10:38:21.423 ibtoold[80091:443606] WARNING: Unhandled destination metrics: (null)
[stderr] 2018-05-08 10:38:21.423 ibtoold[80091:443606] WARNING: Unhandled destination metrics: (null)
▼configuring NSBundle
Compiling resources…
Cleaning up iOS…
▼running gulp task
[10:38:25] Finished ‘ios-shell-app’ after 17 s
▼running archive builder
done running shell app builder
▼building and signing IPA
building and signing IPA
Executing command: security cms -D -i /private/tmp/turtle/24655be6-6788-41f7-a880-fe002195386c/provisioning/24655be6-6788-41f7-a880-fe002195386c.mobileprovision
done retrieving provisioning profile
Checking if teamID is present in keychain and that certificate is valid…
decoding p12 certificate
verifying certificate is installed
Executing command: security find-identity -v -s (XXXXXXXXXX)
confirmed team ID is present in keychain
Chose export method: app-store
writing export-options.plist file…
building IPA
Executing command: fastlane gym -n unsigned.ipa --workspace /usr/local/turtle-agent/shellAppWorkspaces/ios/default/ExpoKitApp.xcworkspace --scheme ExpoKitApp --archive_path /private/tmp/turtle/24655be6-6788-41f7-a880-fe002195386c/archive.xcarchive --skip_build_archive true -i 7324506A242E8690D6F876914C5F6EF05904D492 --export_options /private/tmp/turtle/24655be6-6788-41f7-a880-fe002195386c/provisioning/export-options.plist --export_method app-store --export_xcargs OTHER_CODE_SIGN_FLAGS="–keychain /private/tmp/turtle-agent/821ad62c-52e6-11e8-93f8-0050568e5b7f.keychain" -o /private/tmp/turtle/24655be6-6788-41f7-a880-fe002195386c/build --verbose
Unable to generate IPA.
unable to build and sign IPA
▼deleting keychain
Executing command: fastlane run delete_keychain keychain_path:/private/tmp/turtle-agent/821ad62c-52e6-11e8-93f8-0050568e5b7f.keychain

#2

I have the same issue here, some issue with gulp task and ios-shell-app. Maybe xcode issue in expo builder?

#3

Hi Rashmi, something is off with the provisioning profile you tried to use. The easiest way to fix would be to pass the -c flag to the build command and choose to let expo manage your profile.

#4

Dan, you could try the same and hope you’re having the same issue. If that doesn’t work send us your build id and we can figure out what’s going on.

closed #5

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