Kindly note that we filter out plugins that:
$ tns plugin add nativescript-permissions
A NativeScript plugin to deal with Android permissions (mainly for API 23+/Android 6+)
Has a dummy library for iOS so that if ask it for any android permissions; it will resolve every one of them as true...
This is released under the MIT License, meaning you are free to include this in any type of program -- However for entities that need a support contract, changes, enhancements and/or a commercial license please contact me at http://nativescript.tools.
I also do contract work; so if you have a module you want built for NativeScript (or any other software projects) feel free to contact me email@example.com.
You can see me do something that requests permissions; then I deny the permissions. The second time through you will see the toast about why I think I need these permissions; then I finally accept them.
This requires NativeScript 2.0 or greater
tns plugin add nativescript-permissions
To use the module you just require() it:
var permissions = require( "nativescript-permissions" );
This wraps up the entire Android 6 permissions system into a nice easy to use promise. In addition, you can also have multiple permissions pending and each one will resolve properly.
var permissions = require('nativescript-permissions');
permissions.requestPermission(android.Manifest.permission.READ_CONTACTS, "I need these permissions because I'm cool")
console.log("Woo Hoo, I have the power!");
console.log("Uh oh, no permissions - plan B time!");
The explanation won't be showed unless they have denied the request once.
This simplifies the checks and allows you to have two courses of action depending on the results of the permission request.
The granted or failed promise will return an object keyed to the your permissionName Like so:
If you are granted and receive all permissions, then it will resolve with the granted permission promise. If you failed to get even one of the permissions then it will then resolve the failed/catch promise; then you can use the object list to determine which permission(s) you failed and were granted by the end user.
So in the above example object, this would have been resolved to the failed promise because you failed to get the camera access.
Because this uses support.v4; this code works on ALL versions that nativescript supports currently. So you can start coding this into your app at this point and your app should work on everything.
You still need to put all the permissions you need in the manifest as usual, even on Android 6. On Android 6 you ALSO must ask the user for permissions each time you go to do anything that needs a "dangerous" permission. You can see all the permissions at https://developer.android.com/reference/android/Manifest.permission.html.
Warning: even though the application has been granted permissions once, does NOT mean the app still has permissions; the user can revoke the "dangerous" permissions even while the app is running. So again YOU MUST use requestPermissions each time. If the app still has the permissions you will be granted it immediately without the user seeing a dialog.
In NativeScript when using the permissions names/strings in your code; they are accessed as: android.Manifest.permission.PERMISSION_NAME rather than the android.permission.PERMISSION_NAME that you would put inside the manifest and are listed on the Android documentation site listed above.
The Android manifest that you need to put the permissions in also is located at /app/App_Resources/Android/AndroidManifest.xml
Popularity metric based on:
Quality metric based on:
Maintenance metric based on: