Command PhaseScriptExecution failed with a nonzero exit code #104
Comments
|
It's odd that there's no output reported. Does Also, can you try manually running the command that the app is trying to fork? That might provide some better diagnostics: skip gradle -p /Users/l333n/Desktop/project-name/Darwin/../Android launchDebug |
|
Running After running the |
|
Interesting I restarted the android emulator and now the |
it sounds like you just need to be running the Android emulator in order to be able to launch the app. As per https://skip.tools/docs/gettingstarted/#app_development : skip init creates a functional template app, but before you can build and launch it, an Android emulator needs to be running. Launch Android Studio.app and open the Virtual Device Manager from the ellipsis menu of the Welcome dialog. From there, Create Device (e.g., “Pixel 6”) and then Launch the emulator. |
Odd. Can you try Let us know if that doesn't help and we'll continue to dig. If you can launch it from the CLI, you definitely should be able to run it from Xcode (since all Xcode is doing is invoking that command from its Build Phases for the project). |
|
Alright I did a |
So the same error as before, right? How odd. Let's try a different tack: can you try cloning or downloading https://github.com/skiptools/skipapp-showcase.git and then opening the |
|
Ya the same error indeed, what's also interesting is that when I'm building https://github.com/skiptools/skipapp-showcase.git I'm getting the same error as in my own project. |
Can you post the output of |
|
[✓] Skip version 0.8.25 (= 0.8.25) |
|
Is the machine Intel or ARM? I notice that we are invoking |
|
The machine is running on ARM. |
|
Was it upgraded from a previous Intel machine that has Homebrew installed in /usr/local/bin/? If you trash that folder (keeping a backup), it might fall back to using the correct path. Also, can you run Once you try those things, quit and re-launch Xcode and try running again. Let us know if you continue to see the error, but the mention of |
|
Homebrew wasn't installed on an previous intel machine but it was installed from a terminal using rosetta. I trashed the folder -> restarted xcode -> cleaned the build folder -> rebuild the project. But this still gives the same error The result of running I checked the |
No, absence of the property should be fine – it is only if it is overridden in the environment that it would cause problems. Out of curiosity, do you know why would Terminal have been running under Rosetta? Is it possible that Xcode is also running under Rosetta? You can check in Activity Monitor. That would cause us to try to pick skip/Sources/SkipDrive/GradleDriver.swift Lines 610 to 613 in ac2807c I feel like we are getting close. Thanks for your patience helping us work this out – it will certainly help future users who grapple with this sort of issue. |
|
The reason it was running under Rosetta in the first place was because when the arm systems came out a nodejs project I was working on didn't support running some command lines in a arm terminal yet. So I think I installed brew at that time via the rosetta terminal. I checked Xcode via the activity monitor. The activity monitor says that I'm running Xcode via arm so that's good. |
|
Let's try one more thing: can you manually edit the That should force Skip to use the correct Homebrew install. 
|
|
Still the same error with the edited build phase Error: |
|
Maybe the reason it's not building correctly has something to do with the output of The output of The full log: |
|
This is turning into quite a mystery! Is there anything in the |
|
Hehe ya but now I'm dedicated to find out why it's not working as expected! I checked the folder you mentioned above. After running the command a second time it does give the same error. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Trying to build a demo app from xcode unfortunately this causes the following error in the xcode logs. Any idea on how to fix this issue?
The text was updated successfully, but these errors were encountered: