6
63
Fork
You've already forked android
5

[Bug or not] Unable to display any notifications in the background #71

Closed
opened 2025年11月01日 02:58:24 +01:00 by goddaneel · 18 comments

Environment

System: ColorOS 15 (Android 15)
Device: OnePlus Ace3 / 12R (PJE110)
Software: 1.2.1 (IzzyOnDroid)

Steps

  1. Install Sunup and keep it running in the background.
  2. Launch Element X / FluffyChat and register for Sunup push notifications.
  3. When Element X / FluffyChat is running in the foreground, new messages trigger normal notification pop-ups.
  4. Simply switching Element X / FluffyChat to the background without performing any background cleanup prevents any notifications from appearing.
  5. Bringing Element X / FluffyChat back to the foreground shows the message list updated and Sunup's message count increased, but no notifications appear for older messages.
  6. Same as Step 5, but similar to Step 3, new messages can trigger notifications.

Additional Notes

I'm unsure whether this is an issue with Sunup, Element X / FluffyChat, or the manufacturer's customized system. I just want to confirm if this behavior is expected.

# Environment System: ColorOS 15 (Android 15) Device: OnePlus Ace3 / 12R (PJE110) Software: 1.2.1 (IzzyOnDroid) # Steps 1. Install Sunup and keep it running in the background. 2. Launch Element X / FluffyChat and register for Sunup push notifications. 3. When Element X / FluffyChat is running in the foreground, new messages trigger normal notification pop-ups. 4. Simply switching Element X / FluffyChat to the background without performing any background cleanup prevents any notifications from appearing. 5. Bringing Element X / FluffyChat back to the foreground shows the message list updated and Sunup's message count increased, but no notifications appear for older messages. 6. Same as Step 5, but similar to Step 3, new messages can trigger notifications. # Additional Notes I'm unsure whether this is an issue with Sunup, Element X / FluffyChat, or the manufacturer's customized system. I just want to confirm if this behavior is expected.
Owner
Copy link

It may help you: https://unifiedpush.org/users/troubleshooting/setup/

