BGA app no longer pushing notifications to tablet notification area

[Meeplelowda]

I have a potentially related problem. I get notifications, but sometimes they arrive 15 minutes after the game has begun, or worse, after the game has ended (if I don't notice through another means that the game began)! Because I eventually receive them, obviously my permissions allow notifications.

[Een]

I have a potentially related problem. I get notifications, but sometimes they arrive 15 minutes after the game has begun, or worse, after the game has ended (if I don't notice through another means that the game began)! Because I eventually receive them, obviously my permissions allow notifications.

Web push notifications are dispatched through the browser vendors' infrastructure. Delays could come from:
- delays dispatching the queue for notifications on BGA side (that could potentially happen at peak time if there are too many notifications; is there a specific time of the day where you experience this?)
- delays in the browser vendor's infrastructure; we don't have control over this.
- battery level of your device (yes, that's a thing): we use the default urgency ('normal') for notifications and the notifications protocol specifies "Urgency indicates to the push service how important a message is to the user. This can be used by the push service to help conserve the battery life of a user's device by only waking up for important messages when battery is low."

[Meeplelowda]

I have a potentially related problem. I get notifications, but sometimes they arrive 15 minutes after the game has begun, or worse, after the game has ended (if I don't notice through another means that the game began)! Because I eventually receive them, obviously my permissions allow notifications.

Web push notifications are dispatched through the browser vendors' infrastructure. Delays could come from:
- delays dispatching the queue for notifications on BGA side (that could potentially happen at peak time if there are too many notifications; is there a specific time of the day where you experience this?)
- delays in the browser vendor's infrastructure; we don't have control over this.
- battery level of your device (yes, that's a thing): we use the default urgency ('normal') for notifications and the notifications protocol specifies "Urgency indicates to the push service how important a message is to the user. This can be used by the push service to help conserve the battery life of a user's device by only waking up for important messages when battery is low."

I will start tracking the delay and time of day.

[Meeplelowda]

Web push notifications are dispatched through the browser vendors' infrastructure. Delays could come from:
- delays dispatching the queue for notifications on BGA side (that could potentially happen at peak time if there are too many notifications; is there a specific time of the day where you experience this?)

Here is some information on time of day.

Code: Select all

Date		Time (UTC-7) 	Delay Between Notification Timestamp and
				Receipt of Notification
2022-06-08 	14:18 		3 minutes
2022-06-08 	20:31 		10 minutes
2022-06-10 	23:13 		8 minutes
2022-06-12	21:15 		5 minutes
2022-06-13 	12:09 		5 minutes
2022-06-13 	15:13 		4 minutes
2022-06-16 	15:34 		3 minutes
2022-06-18 	22:56 		4 minutes
2022-06-26 	20:40 		3 minutes
2022-06-27 	20:17 		8 minutes

Delays 2 minutes or under are not included. I perhaps should have included 2 minutes because that is close to running out of time if you don't see the notification.

[Een]

Thanks for gathering some data!
It seems to be very irregular, and that's a relatively small number of notifications with a big delay. Not sure how you collected data, but if you have somehow automated this, what would be interesting would be a histogram with the number of notification received under 10 seconds, under 20 seconds, etc.
NB: this histogram would still characterize only the set (your device / your browser vendor infrastructure / your ISP) but it would still be interesting to see.

Delays 2 minutes or under are not included. I perhaps should have included 2 minutes because that is close to running out of time if you don't see the notification.

I suppose that it means that you are using webpush notifications to play realtime? Playing a move then closing the app or multitasking to another?
I'm not really sure it's a good idea: by nature, webpush notification are asynchronous, without a guaranteed delivery delay (just like email). Very often it goes pretty fast, but there is no guarantee that it will be fast enough for realtime usage (you have probably had this experience being on the phone with someone and them sending you an email, and waiting, waiting... then hanging up and getting the email 3 seconds later; it's just the same).

[Meeplelowda]

Thanks for gathering some data!
It seems to be very irregular, and that's a relatively small number of notifications with a big delay. Not sure how you collected data, but if you have somehow automated this, what would be interesting would be a histogram with the number of notification received under 10 seconds, under 20 seconds, etc.
NB: this histogram would still characterize only the set (your device / your browser vendor infrastructure / your ISP) but it would still be interesting to see.

Haha. Another programming project to use to procrastinate from the programming projects I'm supposed to be doing. (even now I'm hearing the thought in my head that it probably won't be so hard to implement)

But in reality, many notifications come practically instantaneously. In fact, it is fairly common that I'll get a game end notification before I see the final move on my screen. A large portion of notifications also come within a minute. I can't be more specific because I didn't capture that data and vague feelings about statistics are inherently unreliable.

I suppose that it means that you are using webpush notifications to play realtime? Playing a move then closing the app or multitasking to another?
I'm not really sure it's a good idea: by nature, webpush notification are asynchronous, without a guaranteed delivery delay (just like email). Very often it goes pretty fast, but there is no guarantee that it will be fast enough for realtime usage (you have probably had this experience being on the phone with someone and them sending you an email, and waiting, waiting... then hanging up and getting the email 3 seconds later; it's just the same).

I just use it for game start notification in case I shift focus to another browser window or step away from the computer for a minute or so. Some games can take 5 to 10 minute or more to find a real time opponent. But ultimately I know that it is my responsibility to stay on top of it and maybe using this as a crutch does more harm than good because it causes me to be less diligent about dequeuing from a game when I step away.

[Mixxster]

For me uninstalling the "app" on Android, and reinstalling it made me go from chromium V113 to V116 in the notification settings on board game arena, under push notifications. That fixxed the problem for me. (I use brave browser, based on chrome)

[Kuma74]

@mixxster, thanks for the suggestion. I'd noticed my notif's had been broken for maybe up to a week, now?
They seem to be working again, huzzah!

[Myr4el]

@Mixxster: thank you so much, I wasn't getting notifications either but reinstalling fixed the problem. Yay!

[chewy1893]

What app??? I checked App Store but found no bga app??
Also my notifications say I can do it on my web browser on my phone. Ugh this is annoying.

I just want to know when my opponent does his turn soo I can do mine and not check like 1000 times a day.