Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0b8
Issue ID
916867
Regression
Yes
[Regression] Standalone is building to Assets folder by default (which is not allowed)
Starting from 2017.1.0b4 when you build Standalone player the Editor suggests to build it in Assets folder and when you try to Build - give errors as building to Assets folder is not allowed
Also reproduces in 2017.2.0a1
How we can reproduce it
1 Create new project
2 Save scene
3 Go to menu File->Build Settings ...
4 Select Standalone and press Build
Actual results:
Editor tries to build Standalone to Assets folder
Expected results:
Editor should suggest project's root folder to build Standalone in
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
tckerr
Jul 18, 2017 01:01
This happened to me, I accidentally selected it, and now my project can't be build because I get a perpetual error: "Building to the Assets folder is not allowed."
tckerr
Jul 18, 2017 01:01
This happened to me, I accidentally selected it, and now my project can't be build because I get a perpetual error: "Building to the Assets folder is not allowed."