Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0b2
Issue ID
1082263
Regression
No
[BuildFolder] Building app using duplicate project picks original project's folder
How to reproduce:
1. Create a new project
2. Build SampleScene
3. Close project
4. Right click on project folder and Compress it
5. Unzip the project (folder name can be renamed)
6. Open unzipped project and build on same platform
Actual result: notice the folder selected to build the app to is of original project
Expected result: it should select folder of the project which is open
Reproducible: 2018.1.9f1, 2018.2.5f1, 2018.3.0a1, 2018.3.0b2, 2019.1.0a1
Note:
Tested using Mac Standalone, iOS and Android
Tested on MacBook Pro (2017) OSX 10.13.6
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Given that we use absolute paths to save the build location there's no reliable way to determine that we shouldn't be using the original build path in the new project.