Skip to content

Google play store rejection because of in-app browser permission #479

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

Open
Jaybee4real opened this issue Apr 29, 2025 · 1 comment
Open

Comments

@Jaybee4real
Copy link

Our app was rejected during the Google Play review process because a foreground service permission is being declared in the merged Android manifest file but was not properly documented in our Play Store listing. After investigating, we've identified that this permission is being requested by this package. (See image below)

Image

QUESTION:
How is it being used? and how can it be demonstrated to the review team?

@ondra-marik-oksystem
Copy link

@Jaybee4real you are looking at the wrong line, FOREGROUND_SERVICE wasn't added from this package (as it doesn't have it in manifest). Culprit would show on next lines (1292+) on your screenshot.

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

No branches or pull requests

2 participants