Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.8f1
Issue ID
UUM-11690
Regression
Yes
[IL2CPP] iOS build fails when building on a different machine/user due to Il2cppBuildCache caching
How to reproduce:
1. Open the attached project (Google Drive link)
2. Build And Run
Expected result: Xcode project builds successfully
Actual result: Xcode project build fails with “tundra: error: Failed to open file "/Users/<User>/../Library/Il2cppBuildCache/iOS/buildstate/tundra.log.json" for structured logging”
Reproducible with: 2021.3.4f1, 2021.3.8f1
Not reproducible with: 2020.3.38f1, 2021.3.3f1, 2022.1.0a1, 2022.1.13f1, 2022.2.0b4, 2023.1.0a5
Reproducible on:
macOS 12.4 (Intel)
Workaround:
- Delete the Il2cppBuildCache folder in Library
Comments (2)
-
Develoop
Nov 30, 2023 16:01
Thank you! :)
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
- Multiple errors are thrown in the console while using perforce when moving an asset using shortcuts
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
Resolution Note:
We have corrected it in Unity 2022.1 and later. We're not planning to correct this in Unity 2021 versions though. You can work around the the problem by deleting the Il2cppBuildCache folder in Library directory in the Unity project when the project is moved.
Resolution Note (2021.3.X):
We have corrected it in Unity 2022.1 and later. We're not planning to correct this in Unity 2021 versions though. You can work around the the problem by deleting the Il2cppBuildCache folder in Library directory in the Unity project when the project is moved.