Android Marshmallow 6.0: Asking For Permission
Why Stack Overflow recommends it
Stack Overflow users link it when answering questions about Marshmallow runtime permissions, as the official guidance on request timing, UX and sending users to the app settings page.
Recommended by 4 people across 4 different months, 2015 to 2019.
What it is
A short Android Developers video in which Nick Butcher explains the runtime permission model introduced in Android 6.0 Marshmallow. It covers when and how to ask users for permissions, and how to design the request flow so that permissions are more likely to be granted.
What people said
Recommends Pankaj Kumar · 2015-10 · Stack Overflow · on “Android Marshmallow - permissions state change”
No. You will not get any broadcast for it. On each call of a feature, which needs permission, you need to check if permission is granted or not. Read Request App Permissions [LINK] , a well documented, and covers each point which you need to take care of. It seems Google has achieved the official sample [LINK] , but still, you can find some useful information from the sample. And at last watch Android Marshmallow 6.0: Asking For Permission [this video] to design your app in a better way. Note: Also read, Permissions updates in Android 11 [LINK] ,
Recommends BalaramNayak · 2016-03 · Stack Overflow · on “Not able to create the folder in external storage in marshmallow version”
As marshmallow introduce Run time Permission you have to check for the permission in run time. You can refer here 1. [LINK] 2. [this video] 3. [LINK] You have to accept the STORAGE permission group from the user dynamically. Go with the below link [LINK]
Recommends Programmer001 · 2018-10 · Stack Overflow · on “File creation failing without exception”
Your code is probably throwing a file not found exception. After downloadLocation.mkdir() call: if (downloadLocation.exists()) { System.out.println("File Exists"); } You'll notice the message won't print. This is because you never had permissions to write to the directory. Add the following to your AndroidManifest.xml: <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> An easy way to handle requesting permissions is a great library: EasyPermissions [LINK] Using EasyPermissions, your code might look like: 1.) You call a function in your activity to trigger creating the file: @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceSta
Recommends StefanaB · 2019-01 · Stack Overflow · on “Android app request permission before installation”
Since android marshmallow, is implemented to require the permissions at runtime, rather than at the installation. You can check this link: [LINK] and this explaining video: [this video]
Cites Martin Konecny · 2015-10 · Stack Overflow · on “How can I programmatically open the permission screen for a specific app on Android 6.0 (Marshmallow)?”
According to the official Marshmallow permissions video (at the 4m 43s mark [this video] ), you must open the application Settings page instead (from there it is one click to the Permissions page). To open the settings page, you would do Intent intent = new Intent(Settings.ACTION_APPLICATION_DETAILS_SETTINGS); Uri uri = Uri.fromParts("package", getPackageName(), null); intent.setData(uri); startActivity(intent);
Cites ianhanniballake · 2015-10 · Stack Overflow · on “Go to My app's App Permission screen”
No, there is no intent to go directly to the Permissions screen. However, just as in previous versions of Android, you can point people to your application's detail setting page using code such as: Intent intent = new Intent(Settings.ACTION_APPLICATION_DETAILS_SETTINGS, Uri.fromParts("package", getPackageName(), null)); intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK); startActivity(intent); This will allow them to only hit a single button (the Permissions button on that screen) before they can access permissions. Note that as per the UX around asking for permissions [this video] , consider linking to the settings page only as a last resort and only in cases where the permission is necessary for yo
Cites the_new_mr · 2016-11 · Stack Overflow · on “How Do We Distinguish Never-Asked From Stop-Asking in Android M's Runtime Permissions?”
I tried this mechanism but alas, it didn't cover all scenarios. If you allow permission within app and then go to permission settings and deny it, the boolean stored in shared preferences is still true (from before) where you need it to be false. shouldShowRequestPermissionRationale is fine if you don't plan to ever educate up front but, if you do, it's no good. There should have been a "shouldEducateUpFront" method to determine cases where a user has not previously denied a permission. Especially since Google recommend doing so in some cases: [this video]