Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove need for QUERY_ALL_PACKAGES #101

Closed
Kaljurand opened this issue Jan 9, 2023 · 0 comments · Fixed by #106
Closed

Remove need for QUERY_ALL_PACKAGES #101

Kaljurand opened this issue Jan 9, 2023 · 0 comments · Fixed by #106

Comments

@Kaljurand
Copy link
Owner

The Google Play Support does not like the QUERY_ALL_PACKAGES permission and has blocked updates to the app in the Store. The need for this permission is described in:

<!-- TODO: try to avoid having to request this permission (and then enable QueryAllPackagesPermission)
Android v11. We query packages for several reasons:
1) finding speech recognizer providers (this query is declared below in the queries-section)
2) finding TTS service providers (this query is declared below in the queries-section)
3) listing apps (with icon and launch intent) that have previously launched Kõnele
4) launching intents (e.g. setting the alarm or opening maps) via rewrites
It is unclear if use-cases 3 and 4 could be instead declared via the queries-section.
-->
<uses-permission android:name="android.permission.QUERY_ALL_PACKAGES" />

Possible solutions:

  • ask Google Play Support (again) to reconsider
  • build a reduced APK for Google Play without this permission, and recommend users to download from other app stores
  • review the reasons why this permission is needed, and maybe drop some features if they are not essential (e.g. showing an icon next to a package name)
Kaljurand added a commit that referenced this issue Apr 9, 2023
Drop need for QUERY_ALL_PACKAGES without dropping any features

Fix #101
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant