Getting error during IOS build in turtle

https://expo.io/builds/431e8858-362b-46c9-a06c-f8809816ed5f

building and signing IPA
saved provisioning profile to temporary path
provisioning profile copied to home directory
removed provisioning profile from the home directory
Error: Process exited with non-zero code: 1
    at ChildProcess.child.on (/usr/local/turtle-js/node_modules/@expo/spawn-async/build/spawnAsync.js:39:21)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:925:16)
    at Socket.stream.socket.on (internal/child_process.js:346:11)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at Pipe._handle.close [as _onclose] (net.js:554:12)

Hey @christianallred,

Can you run expo diagnostics and paste the log printed out here?

Cheers,
Adam

@adamjnav My original account was locked out yesterday, and is still locked. I tried to post this response minutes after your reply by I was locked out for some reason.


  Expo CLI 2.7.0 environment info:
    System:
      OS: macOS 10.14.1
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 10.14.1 - ~/.nvm/versions/node/v10.14.1/bin/node
      npm: 6.4.1 - ~/.nvm/versions/node/v10.14.1/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    IDEs:
      Xcode: 10.1/10B61 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.5.0 => 16.5.0
      react-native: https://github.com/expo/react-native/archive/sdk-31.0.0.tar.gz => 0.57.1
      react-navigation: ^3.0.9 => 3.0.9
    npmGlobalPackages:
      expo-cli: 2.7.0
Expo CLI 2.6.14 environment info:
    System:
      OS: macOS 10.14.1
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 10.14.1 - ~/.nvm/versions/node/v10.14.1/bin/node
      npm: 6.4.1 - ~/.nvm/versions/node/v10.14.1/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    IDEs:
      Xcode: 10.1/10B61 - /usr/bin/xcodebuild
    npmPackages:
      expo: ^31.0.2 => 31.0.6 
      react: 16.5.0 => 16.5.0 
      react-native: https://github.com/expo/react-native/archive/sdk-31.0.0.tar.gz => 0.57.1 
      react-navigation: ^3.0.9 => 3.0.9 
    npmGlobalPackages:
      expo-cli: 2.6.14

Hey @christianallred/@christiansallred,

Are you still encountering this issue? We pushed a new version of expo-cli out yesterday. If you are still encountering it, can you try updating and see if anything changes?

I think the problem was with my provisioning profile. I updated my certs and provisioning profile and the error went away, but that being said that error was super unhelpful in debuging.

1 Like

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