numandev1 / react-native-keys

πŸ” Protected .ENVs variables in React Native πŸš€βœ¨
MIT License
314 stars 28 forks source link

Xcode 15 Exited with status code 127 #53

Closed efstathiosntonas closed 1 year ago

efstathiosntonas commented 1 year ago

Current behavior

Hi, when I try to build on Xcode 15 it throws Exited with status code 127. I've tried it on my project and the example project, both throw the same error.

See atached .txt for the logs, it seems that it exits on /bin/sh -c /var/folders/tc/sj1dwpmd3wx006fkwntygshh0000gn/T/SchemeScriptAction-fuoWNX.sh, I've tried to run the script on my terminal and it throws No such file or directory

Build KeysExample-Dev_2023-09-27T10-42-05.txt

Expected behavior

Platform

React Native Version 0.72.5

React Native Compressor Version

Reproducible Steps And Demo

github-actions[bot] commented 1 year ago

πŸ‘‹ @efstathiosntonas Thanks for opening your issue here! If you find this package useful hit the star🌟!

numandev1 commented 1 year ago

@efstathiosntonas can you send the screenshot of your preaction script?

numandev1 commented 1 year ago

@efstathiosntonas i tested, it is working on my side

simulator_screenshot_67386EE3-6366-4EC1-87D8-F94238BA35BC

efstathiosntonas commented 1 year ago

@numandev1 thanks for the fast reply. I'm running the example from this repo.

steps MacOS Sonoma 14, Xcode 15:

  1. yarn install
  2. cd example
  3. yarn install
  4. cd ios
  5. pod install
  6. open on Xcode
  7. build on simulator iOS 17

I'm not doing anything else, I didn't touched the schemas. Really weird.

efstathiosntonas commented 1 year ago

I've runned it again, now it throws some more info at the ending lines of the log, it cannot find the .sh script as suspected:

    /bin/sh -c /var/folders/tc/sj1dwpmd3wx006fkwntygshh0000gn/T/SchemeScriptAction-sh6CQB.sh

env: node: No such file or directory
numandev1 commented 1 year ago

if you are using nvm then please follow this guide https://github.com/numandev1/react-native-keys#using-node-with-nvm-fnm-or-notion

efstathiosntonas commented 1 year ago

Yeah, I suspected nvm is the issue after the error above, looking into it now

efstathiosntonas commented 1 year ago

@numandev1 it's fine now, thank you for your help, keep it up!