Search Results

PermissionsManager is a library that enables the management of runtime permissions. This library completely replaces the standard RuntimePermissions library with the addition of modern dangerous permissions and special permissions that require approval via the settings application. This library con
link: In the future of Android development, there will be more and more "special" permissions. I think it is necessary to include them in some library for e
link: Version 1.1 Download library from the first post. Changes: Added special permission SPECIAL_APP_NOTIFICATION in permissions constants. Added special
link: Just use next lines in your active B4XPage: Dim PM As PermissionsManager PM.CheckAndRequestPermission(PermissionsManager.) Wait For B4XPage_Permission

1. Edit: In B4XPages the permission result event signature is: Wait For B4XPage_PermissionResult (Permission As String, Result As Boolean) 2. Important to read: https://www.b4x.-jar-targetsdkversion-minsdkversion.87610/#content 261306184 If the targetSdkVersion is lower than 23 then the standard
link: It is not listed in the list of "dangerous" permissions: https://developer.android..html#normal-dangerous Did you get an error when you set targetSdk
link: hi i dont understand how to implement it in my app i want to request all dangerous at the first start (because i use some via service and dont want
link: Actually, on later Android versions you can go into app manager (Settings->Apps or Settings->Apps & Notifications), tap on the app->Permissions & then

There is a new "dangerous" (runtime) permission On Android 13+ devices required for showing notifications. When targetSdkVersion < 33, the OS will show the permission dialog automatically before the notification is displayed. Once we switch to targetSdkVersion=33 we are responsible for requesting it

as it is not a dangerous permission and you do not use runtimepermissions at all (not needed) it seems to be an Android permission-system. It is the user (not the app) which have to decide to accept permission or not. You can not overcome this i guess.

You don't need this line. You should add put the StartActivity call inside a Try / Catch block as not all devices will have an app installed that can handle pdf.
link: To make it work on emulators: Api 28, Api 31, I had to add the code in.SetComponent("android/com.android.internal.app.ResolverActivity") The emulato

1. No code needs to be added to the manifest editor. 2. The runtime permission request should be implemented based on your app specific requirements. At least parts of it.
link: Double-click on a dangerous permission (in the Permissions window) will automatically add the code needed to the manifest file and the b4a code needed
link: uhm... not even basic code, always necessary? ok, I do everything "by hand" (I also have to study how to request permissions at runtime, when they ar

You need to set it in the B4J sending code: m.Put("priority", 10) - StartServiceAt / StartServiceAtExact: You need to use StartServiceAtExact and add this "non-dangerous" permission: AddPermission(android.permission.SCHEDULE_EXACT_ALARM)

B4A Permissions PermissionsManager PermissionsManager is a library that enables the management of runtime permissions. This library completely replaces the standard RuntimePermissions library with the addition of modern dangerous permissions and special permissions that require approval via the sett
link: B4A Permissions PermissionsManager PermissionsManager is a library that enables the management of runtime permissions. This library completely replace
link: B4X OAuth Google OAuth2 It is no longer possible to use WebView to implement Google's OAuth2 authentication. The solution is to open the default br
link: B4A Colour ColourThief This is a port to B4X of the original ColorThief algorithm by Lokesh Dhakar. https://www.b4x.-cross-platform-colour-palette-ge

The following non-dangerous permission is required: AddPermission(android.permission.REQUEST_INSTALL_PACKAGES) A full example is attached. It also checks that the "installation from unknown source" option is enabled and that the external storage is writable. Example updated and is now based on F

The Runtimepermissions tutorial describes how to find out "dangerous Permissions". Every dangerous permission needs requested using Runtimepermissions. If i add your Code to an app i can see the following Permissions needed http://snapshots.basic4android.de/dangpermissions021.png CALL_PHONE and RE

Powered by ColBERT