expo build:ios fails "Error: xcrun exited with non-zero code: 1"

Expo Development Tools
1

https://expo.io/builds/c02882f7-eaa6-4c9f-ada6-fa00e8219051

Command: expo build: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:169:43)
at Object.buildAssetArchiveAsync (/usr/local/turtle-js/node_modules/@expo/xdl/build/detach/IosAssetArchive.js:49:49)
at
at process._tickDomainCallback (internal/process/next_tick.js:229:7)

2

Same problem, any tip?

3

https://github.com/expo/expo-cli/issues/943

4

I’m having the same issue.

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)
5

Hi @mauricekenji

Do the comments in the bug that @vatex posted above help?

jansomers commented 3 days ago

I have the same issue? Can someone reply?

Solved: make sure your assets are valid for iOS (I was uploading a 56x60 icon , and it had to be 60x60 or any equal )

vatex commented 3 days ago

Yeah, that was a problem of the icon.
If anyone else encountered the same problem, you can use this platform to convert your icon as needed: https://makeappicon.com

6

can you open xcode , there may be an upgrade .

7

Unfortunately, it doesn’t work, and everything is up-to-date.

My Xcode version is current at 10.3. My iOS simulators are up-to-date and have been hard-reset. The Expo client is current at 3.0.10.

https://docs.expo.io/versions/latest/workflow/ios-simulator/

8

I used Figma to generate an non-transparent icon. Then I used expo-optimize automatically generate optimized icons for uploading.

‘expo build:ios’ as well as ‘expo build:android’ still fails

10 
[stderr] FAILURE: Build failed with an exception.
[stderr] * What went wrong:
[stderr] Execution failed for task ':app:mergeReleaseResources'.
[stderr] > java.util.concurrent.ExecutionException: com.android.builder.internal.aapt.v2.Aapt2Exception: Android resource compilation failed
[stderr]   /app/turtle/workingdir/android/sdk34/android-shell-app/app/src/main/res/drawable-xxxhdpi/shell_launch_background_image.png: error: failed to read PNG signature: file does not start with PNG signature.
[stderr] * Try:
[stderr] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
[stderr] * Get more help at https://help.gradle.org
[stderr] BUILD FAILED in 1m 34s
785 actionable tasks: 785 executed

Is it an issue with the Splash screen or formatting? My file is a simple .png file, exported from Figma, following the Expo splash screen asset guidelines.

https://docs.expo.io/versions/latest/guides/splash-screens/#__next

ISOLATED THE PROBLEM: It was a splash.png asset issue.
SOLUTION: Flatten any live type in your Figma file before exporting.

11

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