Search Issue Tracker
By Design
Votes
0
Found in
2019.1.0a13
2019.2.0f1
Issue ID
1174462
Regression
Yes
[Android] Application freezes when permission for GPS or camera is allowed on Android devices
To reproduce:
1. Download attached project
2. Build and run to android device
3. Hit the "Show Camera Permission" button
4. Allow Camera Permission
5. Hit the "Show GPS Permission" button
6. Allow GPS Permission
Actual result: After pressing the permission buttons app freezes
Expected result: The application should not freeze after pressing permission buttons
Reproduced on: 2019.1.0a13; 2020.1.0a1
Not reproduced: 2018.4.7f1; 2019.1.0a12
Tested on:
VLNQA00277, Asus ROG Phone (ASUS_Z01QD), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00262, Sony Xperia XZ Premium (G8141), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00138, Huawei P20 Pro (CLT-L29), Android 8.1.0, CPU: HiSilicon Kirin 970, GPU: Mali-G72
VLNQA00224, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00219, Samsung Galaxy Note9 (SM-N960U), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
Note: showing any permission dialog second time makes the app freeze indefinitely. But then if you hit home screen and open the app again, it starts normally.
Note: logcat attached
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
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Resolution Note (2020.1.X):
Tried on two different devices. It worked fine with GPS button, freeze only happens for camera. Looking into log I see "Denied" being printed. Without knowing how the users plugin works I can only conclude that camera permission is denied without even showing UI and users code doesn't handle this condition properly and locks up the UI. Sending app to background and bringing it up again unlocks it.
I see user using some locks in scripts and I believe those are to blame, hence user error. I consider this to be a user error unless we are provided with exact details why it hangs and why it's our bug, and the source code for native plugins.