=> You should try with UP-Example, it should work even if you swipe out UP-Example from the recent apps (so kills but not force-kills the app, I don't think oneplus tag as force-killed apps that are swiped out)
=> double check you have authorized both apps to run in the background without permission (may be necessary with some OEM and check https://dontkillmyapp.com/oneplus

It may help you: https://unifiedpush.org/users/troubleshooting/setup/ => You should try with UP-Example, it should work even if you swipe out UP-Example from the recent apps (so kills but not force-kills the app, I don't think oneplus tag as force-killed apps that are swiped out) => double check you have authorized both apps to run in the background without permission (may be necessary with some OEM and check https://dontkillmyapp.com/oneplus

After installing the latest version of Sunup (1.2.2, F-Droid), when using UP-Example without killing the background process, clicking "Test in background" successfully receives background notifications.
However, notifications from Element X and FluffyChat remain chaotic. Element X even fails to retrieve specific message details, displaying only the generic message "You have a new message."

After installing the latest version of Sunup (1.2.2, F-Droid), when using UP-Example without killing the background process, clicking "Test in background" successfully receives background notifications. However, notifications from Element X and FluffyChat remain chaotic. Element X even fails to retrieve specific message details, displaying only the generic message "You have a new message."
Owner
Copy link

There is a bug with Sunup on Element X, fix here : https://github.com/element-hq/element-x-android/pull/5741/files
And another one with FluffyChat, not directly related to UnifiedPush, but that impact UnifiedPush: UnifiedPush/flutter-connector#34 (comment)

And did you check dontkillmyapp ?

There is a bug with Sunup on Element X, fix here : https://github.com/element-hq/element-x-android/pull/5741/files And another one with FluffyChat, not directly related to UnifiedPush, but that impact UnifiedPush: https://codeberg.org/UnifiedPush/flutter-connector/issues/34#issuecomment-8292917 And did you check dontkillmyapp ?

Have the same odd behavior:
Fennec notifications work only in foreground with screen is on.
No problem with UP-Example apparently.

Latest GrapheneOS/Pixel 9a, Fennec, https://ntfy.sh/app.

Have the same odd behavior: Fennec notifications work only in foreground with screen is on. No problem with UP-Example apparently. Latest GrapheneOS/Pixel 9a, Fennec, https://ntfy.sh/app.
Owner
Copy link

@bam80 can you go to the matrix channel in this case ? You have likely an issue with your setup or your tests. Check if UP is correctly enabled on Fennec, do not do your tests in private mode, check if you have some ublock origin list blocking webpush.

PS: There is no such "work only in foreground" push notifications and UI notifications are 2 different things
PPS: I delete your comment about the same issue on the other repo, to avoid too much noise on the subject

@bam80 can you go to the matrix channel in this case ? You have likely an issue with your setup or your tests. Check if UP is correctly enabled on Fennec, do not do your tests in private mode, check if you have some ublock origin list blocking webpush. PS: There is no such "work only in foreground" push notifications and UI notifications are 2 different things PPS: I delete your comment about the same issue on the other repo, to avoid too much noise on the subject

@s1m I'm not Matrix user unfortunately, so it's better if we try to solve it here first, thanks.
It looks like a problem with ntfy web app specifically, as I also tried cleverpush.com/en/test-notifications/ and it works properly, increasing notifications count in Sunup (but I can't test remote pushes there).
That is why I asked you to retest in the other issue.

@s1m I'm not Matrix user unfortunately, so it's better if we try to solve it here first, thanks. It looks like a problem with ntfy web app specifically, as I also tried cleverpush.com/en/test-notifications/ and it works properly, increasing notifications count in Sunup (but I can't test remote pushes there). That is why I asked you to retest in the other issue.
Owner
Copy link

But your issue with Fennec is not related to this issue - which is likely fixed with the new version of Element X

And you didn't answer the other points - which may be the origin of your issue. And I can't help if you don't. BTW, ntfy app doesn't work if you use a non-default autopush server

But your issue with Fennec is not related to this issue - which is likely fixed with the new version of Element X And you didn't answer the other points - which may be the origin of your issue. And I can't help if you don't. BTW, ntfy app doesn't work if you use a non-default autopush server

As I got it working for other web app, I assume my Fennec setup is correct.
I didn't do anything unusual, just installed Fennec/Sunup on clean system and try. No ublock here.
There are Fennec entries in Sunup, but none of them are from ntfy app apparently. That's why I don't get pushes from there probably.

As I got it working for other web app, I assume my Fennec setup is correct. I didn't do anything unusual, just installed Fennec/Sunup on clean system and try. No ublock here. There are Fennec entries in Sunup, but none of them are from ntfy app apparently. That's why I don't get pushes from there probably.
Owner
Copy link

Did you enable "Background notifications" on ntfy webapp ?

Did you enable "Background notifications" on ntfy webapp ?

No I didn't, thank you.
That still didn't solve the problem - when I enabled the background notifications, now I get the app entry in Sunup.
But notifications work if I don't swipe off the browser only.
If I swipe ("soft" kill?) it, I don't have notifications any more.
If I reopen Sunup, I see the counter is increased if there were notifications sent remotely. That's the only evidence they were.

No I didn't, thank you. That still didn't solve the problem - when I enabled the background notifications, now I get the app entry in Sunup. But notifications work if I don't swipe off the browser only. If I swipe ("soft" kill?) it, I don't have notifications any more. If I reopen Sunup, I see the counter is increased if there were notifications sent remotely. That's the only evidence they were.

So I retested with other WebPush test Web app and got the same results:
https://simple-push-demo.vercel.app/
Notifications pop up until you don't swipe the browser out only.
After that, they only increase the counter in Sunup, silently. And even then you need to reopen Sunup to notice it.

@s1m could you try yourself and confirm such behavior please?
It looks like Fennec is the app to blame here. I think we need to file an issue if it's the case.

So I retested with other WebPush test Web app and got the same results: https://simple-push-demo.vercel.app/ Notifications pop up until you don't swipe the browser out only. After that, they only increase the counter in Sunup, silently. And even then you need to reopen Sunup to notice it. @s1m could you try yourself and confirm such behavior please? It looks like Fennec is the app to blame here. I think we need to file an issue if it's the case.
Owner
Copy link

I confirm it works when the app is killed

I confirm it works when the app is killed
Owner
Copy link

Can you get the browser logs ? Can you send a screen record maybe ? I've tested with ironfox

Can you get the browser logs ? Can you send a screen record maybe ? I've tested with ironfox

I'll try with Ironfox too and report back.
If you can give some clue how to get the browser logs beforehand, that could be useful, thanks.

I'll try with Ironfox too and report back. If you can give some clue how to get the browser logs beforehand, that could be useful, thanks.
Owner
Copy link

On GrapheneOS, you can go to the app info (after a long click on the app icon) > view logs

You can encrypt the logs with age if you want (public key: age15mrqwzp8qfj6ntqe52jx9tyyu8csrwt5k6cq4uc22dkz43t9ppzs8lkkvg)

On GrapheneOS, you can go to the app info (after a long click on the app icon) > view logs You can encrypt the logs with [_age_](https://age-encryption.org/) if you want (`public key: age15mrqwzp8qfj6ntqe52jx9tyyu8csrwt5k6cq4uc22dkz43t9ppzs8lkkvg`)

Tried Ironfox, there is definitely a difference there - while it has more restricted settings by default, when you set them to allow notifications - they work, event when the browser is killed.
Tried the same test https://simple-push-demo.vercel.app/ at the same time, Fennec just stop working as soon as it swiped out, but Ironfox continues to work.

@s1m could you try to reproduce on Fennec please?

Tried Ironfox, there is definitely a difference there - while it has more restricted settings by default, when you set them to allow notifications - they work, event when the browser is killed. Tried the same test https://simple-push-demo.vercel.app/ at the same time, Fennec just stop working as soon as it swiped out, but Ironfox continues to work. @s1m could you try to reproduce on Fennec please?

It looks like Fennec is the app to blame here. I think we need to file an issue if it's the case.

https://gitlab.com/relan/fennecbuild/-/issues/163

> It looks like Fennec is the app to blame here. I think we need to file an issue if it's the case. https://gitlab.com/relan/fennecbuild/-/issues/163
Owner
Copy link

OK, I've found the bug in Fennec. I'm closing this issue, as it works in the background as intended

OK, I've found the bug in Fennec. I'm closing this issue, as it works in the background as intended
Sign in to join this conversation.
No Branch/Tag specified
main
1.2.3
1.2.3-rc1
1.2.2
1.2.1
1.2.0
1.1.0
1.0.4
1.0.3
1.0.2
1.0.1
1.0.0
0.2.2
0.2.1
0.2.0
0.1.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
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
Sunup/android#71
Reference in a new issue
Sunup/android
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?