Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2017.4.X
Votes
0
Found in
5.6.3f1
Issue ID
946796
Regression
No
[Android] In dev mode the app is drawn on top of the lock screen which blocks native content (e.g keyboard)
How to reproduce:
1. Open QA attached project
2. Set up any lock protection (Pattern, pin, password etc) on the device
3. Deploy the app to device in Dev mode
4. Lock and then wake up the device
5. Touch InputField to call the keyboard
-- Notice the keyboard is not displayed
Actual behaviour: Native content not displayed since the phone is 'locked'
Reproduced on: 5.6.4p4, 2017.1.2p4, 2017.2.1p1, 2017.3.0f3, 2018.1.0b1
Devices under testing
Reproduced using:
Google Pixel XL*, OS:8.0.0, CPU:arm64-v8a, GPU:Adreno (TM) 530, Build:google/marlin/marlin:8.0.0/OPR6.170623.012/4283428:user/release-keys
Razer Phone*, OS:7.1.1, CPU:arm64-v8a, GPU:Adreno (TM) 540, Build:razer/cheryl/cheryl_ckh:7.1.1/NMF26X-CKH-171108/853:user/release-keys
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
Add comment