[GH-ISSUE #684] REQUEST_INSTALL_PACKAGES permission #502

Closed
opened 2026-05-07 00:24:52 +02:00 by BreizhHardware · 7 comments

Originally created by @binwiederhier on GitHub (Mar 26, 2023).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/684

I received this question via email:

I was reading about your software ntfy, and I think it's great !
But I was shocked to know that it requires the "REQUEST_INSTALL_PACKAGES" permission. Why ?
I also noticed that the GooglePlay version doesn't need this permission, but the F-Droid version declares it.
Why the difference between the two versions?

Originally created by @binwiederhier on GitHub (Mar 26, 2023). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/684 I received this question via email: > I was reading about your software ntfy, and I think it's great ! But I was shocked to know that it requires the "REQUEST_INSTALL_PACKAGES" permission. Why ? > I also noticed that the GooglePlay version doesn't need this permission, but the F-Droid version declares it. Why the difference between the two versions?
BreizhHardware 2026-05-07 00:24:52 +02:00
Author
Owner

@binwiederhier commented on GitHub (Mar 26, 2023):

There is a bit more background on it here: https://github.com/binwiederhier/ntfy/issues/531

But the summary is: When you send an .apk file to ntfy as an attachment, Android will not allow you to install the .apk unless the application that downloaded the file has the REQUEST_INSTALL_PACKAGES permission. This applies to trying to install the .apk from ntfy itself, as well as when you try to install it from a file browser. It was wild.

This at least was the case on my device. But when discussing this in Discord it was not everyone's experience.

Honestly I am happy to remove the permission. I don't think many people will miss it.

<!-- gh-comment-id:1484221439 --> @binwiederhier commented on GitHub (Mar 26, 2023): There is a bit more background on it here: https://github.com/binwiederhier/ntfy/issues/531 But the summary is: When you send an .apk file to ntfy as an attachment, Android will not allow you to install the .apk unless the application that downloaded the file has the REQUEST_INSTALL_PACKAGES permission. This applies to trying to install the .apk from ntfy itself, as well as when you try to install it from a file browser. It was wild. This at least was the case on my device. But when discussing this in Discord it was not everyone's experience. Honestly I am happy to remove the permission. I don't think many people will miss it.
Author
Owner

@Quantum-Future commented on GitHub (Mar 30, 2023):

I agree with Google's view explained in #531: "Permission use is not directly related to your app's core purpose".
Why sending an .APK as a ntfy attachment? To make updates?
I don't feel comfortable knowing that an .APK could be installed automatically from within ntfy.
I prefer having this permission removed.
Thank you.

<!-- gh-comment-id:1490897633 --> @Quantum-Future commented on GitHub (Mar 30, 2023): I agree with Google's view explained in #531: "Permission use is not directly related to your app's core purpose". Why sending an .APK as a ntfy attachment? To make updates? I don't feel comfortable knowing that an .APK could be installed automatically from within ntfy. I prefer having this permission removed. Thank you.
Author
Owner

@Quantum-Future commented on GitHub (May 31, 2024):

Hello, the current version (1.16.0) was released on Dec 11, 2022.
Do you have plans for releasing an updated version without this permission and some bugfixes or new features?

<!-- gh-comment-id:2141299999 --> @Quantum-Future commented on GitHub (May 31, 2024): Hello, the current version (1.16.0) was released on Dec 11, 2022. Do you have plans for releasing an updated version without this permission and some bugfixes or new features?
Author
Owner

@Quantum-Future commented on GitHub (Sep 19, 2025):

Honestly I am happy to remove the permission. I don't think many people will miss it.

Hello Phil, please remember this for the next Android release.
Thank you !

<!-- gh-comment-id:3312676902 --> @Quantum-Future commented on GitHub (Sep 19, 2025): > Honestly I am happy to remove the permission. I don't think many people will miss it. Hello Phil, please remember this for the next Android release. Thank you !
Author
Owner

@binwiederhier commented on GitHub (Sep 19, 2025):

Done github.com/binwiederhier/ntfy-android@876d01da00

<!-- gh-comment-id:3313425379 --> @binwiederhier commented on GitHub (Sep 19, 2025): Done https://github.com/binwiederhier/ntfy-android/commit/876d01da00fce68e889eaa6e10270eeef0b0b1da
Author
Owner

@Quantum-Future commented on GitHub (Oct 25, 2025):

Hi, the latest version added to F-Droid on Sept 23 (v1.17.8), still has this permission.

<!-- gh-comment-id:3446087475 --> @Quantum-Future commented on GitHub (Oct 25, 2025): Hi, the latest version added to F-Droid on Sept 23 (v1.17.8), still has this permission.
Author
Owner

@Quantum-Future commented on GitHub (Oct 25, 2025):

Ver 1.17.13 was published today on F-Droid and still declares this permission.

<!-- gh-comment-id:3447874482 --> @Quantum-Future commented on GitHub (Oct 25, 2025): Ver 1.17.13 was published today on F-Droid and still declares this permission.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#502
No description provided.