Search Issue Tracker
Fixed
Votes
0
Found in
2018.4
2020.1.1f1
2020.2
Issue ID
1270430
Regression
No
[IL2CPP][macOS] GameAssembly error is thrown when building the generated Xcode project
How to reproduce:
1. Open the attached project
2. Navigate to Build Settings (File->Build Settings)
3. Enable the "Create Xcode project" option
4. Build the project
5. Open the created Xcode project
6. In the Xcode IDE, Build the Xcode project (Product->Build)
7. Observe the Console
Expected result: GameAssembly error is not thrown
Actual result: "GameAssembly.map: No such file or directory" error is thrown
Reproducible with: 2018.4.26f1, 2019.4.9f1, 2020.1.4f1, 2020.2.0a18 (Target Platform "Mac OS X")
Not reproducible with: 2020.2.0a19 (Target Platform "macOS"), 2020.2.0b1 (Target Platform "Intel - 64")
Couldn't test with Target Platform "Silicon"
Workaround: Use the "New Build System" in the Xcode project (Can be changed in File->Project Settings)
Comments (1)
-
sbsmith
Jan 25, 2021 20:33
This seems to also be present in 2019.4.17
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
- Particle System emission ignores the Sprite Atlas when using a Material that has the "Include in Build" setting unchecked
- [Android] [Windows] The frame buffer is replaced incorrectly when using Framebuffer Fetch
- Crash on Scripting::SetCachedPtrOnScriptingWrapper(ScriptingObjectPtr, Object*) when exiting a project
- WASM Heap size greatly increases when UI elements are present in a WebGL build
- Crash on mdb_node_add when opening a specific project with a corrupted Library
Resolution Note:
Not reproducible with Target Platform "Intel - 64", available in Unity 2020.2.0a20 and above