Expo build:ios and build:android failure during constructing splash screen or bundling assets

Expo Development Tools
1 
Modifying NSBundle configuration at /private/tmp/turtle/a5f4ac16-8430-40dc-a5ab-1b8bd91f54c6/archive/Release/ExpoKitApp.xcarchive/Products/Applications/ExpoKitApp.app...
Using standalone config: { isShell: true,
  manifestUrl: 'https://expo.io:443/@mauricekenji/########',
  releaseChannel: 'default',
  testEnvironment: 'none' }
Configuring iOS Launch Screen...
Bundling assets...
Compiling resources...
Cleaning up iOS...
Error: xcrun exited with non-zero code: 1
    at ChildProcess.completionListener (/usr/local/turtle-js/node_modules/@expo/xdl/node_modules/@expo/spawn-async/build/spawnAsync.js:52:23)
    at Object.onceWrapper (events.js:317:30)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:915:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
    ...
    at spawnAsync (/usr/local/turtle-js/node_modules/@expo/xdl/node_modules/@expo/spawn-async/build/spawnAsync.js:17:21)
    at spawnAsyncThrowError (/usr/local/turtle-js/node_modules/@expo/xdl/build/detach/ExponentTools.js:233:45)
    at Object.buildAssetArchiveAsync (/usr/local/turtle-js/node_modules/@expo/xdl/build/detach/IosAssetArchive.js:89:51)
    at <anonymous>
    at process._tickDomainCallback (internal/process/next_tick.js:229:7)```

Expo CLI 3.0.10 environment info:
System:
OS: macOS 10.14.6
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.16.0 - /usr/local/opt/node@10/bin/node
Yarn: 1.17.3 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/opt/node@10/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5522156
Xcode: 10.3/10G8 - /usr/bin/xcodebuild
npmPackages:
expo: ^34.0.3 => 34.0.4
react: 16.8.3 => 16.8.3
react-native: https://github.com/expo/react-native/archive/sdk-34.0.0.tar.gz => 0.59.8
react-navigation: ^3.11.1 => 3.12.0
npmGlobalPackages:
expo-cli: 3.0.10

1 Like
2

SOLVED: Production issue when exporting asset as .png file. I had editable type in my file. Flattening the type and exporting fixed the issue. There must be extra data packaged when exporting .png while file has live type in it. My issue is mostly helpful if your job is to manage assets and less to do with Expo.

3

Glad you got things figured out and thanks for sharing the solution with the community!

4

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