mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 16:35:53 +02:00
[GH-ISSUE #531] ⛔ Google rejects ntfy from Google Play ⚠️ #408
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#408
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @binwiederhier on GitHub (Dec 5, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/531
Google has rejected the ntfy app update for using the REQUEST_INSTALL_PACKAGES permission.
This permission is used in the current production version (v1.14.0, aka "28") to install .apk files that were received by ntfy
In newer builds of ntfy (v1.15.2, aka "31", and others), I have removed the REQUEST_INSTALL_PACKAGES permission, yet Google keeps rejecting the app. I have appealed, but nothing has helped so far.
Unable to publish new versions ⛔ ⚠️
As of right now, I cannot publish new versions of ntfy on Google Play.
Communication from/with Google
Note: Version "28" is the current Production version. Newer versions do not have this permission. This is an error on Google-side, yet, I cannot do anything about it.
Google Play console screenshots
Update 1
After "Creating a release" (version v1.16.0, aka "32") directly in the "Production" track (and setting the "roll out percentage" to 100%), the "App bundles and APKs using sensitive permissions" page is now empty. There is hope.
Update 2
It's fixed!! I believe what worked was to deploy directly to the Production track with 100% rollout. It was truly YOLO, but I had no other choice. That made the the "App bundles and APKs using sensitive permissions" page show no releases in violation, which I think was ultimately the fix.
@binwiederhier commented on GitHub (Dec 11, 2022):
Fixed.