Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2018.2.0b1
Issue ID
1026831
Regression
No
[UWP] Player will not boot if a non-development build is made while Script Debugging is still checked
In the UWP Build Settings, if you turn on both Development Build and Script Debugging and then disable Development Build, the Script Debugging box will remain checked but greyed out as expected.
If you then make a build however, the UWP player will throw an unhandled exception if attached to Visual Studio, or just crash if not attached. It seems as though we aren't disabling the Script Debugging option correctly in this situation.
1. Boot Unity
2. Create a new UWP project
3. Open Build Settings
4. Turn Development Build ON
5. Turn Script Debugging ON
6. Turn Development Build OFF
7. Create a build
8. Attempt to run the build
Tested on 2018.2.0b1, 2018.2.0a7
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity Cloud icon does not appear next to project and does not connect correctly when the project is created with Cloud but closed right after creation
- ScrollerSlider in the Scroller Control is still using UXMLTraits
- Crash on ExtractHandles when shutting down the Editor in a specific scene while Burst jobs are in progress
- Unity Hub closes with no "Project is currently open" window when selecting an already open project from the Projects list
- The Hub freezes indefinitely when copy/pasting a lot of characters in the “Set project display name” Hub window since it has no character limit
Add comment