#149933: "push notifications stop working, subscriptions duplicated, multiple browsers"
Quel est le sujet de ce rapport ?
Que s'est-il passé ? Merci de choisir ci-dessous
Que s'est-il passé ? Merci de choisir ci-dessous
Veuillez vérifier s'il existe déjà un rapport sur le même sujet
Si oui, veuillez VOTER pour ce rapport. Les rapports ayant le plus de votes auront la PRIORITÉ !
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Description détaillée
-
• Merci de copier-coller le message d'erreur qui s'affiche à l'écran, s'il y a lieu.
n/a
-
• Veuillez expliquer ce que vous vouliez faire, ce que vous avez fait et ce qu'il s'est passé
I have the same behaviour in Safari on iPhone 8 and in Opera (Chrome) on Windows 11.
I have "push notifications" configured, as I play "turn based" mode and want to know when it is my turn.
(In Safari, this requires pinning the website to the home page as a web app)
The push notifications work fine for a while, but then after about 1-2 days on Safari (a bit longer in Opera/Chrome), I stop receiving notifications.
If I visit the "push notifications" section of my profile, then push notifications will start working again, but there is a new "subscription" row created for the same browser.
The old "subscription" row becomes non functional but will remain there forever. I now have about 40 such rows in my profile, with no way to clear up old broken rows.
There are lots of reports of this on the web from other users.
Please could you:
1: Fix whatever is causing the push subscription to fail after a few days
2: Add some method to remove old unattached "subscription" rows from the profile page. The page UI currently says "You can manage your subscriptions by cancelling authorizations directly in your browser", but I don't think that's actually possible in this case, is it?
I had a look on Google for "safari push notifications stop working" to see if there was any known issues in this area and found:
[1] dev.to/progressier/how-to-fix-ios-push-subscriptions-being-terminated-after-3-notifications-39a7
[2] stackoverflow.com/questions/77912561/web-push-notifications-stop-working-on-safari
Thanks! • Quel est votre navigateur ?
Safari
-
• SVP copiez / collez ici le texte affiché en anglais au lieu de votre langue. Si vous disposez d'une capture d'écran du bug (bonne pratique), vous pouvez utiliser le service d'hébergement de votre choix (snipboard.io par exemple) pour la télécharger et en copier/coller le lien ici. Ce texte est-il disponible dans le système de traduction ? Si oui, a-t-il été traduit depuis plus de 24 heures ?
n/a
• Quel est votre navigateur ?
Safari
-
• Merci d'expliquer votre suggestion de manière précise et concise, de façon à ce qu'il soit aussi simple que possible de comprendre ce que vous voulez dire.
n/a
• Quel est votre navigateur ?
Safari
-
• Qu'affichait l'écran lorsque vous avez été bloqué(e) (Un écran vierge ? Une partie de l'interface du jeu ? Un message d'erreur ?)
n/a
• Quel est votre navigateur ?
Safari
-
• Quelle partie des règles n'a pas été respectée par l'adaptation BGA ?
n/a
-
• La violation de règle est-elle visible dans le replay de la partie ? Si oui, à quel numéro de coup ?
I have the same behaviour in Safari on iPhone 8 and in Opera (Chrome) on Windows 11.
I have "push notifications" configured, as I play "turn based" mode and want to know when it is my turn.
(In Safari, this requires pinning the website to the home page as a web app)
The push notifications work fine for a while, but then after about 1-2 days on Safari (a bit longer in Opera/Chrome), I stop receiving notifications.
If I visit the "push notifications" section of my profile, then push notifications will start working again, but there is a new "subscription" row created for the same browser.
The old "subscription" row becomes non functional but will remain there forever. I now have about 40 such rows in my profile, with no way to clear up old broken rows.
There are lots of reports of this on the web from other users.
Please could you:
1: Fix whatever is causing the push subscription to fail after a few days
2: Add some method to remove old unattached "subscription" rows from the profile page. The page UI currently says "You can manage your subscriptions by cancelling authorizations directly in your browser", but I don't think that's actually possible in this case, is it?
I had a look on Google for "safari push notifications stop working" to see if there was any known issues in this area and found:
[1] dev.to/progressier/how-to-fix-ios-push-subscriptions-being-terminated-after-3-notifications-39a7
[2] stackoverflow.com/questions/77912561/web-push-notifications-stop-working-on-safari
Thanks! • Quel est votre navigateur ?
Safari
-
• Quelle action de jeu vouliez-vous faire ?
n/a
-
• Qu'avez-vous essayé de faire pour déclencher cette action de jeu ?
I have the same behaviour in Safari on iPhone 8 and in Opera (Chrome) on Windows 11.
I have "push notifications" configured, as I play "turn based" mode and want to know when it is my turn.
(In Safari, this requires pinning the website to the home page as a web app)
The push notifications work fine for a while, but then after about 1-2 days on Safari (a bit longer in Opera/Chrome), I stop receiving notifications.
If I visit the "push notifications" section of my profile, then push notifications will start working again, but there is a new "subscription" row created for the same browser.
The old "subscription" row becomes non functional but will remain there forever. I now have about 40 such rows in my profile, with no way to clear up old broken rows.
There are lots of reports of this on the web from other users.
Please could you:
1: Fix whatever is causing the push subscription to fail after a few days
2: Add some method to remove old unattached "subscription" rows from the profile page. The page UI currently says "You can manage your subscriptions by cancelling authorizations directly in your browser", but I don't think that's actually possible in this case, is it?
I had a look on Google for "safari push notifications stop working" to see if there was any known issues in this area and found:
[1] dev.to/progressier/how-to-fix-ios-push-subscriptions-being-terminated-after-3-notifications-39a7
[2] stackoverflow.com/questions/77912561/web-push-notifications-stop-working-on-safari
Thanks! -
• Que s'est-il passé lorsque vous avez essayé de faire cela (message d'erreur, message dans la barre d'état du jeu...) ?
• Quel est votre navigateur ?
Safari
-
• À quelle étape de la partie le problème est-il apparu ? Quelles instructions le jeu affichait-il ?
n/a
-
• Que s'est-il passé lorsque vous avez essayé de faire cette action de jeu (message d'erreur, message dans la barre d'état du jeu...) ?
I have the same behaviour in Safari on iPhone 8 and in Opera (Chrome) on Windows 11.
I have "push notifications" configured, as I play "turn based" mode and want to know when it is my turn.
(In Safari, this requires pinning the website to the home page as a web app)
The push notifications work fine for a while, but then after about 1-2 days on Safari (a bit longer in Opera/Chrome), I stop receiving notifications.
If I visit the "push notifications" section of my profile, then push notifications will start working again, but there is a new "subscription" row created for the same browser.
The old "subscription" row becomes non functional but will remain there forever. I now have about 40 such rows in my profile, with no way to clear up old broken rows.
There are lots of reports of this on the web from other users.
Please could you:
1: Fix whatever is causing the push subscription to fail after a few days
2: Add some method to remove old unattached "subscription" rows from the profile page. The page UI currently says "You can manage your subscriptions by cancelling authorizations directly in your browser", but I don't think that's actually possible in this case, is it?
I had a look on Google for "safari push notifications stop working" to see if there was any known issues in this area and found:
[1] dev.to/progressier/how-to-fix-ios-push-subscriptions-being-terminated-after-3-notifications-39a7
[2] stackoverflow.com/questions/77912561/web-push-notifications-stop-working-on-safari
Thanks! • Quel est votre navigateur ?
Safari
-
• Veuillez décrire le problème d'affichage. Si vous disposez d'une capture d'écran du bug (bonne pratique), vous pouvez utiliser le service d'hébergement de votre choix (snipboard.io par exemple) pour la télécharger et en copier/coller le lien ici.
n/a
• Quel est votre navigateur ?
Safari
-
• SVP copiez / collez ici le texte affiché en anglais au lieu de votre langue. Si vous disposez d'une capture d'écran du bug (bonne pratique), vous pouvez utiliser le service d'hébergement de votre choix (snipboard.io par exemple) pour la télécharger et en copier/coller le lien ici. Ce texte est-il disponible dans le système de traduction ? Si oui, a-t-il été traduit depuis plus de 24 heures ?
n/a
• Quel est votre navigateur ?
Safari
-
• Merci d'expliquer votre suggestion de manière précise et concise, de façon à ce qu'il soit aussi simple que possible de comprendre ce que vous voulez dire.
n/a
• Quel est votre navigateur ?
Safari
Historique du rapport de bug
Unexpected error: BGA service error
(reference: VO 06/03 02:07:10)
So there was something about older Safari which didn't work well with this.
I do still have about 50 orphaned push subscriptions linked to my account with no way of removing them.
Please could you add a button to delete a push subscription? The UI says to do it in my browser but I can't see any way to do that.
Very annoying :(
I get the same. My iPad seems to keep getting notifications (the first Safari 17.4 in the screenshot) but with my iPhone it starts and stops intermittently. On the screenshot I have added the DuckDuckGo (on iPhone) and the others lines have appeared by themselves.
Suggestion: drop the subscription of any device that hasn’t visited the site in, say, 30 days. Or 90. Or something.
Ajouter à ce rapport
- Un autre n° de table / n° de coup
- Appuyer sur F5 a-t-il résolu le problème ?
- Le problème est-il apparu plusieurs fois ? À chaque fois ? Aléatoirement ?
- Si vous disposez d'une capture d'écran du bug (bonne pratique), vous pouvez utiliser le service d'hébergement de votre choix (snipboard.io par exemple) pour la télécharger et en copier/coller le lien ici.
