You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Don't have an option to write a PR(debugged), so I rather ask beforehand. When I use custom launcher, I put there every permission I know could be at least a little bit useful. As the launcher isn't intended for final distribution, e.g. __init__.py could be a nice place for a list of all available permissions.
Then --permission ALL would be possible as it'd only need to have a simple loop in each build.py that can build the launcher(or even in all builds). However, I can see ALL not available in arguments as a safety switch too for the final dist.
Is it a good idea to include ALL into p4a? pros could be simple process of adding permissions, maybe future check if permission is typed correctly(in a list of permissions) and maybe prevent crashes this way(don't know if there is some check for this), then make updating custom(I don't want you to go for stable launcher with all permissions) one less frequent. This could make the launcher slowly become "ide" on android for Kivy.
Two critical cons are basically disabling permission security at all with this(app would have ALL) and a risk that some beginner would go for this craziness in final dist.
Activity
KeyWeeUsr commentedon Oct 8, 2016
If not access to all, then at least to permissions that are profitable for kivy apps with plyer or for those working directly with the shell (more):
Julian-O commentedon Nov 18, 2023
Given we have no launchers currently live (or planned to be live), closing this as Not Planned.