Search Issue Tracker
By Design
Votes
0
Found in
2022.1.0a10
Issue ID
1367366
Regression
Yes
Project runs in a background after building it
How to reproduce:
1. Make sure you are using multiplay displays
2. Create a new Unity project
3. Move editor to a 2nd display
4. Build and run the project
5. Change your focus to 1st display (any app should be opened, for example, Chrome)
6. Wait until the build is finished
7. Observe that it runs in a background
8. If the issue doesn't reproduce, repeat from the 4th step
Reproduced with: 2022.1.0a10.
Didn't reproduce with: 2022.1.0a9, 2021.2.b13.
Workaround: Press the Windows key to change focus.
Note: Not sure if it's the right version where this bug regressed as the issue isn't always reproducible, but couldn't reproduce it on any other version.
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
Resolution Note:
It is intended behavior to run the built player in the background if you change focus to another application while building and running.