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
{{ message }}
This repository has been archived by the owner on Aug 11, 2021. It is now read-only.
Using the Android permission GET_TASKS in an Android app,
triggers the following permission request while installing the app:
** Device & app history.
** Allows the app to view one or more of:
** information about activity on the
** device, which apps are running,
** browsing history and bookmarks.
Users get suspicious about what the app does with this personal information.
I looked at the code and I don't see why we would need this permission request.
If it is used with activity intents to handle the back stack, couldn't this be solved with an:
android:noHistory="true" attribute in the AndroidManifest?
Hope you can work around this permission.
Best Regards, Stefan
The text was updated successfully, but these errors were encountered:
Thanks for highlighting this. It was a long time ago since I wrote the QuickStart app and I honestly can't remember why this line is included. I just tested the QuickStart app and to me it functions exactly the same without the GET_TASKS permission so I have just removed it. Am all in favour of reducing unwanted permissions.
I will have another look at the noHistory option soon, as the way I currently handle the Back Stack is not the prettiest.
Thanks
Steve
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Using the Android permission GET_TASKS in an Android app,
triggers the following permission request while installing the app:
** Device & app history.
** Allows the app to view one or more of:
** information about activity on the
** device, which apps are running,
** browsing history and bookmarks.
Users get suspicious about what the app does with this personal information.
I looked at the code and I don't see why we would need this permission request.
If it is used with activity intents to handle the back stack, couldn't this be solved with an:
android:noHistory="true" attribute in the AndroidManifest?
Hope you can work around this permission.
Best Regards, Stefan
The text was updated successfully, but these errors were encountered: