Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2020.2
2021.1.0a3
Issue ID
1288729
Regression
Yes
[Mac OS] Building Standalone project for Mac when Generate Xcode project is enabled generates both a folder and .xcodeproj
Reproduction steps:
1. Create a new project
2. Go File -> Build Settings
3. Select standalone Mac platform
4. Enable the "Create Xcode Project" option
5. Click "Build"
6. You will be prompted to choose the build location
Expected result: You will be able to choose where xcodeproj will be located, both project and accompanying files will be generate inside selected location
Actual result: You must select a folder type file to begin the build. After the build completes xcodeproj file is created next to selected location and accompanying files are missing
Reproducible with: 2020.2.0b10, 2021.1.0a3
Not reproducible with 2019.4.14f1, 2020.1.12f1
Could not test with 2018.4 because you cannot make Xcode projects for OSX
Notes:
1. This issue appeared after fix in case 1265065 (previously there were other issues)
2. With iOS OSX tvOS builds cannot be built in the root of the project (invalid path exception)
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 (fix version 2020.2):
Fixed in 2021.2.0a5.926
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0f1.3687