Search Issue Tracker
Fixed
Fixed in 2021.3.31f1, 2022.3.10f1, 2023.1.15f1, 2023.2.0b12, 2024.1.0a1
Votes
60
Found in
2022.3.7f1
2023.1.9f1
2023.2.0b5
Issue ID
UUM-46899
Regression
No
Building projects with IL2CPP scripting backend for Apple platforms fails with Xcode 15.0b6 or newer
Xcode >= 15.0b6 contains a change to the "ProductName" in the "version.plist", which Unity will fail to parse. Because of that, Unity is not able to use this or newer version of Xcode to compile code for IL2CPP for macOS and iOS.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
shuan_xy
Feb 07, 2024 00:53
run into this issue with 2022.3.8 after XCode15, update unity version to 2022.3.19, now works like a charm! thanks for the update
Christopher-Anderson-GISP
Dec 11, 2023 16:45
Unity, this is not resolved!!!
All unity versions (including 2022.3.15f
I have to completely delete the xcode project and add the -ld64 before hitting play or archiving. If I miss a step I have to do it all over again. This is ridiculous.
OnTopStudios
Nov 21, 2023 17:32
I don't believe this issue is solved. I updated one of my projects to 2022.3.13 and still had to write "-Id64" to other flags, in another project I updated from 2021.3.16 to 2021.3.32 and is not working even when adding the flag workaround.
Inc8877
Nov 18, 2023 18:10
Still facing this issue in Unity 2022.3.12 and macOS Sonoma on M1, add "-Id64" to other flags workaround works but it's annoying
unity_F6BA6E2672D01BA21855
Nov 17, 2023 06:48
Hi for me this issue is solve, build this and run in xcode in seperate, dont do build and run.
Love to connect in linkedin, Aasurjya Bikash Handique
VincentBarnoux
Nov 12, 2023 08:01
It is still an issue in 2022.3.13f1 and workaround is needed -ld64 or -ld_classic
The workaround only works when the Xcode solution is never build before. If it is build once with the error, and try to do the workaround it won't work.
theolagendijk
Nov 08, 2023 14:43
Still an issue in Unity 2023.1.19f1
Griffo
Nov 06, 2023 16:32
Upgraded to 2023.1.19f1 and still have the problem :(
nickhworks
Oct 24, 2023 18:03
Mac - M1 Pro, Ventura
Xcode - 15.0.1
Unity - 2022.3.5f1
Error - "PhaseScriptExecution failed with a nonzero exit code"
The “-ld64" work around is not working for us.
https://developer.apple.com/forums/thread/735426
Sean09
Oct 23, 2023 09:31
As a temporary workaround you can add “-ld64” to the “Other Linker Flags” in the Build Settings for UnityFramework.
Spotted this solution here:
https://developer.apple.com/forums/thread/735426