Search Issue Tracker
Fixed
Fixed in 1.13.1
Votes
0
Found in [Package]
1.13.0
Issue ID
ISXB-1430
Regression
Yes
Build profiles cause Editor to be stuck in infinite restart loop when input type is old and global is New or Both
{*}Steps to Reproduce{*}: # On a project where the Input System is set to {*}Both{*}, create a new build profile (I’ve tested with Web and Facebook Instant Games as targets). Set the Input System to {*}Old{*}.
# The editor will prompt you to restart, and show a warning window saying that your project is using the new input system but the player settings is set to the old input system, and ask if you want to restart and swap back to using {*}Both{*}.
*Actual results:*
Clicking *Yes* restarts the editor but triggers the warning to come up again, which causes an infinite loop until the user presses *No* or force quits Unity. This error only occurs with build profiles and not when changing the global project settings.
*Expected results:*
Clicking *Yes* will restart the editor and set the player settings back to *Both*
**See attached Google Drive links for videos of expected and actual behavior.
*Reproducible with versions:* 6000.2.0a3
*Not reproducible with versions:* 6000.0.29f1, 6000.1.0a4
*Can’t test with versions:*
*Tested on (OS):* MacOS (ARM64)
*Notes:*
*
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Resolution Note (fix version 1.13.1):
Fixed a problem with the logic to get the active player settings object that cause an infinit reimport loop.