[GH-ISSUE #1176] web view works, but android app doesn't #830

New issue

Closed

opened 2026-05-07 00:27:50 +02:00 by BreizhHardware · 3 comments

BreizhHardware commented

2026-05-07 00:27:50 +02:00

Owner

Originally created by @umk0m1qk on GitHub (Sep 2, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1176

Describe the bug
web view works, but android app doesn't
Components impacted
android app
Screenshots and/or logs
See log attached
This is a log of the ntfy.txt

Additional context
Steps to reproduce:

Install ntfy android app on GrapheneOS build 2024082200 running on Pixel 8a confirming full network, notifications, and sensors permissions without restriction. Confirm background usage is allowed (should be by default on install).
Add topics from Unified Push apps (e.g., Amethyst, 0xChat)
Check if those topics are working from a terminal: $ curl -d "It's not working" ntfy.sh/**********
Receive terminal confirmation
No push notification arrives on phone
Open ntfy.sh/********** in web browser, and you will see the test notification "It's not working"

Originally created by @umk0m1qk on GitHub (Sep 2, 2024). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1176 **Describe the bug** web view works, but android app doesn't **Components impacted** android app **Screenshots and/or logs** See log attached [This is a log of the ntfy.txt](https://github.com/user-attachments/files/16831494/This.is.a.log.of.the.ntfy.txt) **Additional context** Steps to reproduce: - Install ntfy android app on GrapheneOS build 2024082200 running on Pixel 8a confirming full network, notifications, and sensors permissions without restriction. Confirm background usage is allowed (should be by default on install). - Add topics from Unified Push apps (e.g., Amethyst, 0xChat) - Check if those topics are working from a terminal: $ curl -d "It's not working" ntfy.sh/********** - Receive terminal confirmation - No push notification arrives on phone - Open ntfy.sh/********** in web browser, and you will see the test notification "It's not working"

BreizhHardware

2026-05-07 00:27:51 +02:00

closed this issue
added the
🪲 bug
label

BreizhHardware commented

2026-05-07 00:27:51 +02:00

Author

Owner

@wunter8 commented on GitHub (Sep 2, 2024):

That's not how UnifiedPush works. ntfy forwards the messages received on the UnifiedPush topic to the app that registered the topic behind the scenes. You won't see anything in the ntfy app for UP messages. If the messages sent to the UP topics are not in the correct format, the UP app that registered the topic will not display a notification either. The only way to test a UP topic is to trigger a notification in that app (e.g., send/receive a message in 0xChat that should trigger a notification)

@wunter8 commented on GitHub (Sep 2, 2024): That's not how UnifiedPush works. ntfy forwards the messages received on the UnifiedPush topic to the app that registered the topic behind the scenes. You won't see anything in the ntfy app for UP messages. If the messages sent to the UP topics are not in the correct format, the UP app that registered the topic will not display a notification either. The only way to test a UP topic is to trigger a notification in that app (e.g., send/receive a message in 0xChat that should trigger a notification)

BreizhHardware commented

2026-05-07 00:27:51 +02:00

Author

Owner

@umk0m1qk commented on GitHub (Sep 2, 2024):

Thanks for the response. I'm a bit confused, though, because the topic link we are sending test messages to using $ curl -d is the UP topic link generated from within Amethyst by selecting "ntfy" as the push notification option. If I'm understanding you correctly, we shouldn't be able to send anything to this link except UP from the originating app (Amethyst), and yet, we can from terminal and the messages show in the ntfy web app.

The reason we're exploring this is because UP from Amethyst (and 0xchat) paired with ntfy is not working at all - zero push notifications are arriving on the above described device.

@umk0m1qk commented on GitHub (Sep 2, 2024): Thanks for the response. I'm a bit confused, though, because the topic link we are sending test messages to using $ curl -d is the UP topic link generated from within Amethyst by selecting "ntfy" as the push notification option. If I'm understanding you correctly, we shouldn't be able to send anything to this link except UP from the originating app (Amethyst), and yet, we can from terminal and the messages show in the ntfy web app. The reason we're exploring this is because UP from Amethyst (and 0xchat) paired with ntfy is not working at all - zero push notifications are arriving on the above described device.

BreizhHardware commented

2026-05-07 00:27:51 +02:00

Author

Owner

@wunter8 commented on GitHub (Sep 2, 2024):

You can send stuff to the topic using curl, but it won't create a visible notification on your phone because it's not in the format Amethyst is expecting.

Yes, you can see the notifications in the web browser if you manually subscribe to the randomly generated topic url. You'd be able to see both Amethyst's notifications (in their proper format) and your manual notifications.

If neither UP app is working, it seems something is misconfigured. Do you have auth set up on your server? If so, did you create the anonymous write up* auth rule?

If that's not the issue, it could be that your base-url isn't configured properly.

(If you can, Discord is often better for troubleshooting problems like this)

@wunter8 commented on GitHub (Sep 2, 2024): You can send stuff to the topic using curl, but it won't create a visible notification on your phone because it's not in the format Amethyst is expecting. Yes, you can see the notifications in the web browser if you manually subscribe to the randomly generated topic url. You'd be able to see both Amethyst's notifications (in their proper format) and your manual notifications. If neither UP app is working, it seems something is misconfigured. Do you have auth set up on your server? If so, did you create the anonymous write up* auth rule? If that's not the issue, it could be that your `base-url` isn't configured properly. (If you can, Discord is often better for troubleshooting problems like this)