pull down to refresh

Find the reason and solution for push subscription setting being lost 500k sats
1384 sats \ 3 comments \ @k00b 7 Oct 2023 meta
zaps forwarded to @ek (50%)
Our push subscription setting is flakey and we haven’t been able to figure out why.
Partial help that directly leads to the exact solution will yield a partial bounty. Full bounty payment requires finding the exact cause of the problem and the exact solution.
https://github.com/stackernews/stacker.news/issues/411
500,000 sats bounty
write
preview
k00b's bounties
440 sats \ 1 reply \ @ek fwd 7 Oct 2023
Very good idea to put up a bounty, it's hard to debug if you can't reproduce or have to wait multiple days to check if it's fixed. On my device, it's not lost so maybe related to specific Android version. I am using Android v9
reply
0 sats \ 0 replies \ @k00b OP 7 Oct 2023
I figured someone might be a pwa wizard with push notification experience and we're just missing something.
reply
0 sats \ 0 replies \ @Signal312 8 Oct 2023
Maybe these links could help...
https://medium.com/@madridserginho/how-to-handle-webpush-api-pushsubscriptionchange-event-in-modern-browsers-6e47840d756f
https://stackoverflow.com/questions/36602095/how-should-i-handle-the-pushsubscriptionchange-event
https://stackoverflow.com/questions/36602136/how-can-i-test-pushsubscriptionchange-event-handling-code
https://stackoverflow.com/questions/68504163/pwa-stop-receiving-push-notification-on-android-app-closed
reply