You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the location permission is denied for the app in a specific way the app screen keeps flashing with the "Requesting Location Permission" dialog being visible.
Steps to reproduce:
Ensure the device's location is turned off
Use a fresh installation of the app
Log-in to the app
Tap on "Nearby".
You'll see the location permission request
Tap outside the permission dialog.
You're shown the location permission request again (twice). Tap on "Don't allow" in both cases.
System logs:
Let me know if this is necessary.
Device and Android version:
OnePlus Nord running Android 11
Commons app version:
3.1.1~1c9267ca0
Screen-shots:
Here's a screen recording:
22-01-23-17-17-49.mp4
Would you like to work on the issue?
Prefer not.
The text was updated successfully, but these errors were encountered:
It's a problem that changes from device to device and is created by the system launcher of the device itself. My MIUI12 version of android works perfectly and doesn't cause any issue here
It's a problem that changes from device to device and is created by the system launcher of the device itself. My MIUI12 version of android works perfectly and doesn't cause any issue here
I'm confused. This bug speaks about screen flashing that happens with a sequence of actions that are all within the app. How does the system launcher come into picture here? 🤔
Summary:
When the location permission is denied for the app in a specific way the app screen keeps flashing with the "Requesting Location Permission" dialog being visible.
Steps to reproduce:
System logs:
Let me know if this is necessary.
Device and Android version:
OnePlus Nord running Android 11
Commons app version:
3.1.1~1c9267ca0
Screen-shots:
Here's a screen recording:
22-01-23-17-17-49.mp4
Would you like to work on the issue?
Prefer not.
The text was updated successfully, but these errors were encountered: