No IMHO that's a bad idea. The user expects the permission request to happen exactly when an action was actually prompted that needs it - otherwise, it seems like a malicious app that wants unrestricted permissions of everything right at launch to mess your phone up. (Exactly why Google introduced this system)

p4a would need to add API calls for each permission type for the app to consciously request these at runtime, and return True/False depending on whether the user gave permission. For a phone that has an older API without checkSelfPermission() being present, those calls should ideally just return True.

Also it would be good to make sure the functions in PythonActivity are thread-safe and don't access global state, because checkSelfPermission is blocking (for the duration of the popup dialog being visible, if I understand google's documentation correctly) and some apps may want to call them from a side thread to keep some sort of action (e.g. network connections) running. Please note this also means the GIL should be released while PythonActivity is in this function

p4a doesn't handle runtime permissions #1183

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions