[Permissions] A better way to handle permissions easier.

[erfansn]

Description

Unfortunately, the current API is not something that makes the work of programmers easier, and everyone should rewrite the logic based on possible scenarios. Based on the topics that were raised in previous issues, I have a new solution to propose, which is based on callback work. and handles the following scenarios correctly, and if approved, I will create the corresponding pull request:

• Touch the outside of the permission dialog

  • No matter how many times this action occurs, nothing happens until the permission status is explicitly set by the user.
  • When the permission status is specified and Denied is selected, the callback corresponding to rationale show will be called.

• Granting partial or all permissions from the app settings before the first run

• Being clear about what permissions have been explicitly granted in the first place

• Make a distinction between whether permissions have been permanently denied or are being requested for the first time

[bentrengrove]

We aren't looking to change how Accompanist permissions works at this time. I would encourage you to release your own library with this idea. Thanks for the submission.

[akardas16]

Description

Unfortunately, the current API is not something that makes the work of programmers easier, and everyone should rewrite the logic based on possible scenarios. Based on the topics that were raised in previous issues, I have a new solution to propose, which is based on callback work. and handles the following scenarios correctly, and if approved, I will create the corresponding pull request:

• Touch the outside of the permission dialog

  • No matter how many times this action occurs, nothing happens until the permission status is explicitly set by the user.
  • When the permission status is specified and Denied is selected, the callback corresponding to rationale show will be called.
• Granting partial or all permissions from the app settings before the first run
• Being clear about what permissions have been explicitly granted in the first place
• Make a distinction between whether permissions have been permanently denied or are being requested for the first time

I am using similar to your solution in android view system, there are some cases which android remove all permissions if app is not used in long time by user but values stored in shared preferences won't change in that case. How will this affect solution you described?