Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0a10
Issue ID
1104723
Regression
No
[iOS] Locking device while debugging, debugger disconnects from the process
How to reproduce:
1. Open the attached project
2. Switch platform to iOS
3. Make sure that Scripting Runtime Version is set to .NET 4.x Equivalent
4. Open Build Settings and enable Development Build and Script Debugger
5. Build and run project on iOS device
6. Close XCode
7. Open script in Visual Studio (breakpoints are not needed)
8. Open project on device
9. Go to Run -> Attach to Process in Visual Studio
10. Find UnityPlayer iPhonePlayer -> select it and Attach
11. While it is debugging lock the screen
Result: debugger stops debugging and it forgets the process. If you repeat step 9, you won't find UnityPlayer iPhonePlayer.
Note: If screen is locked when debugger hits the breakpoint, then this issue doesn't reproduce
Reproducible: 2019.1.0a10, 2019.1.0a2, 2018.3.0b11
Tested and reproduced on: iPhone 8plus iOS 12.0, iPad Pro 10.5" iOS 10.3.3
Tested and din't reproduce: VLNQA00150, Samsung Galaxy S9 (SM-G960U), Android 8.0.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
The managed debugger cannot re-attach to a device after the device is locked. Instead, the application should be restarted on the device.