XCode 14.2 build failed PhaseScriptExecution - from Unity 2022.2.0f1

Sorry dont know where else to ask the question

On Android the project builds and runs fine. If I build to XCode, from Unity thats fine, but then from XCode I run into a build failed:

I’m running Unity on Windows, but XCode on a M2 mac with iPad Pro

Any ideas?

You are getting an InvalidOperationException from a custom shell script called ‘Run Script’. I’m not familiar with any script like this on our end. Is that yours?

@andyb-unity I’m building the AR samples and only the scene “BasicImageTracking”.

I also imported the Kyle robot, and a template from Joy’s latest AR tut on Unity Learn.

How can I search for this “Run Script” shell script? I dont even know what is a shell script!

I searched in Windows Explorer in my entire project and there is no file called “run script” or even “runscript

Maybe its something new in XCode 14.2?

I wonder if this is related, seems many people are having issues building with XCode from Unity 2022.2:
https://discussions.unity.com/t/902678

I can confirm, rolling back to Unity 2021.3, fixes the issue. So it seems to be some issue with Unity 2022.2

I build for iOS from OSX so I haven’t seen this issue. Based on the thread you linked, it appears that there might be an issue compiling for iOS from Windows in 2022.2. I don’t see any reason to think that AR Foundation is the cause of this issue but feel free to reach back out if you get more information.

1 Like

Same here. The project builds OK in Windows, but the error occurs when trying to build in XCode 14.2. When building from Unity on MacOS, no issues occur. Suppose this is Unity related. I am using Unity 2022.2.8f1

I tried this last week and also ran into issues. If one of you could file a bug for this: Unity QA: Building quality with passion, that would create a public issue in our issue tracker so that other users can check the status of the fix. Either way for now you are correct that building AR Foundation apps for iOS from Windows is currently broken. Thanks for this report!

2 Likes

Same problem. Have found a raised issue here.

2 Likes