Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
2017.1.0b2
Issue ID
923668
Regression
No
"Uncheck 'Scripts Only Build' and try again." error is thrown when "Scripts Only Build" is unchecked
Steps to reproduce:
1. Create a new project
2. Open Build Settings
3. Check Development Build
4. Check Scripts Only Build
5. Uncheck Development Build
6. Build and Run
7. Observe the error
Expected result: Unity should build normally
Actual result: Unity throws the error
Note:
"Scripts Only Build" is introduced in 2017.1
Reproduced with: 2017.1.0f1, 2017.2.0b1
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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
russ_magicleap
Aug 03, 2017 21:09
What is the work around?