Android Question Best Practice for Managing Runtime Permissions in B4A Across Android Versions?

[jhonnmick]

Hello everyone,

I’ve been updating an older B4A app and I’m trying to streamline how runtime permissions are requested and managed across different Android versions (especially from Android 10 to 14).

I’m currently using RuntimePermissions and it works fine for simple flows, but I’m unsure about best practices when:

• Multiple permissions (e.g., location + storage) are required together
• A permission is denied permanently ("Don't ask again")
• Permission logic affects navigation or layout flow

Also:

1. Is there a centralized module or template anyone recommends for managing permission requests and fallbacks?
2. Any known issues with targetSdkVersion 33+ or scoped storage behavior that I should account for?

I'd really appreciate any examples or updated libraries that can simplify this part of development.

Thanks in advance!

— jhonnmick

 

[Erel]

There isn't anything dramatic related to the handling of permissions and different Android versions.

It is usually a matter of checking Phone.SdkVersion to decide whether a permission is needed or not.

Example of handling multiple permissions, based on Android version: https://www.b4x.com/android/forum/threads/b4x-ble-2-bluetooth-low-energy.59937/#content