For ease of reading here’s the notification in text format: “UnifiedPush: The push service application is no longer available. It may have been uninstalled. Please re-enable UnifiedPush to select a new service.”
I haven’t changed any settings or installed anything related recently. I only updated from /e/OS official 3.4 to 3.6 (it may have started with the update, but not sure). My device is a Fairphone 5 (FP5). My notification settings both overall and for Fennec are normal / default, I’d say.
Does anyone know what the meaning of this is? Is it a UnifiedPush / /e/OS’ notification function problem or is it a Fennec problem? Or anyone else having this problem?
hows fennec set up, does it use eOS integrated services or else?
You may try clearing the cache and/or data of system appfoundation.e.ntfyand/or you may try config fennec to use another Unified Push server to rule out integrated UP. The latter is easiest done by installing io.heckel.ntfy from FDroid and use the default service therein, note that then probably two ntfy will show up during config in fennec: choose the second in the list, which usually is the extra install.
In my experience the integrated foundation.e.ntfy or push.murena.com (who can tell?) sometimes seems to behave a bit shady or unforeseeable when it comes to non-eOS-notifications from other apps installed that use UP…
edit: fennec obviously does not allow choice among available push service applications, see my post below
I am affected by the same issue (/e/OS 3.6 on a Oneplus 6). I couldn’t find how to change the UnifiedPush settings for Fennec so I just rolled back from version 149 to version 148.0.2 in F-Droid. When Fennec then showed up in F-Droid’s updates pane, I simply checked “Ignore this update” from the dots menu on the top right as a quick workaround.
Thanks @jobal
Sorry, I did find the settings you are referring to, I meant the settings regarding the UnifiedPush server to be used, as mentioned by @obacht
Sorry, my post was misleading, I must admit I did not know fennec in detail but expected it to allow choice of push server application like other apps do in case there´s options. So I just installed fennec to check my presumptions. Turns out there´s no way to choose the push server or any respective application in fennec settings like I expected, thus no way (for me) to tell what fennec tries to do in case there´s push server options or how it is structured with regards to UP in general.
But I can confirm that in my test case fennec does neither register in integrated foundation.e.ntfy nor in extra installed io.heckel.ntfy and that I get the same error message stating there would be no push service application, which I consider a false statement as my device provides 2 of them…
I can confirm the first part but rather unsure about the coincidence with 3.6 as in my observation with org.unifiedpush.example in previous versions not long ago (can´t remember the exact last version) it recognized foundation.e.ntfy in terms of giving a choice when io.heckel.ntfy was installed in parallel (just like Molly still does (!) for instance) - but at some point it did not anymore and that was right after an update of UP-Example. I remember switching versions back and forth to doublecheck and I can say for sure that at this point in time the oddness was on the UP-Example side of things:UP-Example seemingly ignores foundation.e.ntfy but automatically works via io.heckel.ntfy (if present).
(right now I am not willing to kill my working Molly-using-UP-setup by deleting io.heckel.ntfy just to check foundation.e.ntfy)
It´s a pity we have no further information on how foundation.e.ntfy and/or push.murena.com are set up/config´d, we are waiting for a documentation and status-indication for months now after the integrated ntfy was made invisible in device settings in some late 2025 eOS-version.
But for troubleshooting fennec (and testing with UP-Example) it may be worth giving Sunup (a UnifiedPush distributor using Mozilla’s push server) a go (instead of io.heckel.ntfy).
I tried it when I struggled to get Molly-UP into some stable config but did not use it then because it did not allow me to change its default push server for good). From what I recall at that time it worked well - least with UP-Example…
Maybe fennec is happier with a Mozilla-server?
Issues with UP seem hard to troubleshoot as so many different and independent unknowns are involved…
Thank you for your tests. I have downgraded UP-Example to version 2.2, and indeed this version works with foundation.e.ntfy.
Hence, the registration problems of Fennec and UP-Example seem to be on their side, not on the ntfy apps we have tried.
… that made me curious and I downgraded too to learn something new: in developer settings of UP-Example one can change ditributor in case more than one such app is present on the device. Only version 2.2 offers to choose foundation.e.ntfy, version 2.3 does not. (my original observation was in versions further back when this choice was not hidden in Dev-settings of the app but popped up first thing when “register” button was touched)
I know I’ve been awfully quiet. But I think the thread has been more than insightful in the meantime. Thanks to everyone who contributed! I just want to add that I’ve, as a quick fix, disabled UnifiedPush in Settings > Apps > Fennec > Notifications (can also be seen in the post I replied to), while all other notification categories stayed enabled. So far the notification from the first post hasn’t reappeared.
