Web push notifications stopped working
-
wetsmurfette last edited by leocg
web push notification stopped to work long time ago.
Always get this error."Unable to register push subscription AbortError: Registration failed - push service error"
I don't know why they don't care...but at this point if you don't fix it just ditch the service instead of offering notification that won't work cause you do nothing about it
-
-
-
wetsmurfette last edited by
Why answering if you have no idea what's the matter?
If web push notifications isn't clear enough..no idea how to explain.
I was used to get notification from Opera from youtube or keepa, they are not working anymore by months now..
But never mind...if here you don't even know what they are... amen.. -
burnout426 Volunteer last edited by
Now that you mention Youtube, Opera has a bug report investigating Youtube notifications not working for some users at least. It's RNA-1653. The cause hasn't been figured out yet though.
-
wetsmurfette last edited by
@burnout426 Wow. So they know but they have no clue how to solve it? sounds reassuring..
And isn't about just youtube..it happens in every site that offers notification in the browser
-
marteenas last edited by
I noticed this quite some time ago (2-3 months ago) when working on web push integration for my web app. All browsers work fine with subscribing for web-push notifications, Opera fails with some error. I feel like the service (or server) that is responsible for subscribing and sending the notification to users phone is just gone. Does not work on Opera Android either (would make sense if the web push responsible server is just gone). Did Opera cut this service off?
-
Mlipka Opera last edited byThis issue is certainly something we will look into. We plan to investigate it internally and may reach out with further questions.
To @wetsmurfette: We understand your frustration regarding this matter. However, it's important to maintain a respectful tone in our interactions. When @leocg asked clarifying questions, the response was quite harsh. Constructive communication is key to resolving issues effectively.
-
burnout426 Volunteer last edited by
Close Settings in Windows if it's open.
In Opera, goto https://example.com and hit ctrl + shift + j to open the console in the developer tools.
Type:
Notification.requestPermission().then(permission => { alert("Permission: " + permission); });and press enter.
When asked to allow notifications for example.com, choose "yes". You should then see an alert dialog saying the permission was granted.
Then, in Windows, goto "Settings -> System -> Notifications", make sure notifications are enabled, "Do not disturb" is disabled and there's no focus session enabled. Then, see if Opera is in the notification app list (it should be now if it wasn't). If it is, click "Opera" in the list and make sure its notification settings are correct.
Then, restart Opera.
Then, go back to https://example.com/, open the console again, type:
new Notification("Test notification from example.com");and press enter to test that notifications work for the site.
Does all that work at least?
It does for me, but I'm on 23H2.
-
wetsmurfette last edited by
@burnout426 i tried and i get the notification...but that is not the point..
if you go here it's simplerhttps://girliemac.com/html5-notifications-webOS-style/
and i get notification. Still when i want to register to web push notification on Keepa.com, for example, I get the error message i posted.
If you force notification of course it pops out, but opera fails to register to the subscription to the service.
-
burnout426 Volunteer last edited by
@wetsmurfette I can confirm the keepa.com issue. Had to go all the way back to Opera 117 (117.0.5408.197 was the specific build I tried) for it to work. By "work", I mean I was able to enable the web push notification setting on the Keepa settings page and click its test link to get a notification.
For Opera 118 and newer, I couldn't get things to work. Spoofing as Chrome or Firefox didn't help and the --disable-extensions command-line switch (to kill Opera's built-in extensions) didn't help. I also didn't see any flags at the URL
opera://flagsthat would make a difference. It's just broken. With that said though, I can't tell if the Keepa issue specifically is actually a bug with the Web Notification API support in opera or if it's a bugs with the handling of some other Javascript code on the Keepa site. Either way, since it works in 117 - 102 for example, I'll file a bug specifically for the Keepa issue to see if someone can figure out the cause and hopefully, that might fix other notification issues.On a side note, in testing some builds from 102 - 114, I noticed that sometimes notifications would stop working for Keepa in Opera. To make them work for Opera again, I had to delete the keepa.com string under the root/gcm/push_messaging_application_id_map node in the "Preferences" file in the profile folder. Or, I could goto
opera://settings/resetand reset just settings. -
-
wetsmurfette last edited by
@burnout426 Thank you so much for diving in it and look for possible causes and solutions.
Point is something like getting a notification on a browser should be something easy and reliable, or it doesn't make sense.
If it was just about keepa.com i could just forget it, cause i can get notification other way, but they are not working anywhere. So my thought is..fix it or ditch it. Opera offers the option to have them but they never worked that well ever. Even before they were not reliable.
If any app out there nowadays can get push notifications guess isn't such difficult task to achive.
I really get frustrated when i can't make something that should work but doesn't.
Again, if can't be solved just ditch notification..it's a no sense giving that option if then you keep adding this and that and never fix what isn't working.Again, thanks to you and anyone looking into it. Really appreciate.
And sorry if i used a disrespectful tone, as have been pointed out.
