I have got this really weird behaviour.
After adding the permissions at runtime for my app, I was checking and testing all cases.
I have the request code in my MainActivity.
So, after I set Never Ask Again and deny the giving permission for ACCESS_FINE_LOCATION, if I press the menu button and then restart the app (the app will call onResume of MainActivity I guess), then the screen is black except a rectangle part in the middle of the screen which varies in size. (Is not the AlertDialog size)
Here some screenshots:
Normal screen
After press menu and then open again can be that it opens with the normal state or with these states:
Or
This is quite weird, anybody had this before?
Thanks for your answers!
Without seeing the code, it's hard to give a very accurate answer.
When requesting permissions, if the user selected 'never ask again', the request permissions response will be denied. I'm GUESSING (due to lack of code) that your app relies on the granted permission to continue loading the UI and executing more code, which it won't do if permission is denied. You need to handle all possible responses when requesting runtime permissions.
if permission is granted: good to go
if permission is denied: check if you should show the permission rationale. This means you display a message to the user explaining why you need the permission.
if shouldShowRationale is true: it means 'never ask again' was NOT checked. Display the message, then ask for permission again.
if should show Rationale is false: it means 'never ask again' was checked and you should probably direct the user to the app settings to turn the permission on if it's required.
Related
I'm use ActivityResultContracts to request runtime permissions. Here is my code:
private val contactsPermissionLauncher =
registerForActivityResult(ActivityResultContracts.RequestPermission()) { granted ->
// some logic here
}
And in onCreate():
contactsPermissionLauncher.launch(Manifest.permission.READ_CONTACTS)
Accordingly, I should be request for permission every time I go to the activity/fragment.
At first glance, everything works well. However, I noticed such a problem, on Android 11, after a certain number of times the permission was denied, when re-navigating to the screen, permission is not requested (that is, the system dialog is not displayed).
And also on android 6, it was noticed that after a lot of permission denial, after the next display of the system dialog asking for permission, when trying to allow, the button does not respond, while the deny button works correctly.
Can you please tell me what could be causing these problems? Perhaps there is a permission request limit?
Please, help me(
User can cancel a permission request by hitting the "Back" button. And since Android 11, user can also clicking on the outside of the permission dialog to cancel. When a permission is canceled, the permission is not granted, and shouldShowPermissionRationale() will return false, which means app can call requestPermissions() again.
When user choose "Don't ask again", or deny twice for a permission in Android 11, shouldShowPermissionRationale() will also return false. But how can I distinguish "Don't ask again" from the "Canceled" state?
I need to distinguish these two states is because that if user canceled a permission before, I know that I still have the chance to prompt the system permission dialog to them. But if user choose not to ask for a permission again, I need to guide them to the app info page to grant the permission manually.
It's not a direct solution to this problem because there appears to be no way to get that.
However, I have realised that there is a method where Android will tell us if we need to show RationaleDialog to our user without any work from our end (before I was under impression we need to keep track of this ourselves).
Just call activity.shouldShowRequestPermissionRationale(permission) and it will take care of all back calls itself.
In Android OS 11, apps targeting SDK 30+. We get a permission dialog with three buttons when we request location -foreground permission for the first time.
As per documents it is given that OS is granting permission for this time only.
https://developer.android.com/about/versions/11/privacy/permissions#one-time
When I am clicking on "Only this time".
As per the user's perspective, the permission should ask again. When I am coming back.
But In actual Operating systems granting the permission.
Why this is happening. Is this system behavior?
Do I need to do any changes app-side?
Thanks in anticipation.
In Android OS 11- If we are granting permission “Only this time”. It means the OS is granting permission for next some time.
When you are immediately opening the app or your app is in the background and opening the app again you will find permission granted.
If you are coming after some time you will see the permissions not granted.
Permission popup reappears.
some more findings on android OS 11:-
till Android OS 10, the shouldShowRequestPermissionRationale function returned false for the first time, but in OS 11 shouldShowRequestPermissionRationale function returns true for the first time and when the user is in a confused state as explained in the document.
Till android OS 10, android OS permission popup gets displayed if shouldShowRequestPermissionRationale is true and when we are requesting permission for the first time. after that, if shouldShowRequestPermissionRationale is false the permission popup will not display.
But in OS 11 we are able to see a popup no matter the shouldShowRequestPermissionRationale return true or false.
Hope this will help someone. please correct if anything wrong.
I've set my app to target AP 29 and removed requestLegacyExternalStorage=true from manifest.
Now I'm checking if the user has this permission and if result is denied I request for permission.
My problem is that the request for permission is returning Granted without showing the prompt... I know the flow is working since I'm able to read the GPS location from picture after being granted.
I see permission status = Denied and as soon as I explicitly request this permission, it returns Granted without any user interaction.
Eveything looks OK but I'm confused about not seeing the prompt... is this expected? I saw this permission qualifies as "Dangerous" so I was expecting a prompt. I'm testing on a Android 10 device.
I'm not showing any code since the project is Xamarin and the permission logic is handled through a third party library, don't think my code will help as the platform logic to request the permission is hidden by the component.
From
Android 10: fetch the gallery via MediaStore with location information :
This requires holding the ACCESS_MEDIA_LOCATION permission. Note, this permission is not "user visible in the settings UI" (source), which means the user won't see a popup asking for permission, even though it is a runtime permission. This means you have to ask for permission during runtime (in contrast to just the manifest file) but the user won't have to consent to it. Adding this here because you might be wondering why no extra UI popups are shown.
I'm still getting my head around the logic though. I'm in favour of the user being asked for permission but I don't understand why it should be necessary to "request" it if the user doesn't actually grant permission.
I was able to reproduce the issue in a simpler app. I have posted a slightly different question with code snippets.
This is an answer by HilaryN that I believe should not have been deleted (I removed the off-topic bits).
I couldn't find any information about what happens when the user disables an app's permission while the app is running.
Is the application re-initilized?
I saw that in some apps if a Dialog or BottomSheet is open while I disable the permission, the dialog is no longer displayed when I return to the app.
Can anyone explain what happens in-detail when a permission is denied at runtime? Or does anyone have some useful links for me?
I would be especially interested in which lifecycle events are called when returning to the app.
When a previously granted permission is revoked through settings, the app is force stopped. You can see this by watching your app in the debugger. The app process is marked DEAD as soon as the permission is revoked.
Returning to the app will launch it from the main activity. I've never really looked into why this happens, but I assume it's because when a granted permission is revoked, the user could be deep into the app at a place where it is assumed the permission is granted. When the permission is revoked, there's no way to know if the screen they are currently in is even valid anymore.
Upon returning to the app, the app's state is restored and your current activity will be restarted, similar to a configuration change. If the activity you are in assumes a certain permission is granted, you should probably check that permission again in onCreate() to make sure you have it.
Simply put, That depends on what the app is trying to do when it needs permission.
For example: If we live in a country that requires you to be an adult to watch any video on YouTube, nothing will work with Location permissions denied
Another example: If you want to take photos using your phone via an app, the Camera permission should be permitted.
Under some circumstances, just part functions of app can not be used, but at an Extreme case, app would throw Security Exception and crash.
According to your point :
I saw that in some apps if a Dialog or BottomSheet is open while I
disable the permission, the dialog is no longer displayed when I
return to the app.
There is no lifecycle callback about what you do once permission is denied, but there's method on ActivityCompat which gives you flag if you want to show your own Dialog/BottomSheet
So, you can call shouldShowRequestPermissionRationale() method from ActivityCompat & make your own logic work when it's true.
shouldShowRequestPermissionRationale :
Gets whether you should show UI with rationale for requesting a permission. You should do this only if you do not have the permission and the context in which the permission is requested does not clearly communicate to the user what would be the benefit from granting this permission.
For example,
if you write a camera app, requesting the camera permission would be expected by the user and no rationale for why it is requested is needed.
If however, the app needs location for tagging photos then a non-tech savvy user may wonder how location is related to taking photos. In this case you may choose to show UI with rationale of requesting this permission.
While disabling permission for first time will give you callback in onRequestPermissionResult() method.