Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.3.X, 6000.4.X, 6000.5.X
Votes
2
Found in
6000.0.56f1
6000.2.1f1
6000.3.0a5
6000.4.0a1
6000.5.0a1
Issue ID
UUM-114549
Regression
No
[macOS] Setting IL2CPP Stacktrace Information to "Method Name, File Name, and Line Number" Will Fail the Build for macOS on Xcode
How to reproduce:
1. Open the “macOSBuildFails.zip“ project
2. Open the “SampleScene“
3. Navigate to the “File > Build Profiles“
4. Enable the “Create Xcode Project“ options
5. Navigate to the “Edit > Project Settings > Player > Other Settings“
6. Under the Configuration section, set Scripting Backend to IL2CPP
7. Set ”IL2CPP Stackrace Information” to “Method Name, File Name, and Line Number“
8. Build the Xcode Project
9. Open the “macOS.xcodeproj“
10. Build the application in Xcode
Expected result: Build does not fail
Actual result: Build fails with “Command PhaseScriptExecution failed with a nonzero exit code”
Reproducible with: 2023.3.0a15 (88af49042196), 6000.0.56f1, 6000.2.1f1, 6000.3.0a5
Could not test with: 2023.2.0a10 (67f0519c7f6d), 2023.2.0a19 (cab10490cda3) (The Xcode project fails to build on issue unrelated to the issue investigated on this ticket)
Reproducible environment: macOS 15.6 (M4 Max)
Not reproducible environment: No other environment tested
Notes: Just building a “.app“ file will not have issues, but building on an Xcode Project will fail
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Switching a Type QueryBlock to prefabs fails
- Search Index Manager allows deleting Empty Index List when clicking on “-“ button, throwing “ArgumentOutOfRangeException” error in the Console window
- "System.ArgumentOutOfRangeException" error is thrown when baking Adaptive Probe Volumes
- Project Directory is opened when Opening the Editor Log from the Console Window and the Editor is launched with the -nolog argument
- "vector<bool> too long" error is thrown when using UnityYAMLMerge
Add comment