No notifications on GrapheneOS #91
Labels
No labels
bug
contribution welcome
duplicate
enhancement
later
not planned
out of scope
question
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
tom79/Holos-App#91
Loading…
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?
Description
I do not receive any notifications, neiter with holos in foregrounfd or background.
Steps to Reproduce
Expected Behavior
A notification should be received
Actual Behavior
Nothing. But when I open the app again, I notice it is doing updates of news and after that an in-app notification is generated. So it looks like the app doesn't run in background.
Ntfy is able to generate notifications from other source, so that works, and also in background.
I suspect Holos may need to issue a permanent notification, to be able to run in the background, just like ntfy does.
But I also wonder, since holos is the server itself, why does it need a distributor of notifications ? It is perfectly able to generate a local notification when it synchronize, without using ntfy, so why not the notifications for newsfeed ?
Screenshots / Logs
Environment
1.1.1
GrapheneOS Android 16, latest updates.
Ntft
Holos registered with ntfy
App battery usage set to unlimited
Fix was deployed on the relay
codeberg.org/tom79/Holos-Relay-Server@4e8069a9c9Push notifications to ntfy distributors were sent using web-push encryption (RFC 8030) which ntfy doesn't support. They are now sent as plain JSON.
After the changes yesterday, it is no longer possible to register for notifications, I get a timeout when I try.
And still no notifications received.
The fix was deployed less than an hour ago. Could you please try again now?
Also, could you share your exact Holos handle so I can check your push configuration on the relay?
Regarding the registration timeout, this is unrelated to the push fix. Can you describe exactly what happens: which screen, what error message?
I go to holos->settings->notifications->Distributor
Then click "Register", then a long wait and timeout message briefly in the bottom of the screen.
I just tried sending a private message from Mastodon, but no notification received.
A huge thank you for your attention. Where can I find the donor contribution link ?
Holos handle: dennis_melhede@holos.melhede.net
I tested push notifications with an ntfy account and they work correctly. Your issue is that your push endpoint became stale/disconnected. I've fixed a bug where re-registering could timeout, this will be in the next build. Once updated, go to UnifiedPush Setup and tap Register again.
When you asked me, I was actually able to perform a new registration without timeout, so I should already be in a situation where thw registration succeeded, but i still do not receive any notifications.
Aaaaand I just tested after a re-register, it now works.
Still on 1.1.1
Thank you, you made me realize that push notifications weren't working (maybe because my install comes from the very early betas?), but after re-registering they're working fine with the app closed and all, yay! (I use Conversations as a distributor.)
We have work to do in the notifications presentation, for the bubbles and for the whole Notifications tab, but push working feels great!