Search Issue Tracker
Not Reproducible
Votes
0
Found in
2019.3
2020.1
2020.1.0a15
Issue ID
1200865
Regression
No
[IL2CPP] Generated Mac Xcode project causes a missing GameAssembly.map error
How to reproduce:
1. Open the "Il2cppMacTest.zip" project
2. Build the project for macOS with "Create Xcode Project" option
3. Build the project via Xcode
Actual result: Errors are thrown in Xcode
Expected result: No errors are thrown in Xcode
Reproducible with: 2020.1.0a15, 2019.3.0f1.
Notes:
- The "Create Xcode Project" option is available since 2019.3.
- The issue reproduces only on Il2CPP
- The error:
rm: /Users/karolisk/Library/Developer/Xcode/DerivedData/asdfgh-dtlrqwuigtqbwletbsmnmbgwtoof/Build/Products/Debug//GameAssembly.map: No such file or directory
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
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
- Text is truncated in the Inspector when the display scale is set to 150%
- CancellationTokenSource(<timeout>) has incorrect cancellation status when used in WebGL Player
- VFX property value names are cut off when properties with 'Arc' are viewed in the VFX Blackboard
clckwrk
Apr 22, 2020 19:49
Update #2: This error re-occurred when I archived the build. I fixed this by enabling the "New Build System" in Xcode (File>Project Settings) and by enabling code signing.
This seems to be the catch all error for "Something has gone wrong." The fact that it can't find a file is misleading.
clckwrk
Apr 22, 2020 18:51
Update: This error was caused by my codebase having some extern functions that were meant for an iOS build
clckwrk
Apr 22, 2020 18:20
+1 on this issue with 2019.3.10f1
mdrotar
Dec 13, 2019 19:58
I had the same/similar error in a basic test project with 2019.3.0f3. My installation path for Unity Hub has a space in it which the Unity-generated Run Script in Xcode doesn't handle correctly.
I was able to fix it by modifying the Run Script it generated for the GameAssembly target in Xcode. On line 1, I put quotes around the path on the right hand side of the MONO definition, and on line 3 I put quotes around first word, $MONO.
Line 1:
MONO="/Applications/Unity Hub/Hub/Editor/2019.3.0f3/Unity.app/Contents/MonoBleedingEdge/bin/mono"
Line 3:
"$MONO" "$IL2CPP" -verbose --compile-cpp --libil2cpp-static --dotnetprofile="unityaot" --platform="MacOSX" --architecture="x64" .........etc
I can build and run now.
It's unfortunate that Unity closed this without fixing it but hopefully this helps someone in the future.