KPermissions 3.5.0

• Fixed the issue #303 adding the support to send permission requests in parallel
• Add API to support a list of permissions as input (suggested in the issue #379)
• Updated Kotlin from 1.7.20 to 1.9.22
• Updated Kotlin coroutines from 1.5.4 to 1.8.0
• Updated AndroidX AppCompat from 1.5.1 to 1.6.1
• Updated AndroidX Fragment from 1.5.4 to 1.6.2

KPermissions 3.4.0

• Updated Kotlin to from 1.6.10 to 1.7.20
• Updated Kotlin coroutines from 1.5.2 to 1.5.4
• Updated AndroidX Fragment to from 1.3.1 to 1.5.4

KPermissions 3.3.0

• Fixed ConcurrentModificationException when updating the listeners while iterating on them in another thread (#288)
• Removed legacy implementation of RuntimePermissionHandler and all its deprecated usages
• Updated Kotlin to from 1.4.31 to 1.6.10
• Updated Kotlin coroutines from 1.4.3 to to 1.5.2
• Updated AndroidX Fragment to from 1.3.1 to 1.4.0
• Updated RxJava3 to from 3.0.8 to 3.0.13

KPermissions 3.2.1

• Fixed bug happening when the permission request was sent as soon as its container (activity or fragment) was created (#213)
• Updated AndroidX Fragment from 1.3.0 to 1.3.1

KPermissions 3.2.0

• Fixed bug on listener which wasn't notified when the request contained implicit permissions (e.g. Manifest.permission.BLUETOOTH) (#200)
• Updated the internal implementation of RuntimePermissionHandlerProvider using the ActivityResultLauncher API and deprecated the old one (FragmentRuntimePermissionHandlerProvider)
• Updated AndroidX Fragment from 1.2.4 to 1.3.0
• Updated Kotlin stdlib from 1.4.10 to 1.4.31
• Updated Kotlin coroutines from 1.4.1 to 1.4.3
• Updated RxJava3 from 3.0.6 to 3.0.8
• Updated RxJava2 from 2.2.20 to 2.2.21

KPermissions 3.1.3

• Fix bug when using both WRITE_EXTERNAL_STORAGE and READ_EXTERNAL_STORAGE in a request (#159)
• Updated AndroidX Fragment from 1.2.3 to 1.2.4
• Updated Kotlin stdlib from 1.3.72 to 1.4.10
• Updated Kotlin coroutines from 1.3.7 to 1.4.1
• Updated RxJava3 from 3.0.1 to 3.0.6
• Updated RxJava2 from 2.2.19 to 2.2.20

KPermissions 3.1.2

• Updated Kotlin from 1.3.70 to 1.3.71
• Small optimization to sendSuspend() API (:kpermissions-coroutines)

KPermissions 3.1.1

IMPORTANT: if you are using :kpermissions-coroutines, kpermissions-rx2 or kpermissions-rx3, apply the following fix or upgrade to the version 3.1.2.

implementation("com.github.fondesa:kpermissions:3.1.1")
implementation("com.github.fondesa:kpermissions-coroutines:3.1.1") {
    exclude group: "kpermissions"
}

• Updated Kotlin from 1.3.70 to 1.3.71
• Small optimization to sendSuspend() API (:kpermissions-coroutines)

KPermissions 3.1.0

On the main artifact:

• Fixed a bug related on the save instance state of a runtime permission request (#78)
• Added the LiveData support
• Added send { } inline API

Added the secondary artifacts:

• com.github.fondesa:kpermissions-rx2
• com.github.fondesa:kpermissions-rx3
• com.github.fondesa:kpermissions-coroutines

KPermissions 3.0.0

This is a major release.
It introduces the new callback system using the PermissionStatus API.
All the previous callbacks introduced before the version 3.0.0 are deprecated and should be replaced with the new API.
The deprecated API will be removed in the version 4.x.
To learn more about the PermissionStatus API check the docs and the wiki.
The motivation behind these big changes is to provide the most flexible way to handle a permissions request.
Even if the versions 1.x and 2.x could seem simpler to use, they forced the lifecycle of a permissions request I thought it was the standard to most of the users.
The version 3.x. doesn't make such assumptions and lets the users to choose how to handle them providing a callback which follows the Android style of onRequestPermissionsResult().