[GH-ISSUE #1445] Android client crashes on GrapheneOS #1017

Closed
opened 2026-05-07 00:29:36 +02:00 by BreizhHardware · 4 comments

Originally created by @keynlotepan on GitHub (Sep 23, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1445

🐞 Describe the bug

After update to 1.17.0 via F-Droid ntfy crashes permanently

💻 Components impacted

ntfy 1.17.0 used (only) for Molly (v7.53.5-1-FOSS) notifications on GrapheneOS (Android 16, Build 2025091900)

💡 Screenshots and/or logs

Logs cannot be obtained because of crash on start

🔮 Additional context

Originally created by @keynlotepan on GitHub (Sep 23, 2025). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1445 :lady_beetle: **Describe the bug** <!-- A clear and concise description of the problem. --> After update to 1.17.0 via F-Droid ntfy crashes permanently :computer: **Components impacted** <!-- ntfy server, Android app, iOS app, web app --> ntfy 1.17.0 used (only) for Molly (v7.53.5-1-FOSS) notifications on GrapheneOS (Android 16, Build 2025091900) :bulb: **Screenshots and/or logs** <!-- If applicable, add screenshots or share logs help explain your problem. To get logs from the ... - ntfy server: Enable "log-level: trace" in your server.yml file - Android app: Go to "Settings" -> "Record logs", then eventually "Copy/upload logs" - web app: Press "F12" and find the "Console" window --> Logs cannot be obtained because of crash on start :crystal_ball: **Additional context** <!-- Add any other context about the problem here. -->
BreizhHardware 2026-05-07 00:29:36 +02:00
  • closed this issue
  • added the
    🪲 bug
    label
Author
Owner

@inDane commented on GitHub (Sep 23, 2025):

Yup, same for me... F-Droid auto-updated it... sucks.

See here:
https://github.com/binwiederhier/ntfy?tab=readme-ov-file#%EF%B8%8F-f-droid-do-not-upgrade-to-ntfy-1170
@binwiederhier wrote a warning in the README.

Unfortunately for me, I do not use google play...
Edit: I had to uninstall the F-Droid installed ntfy. Install the 1.17.8 .apk and re-configure the app.

<!-- gh-comment-id:3323293150 --> @inDane commented on GitHub (Sep 23, 2025): Yup, same for me... F-Droid auto-updated it... sucks. See here: https://github.com/binwiederhier/ntfy?tab=readme-ov-file#%EF%B8%8F-f-droid-do-not-upgrade-to-ntfy-1170 @binwiederhier wrote a warning in the README. Unfortunately for me, I do not use google play... Edit: I had to uninstall the F-Droid installed ntfy. Install the [1.17.8 .apk](https://github.com/binwiederhier/ntfy-android/releases/tag/v1.17.8) and re-configure the app.
Author
Owner

@keynlotepan commented on GitHub (Sep 23, 2025):

Thank you for your advice to install v1.17.8 from the link you provided. I followed it and installed ntfy-1.17.8-fdroid-debug.apk from there. As a result, I was able to start ntfy app again, but the configured topic was lost. I did not have time to re-configure but planned it for this evening. Meanwhile F-Droid automatically updated from this ntfy-1.17.8-fdroid-debug.apk to 1.17.8 (versionCode 41) and the configuration is back now. Unexpectedly but it works again without any repeated configuration.
I'm going to close the issue because it works for me now.

<!-- gh-comment-id:3324545011 --> @keynlotepan commented on GitHub (Sep 23, 2025): Thank you for your advice to install v1.17.8 from the link you provided. I followed it and installed ntfy-1.17.8-fdroid-debug.apk from there. As a result, I was able to start ntfy app again, but the configured topic was lost. I did not have time to re-configure but planned it for this evening. Meanwhile F-Droid automatically updated from this ntfy-1.17.8-fdroid-debug.apk to 1.17.8 (versionCode 41) and the configuration is back now. Unexpectedly but it works again without any repeated configuration. I'm going to close the issue because it works for me now.
Author
Owner

@keynlotepan commented on GitHub (Sep 23, 2025):

I can see now the reason for the apparently lost configuration in the debug version: It was installed parallel and did not replace the defective one, so it had it's own (empty) configuration.
Thanks for the fix.

<!-- gh-comment-id:3324569751 --> @keynlotepan commented on GitHub (Sep 23, 2025): I can see now the reason for the apparently lost configuration in the debug version: It was installed parallel and did not replace the defective one, so it had it's own (empty) configuration. Thanks for the fix.
Author
Owner

@matm commented on GitHub (Sep 24, 2025):

FYI the F-Droid version 1.17.8 worked for me after cleaning cache and data. Same crashes issues otherwise.

<!-- gh-comment-id:3327105681 --> @matm commented on GitHub (Sep 24, 2025): FYI the F-Droid version 1.17.8 worked for me after cleaning cache and data. Same crashes issues otherwise.
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#1017
No description provided.