Detailed use of Android permission halopermission

1. Regular use

Request a permission and receive the result callback

Request multiple permissions

Only callbacks with permission allowed (not allowed) are concerned

2. Using rational erender

If you want to explain to the user why permission is requested, you can use the setrational erender method

If you want to customize the style of rational erender, for example:

Trigger description of this callback:

3. Settingrender use

If you want to explain to the user why permission is requested, you can use the setrational erender method

If you want to customize the settingrender style, for example:

If you think the permission setting interface opened by halopermission is not satisfactory to you, you can override the getcustomsettingintent method of settingrender to provide an intent. If NULL is returned, it will be opened in the default mode of halopermission:

4. User defined permission verification rules

Two steps

Unless you are very sure, it is not recommended to use custom permission verification rules, because halopermission will be adapted and compatible as much as possible

5. Custom request method

Halopermission requests permission in the form of shadowactivity by default. Of course, you can implement it in the form of fragment if you like. Halopermission also provides the request method of fragment, but the implementation of this part is finally removed, because some strange problems may occur if the fragment use mechanism is not used properly, I think this is what you and I don't want to see. Similarly, you can customize the request mode in two steps

The above is the whole content of this article. I hope it will be helpful to your study, and I hope you can support programming tips.