Search Issue Tracker
Not Reproducible
Votes
0
Found in
2019.2.0a5
Issue ID
1126863
Regression
Yes
[iOS] The whole project recursively copies itself into the Build folder when Building Xcode project
To reproduce:
1. Download attached project “case_1124821-iosPluginTest 2.zip" and open in Unity
2. Open "EmptyScene" scene
3. Go to your project location and from "Library" folder delete "PackageCache" folder
4. Go back to Unity Editor and wait for recompilation
5. Make sure that Platform is set to iOS
6. Build project
Expected results: Unity Editor successfully builds Player
Actual results: Build process hangs on "Closing Open Unity projects in Xcode" and the whole Project starts recursively copying itself into the Build folder that leads into Crash because it eats the whole Storage
The whole Unity root project folder is copied into <xcodeBuildDir>/Libraries.
Notes:
- This issue happens only on iOS
- This issue could happen because there are one or more Plugins in Project
- If You cannot reproduce this issue, restart Unity and try again
Reproduced on Unity 2019.2.0a5
Not reproduced on Unity 2019.2.0a4
Regression on Unity 2019.2.0a5
Should also reproduce on latest 2018.3
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
- [iOS] App crashes when trying to use WebCamTexture depth data on back triple camera
- [Mobile] Only second base Camera out of two base Cameras with priority 1 and -1 is rendered in the Player
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
JPLee
Feb 05, 2020 15:36
I got this today on a Mac on version 2019.2.12f1 Same occured for me, It's recursively copying items into the Build folder.
wanzhang
Nov 12, 2019 11:26
did occur in 2019.2.11.f1 . update project from 2018.4.4f1.
fhickman
Sep 20, 2019 18:30
I ran into the same thing with Unity 2019.2.4f1. It seems to have been a side effect of doing an in-place upgrade from an earlier Unity (in my case, 2018.4.2f1).
After nuking the Library directory and reimporting, the issue was resolved.
joshuacwilde
Sep 05, 2019 21:59
I had this same issue on 2019.2.1f1. It was creating a massive amount of data very quickly in the same manner as described above (in the Libraries folder).
I quit Unity, deleted the Temp, Library, and old build folders and then opened it back up. I then set it to build at a new location. It then built fine.