Google has deprecated the previous method of sending push notifications. It will stop working on June 2024. If you have an already working solution then you only need to update the B4J side. Do make sure that you switched from the service to a receiver on B4A. The new API is (confusingly) named...
www.b4x.com
Everything has been working fine until today (June 1st) when all notifications stooped this morning. I remembered that as mentioned in the post -
"Google has deprecated the previous method of sending push notifications. It will stop working onJune 2024."
So thinking that this deadline may be the issue, I went ahead and generated a new sign key as per the instructions in the above post for B4J - However, the notifications still do not work.
[edit] - Working now with both sign keys. Must have been an issue with Google's server. I wish there was an alternative that allowed us to use our own server instead of a 3rd party server.
Yes... I was using the new code posted in the thread I mentioned above and using the B4J FCMPush Program to send test notifications.
Anyway, it's working again now without any changes. Must have been an issue with Google's server - I was not getting notifications all morning and could not figure out why.
I have had problems with FCM since April where there is delays etc, and I got Google AI robots replying to my emails when I reported the issue I was having. Today it seems to be no delay and there status checker page shows that other people also had issues with delayed push notifications. I guess it takes an human to check out the issue and not rely on there AI robots to review issues.
I have had problems with FCM since April where there is delays etc, and I got Google AI robots replying to my emails when I reported the issue I was having. Today it seems to be no delay and there status checker page shows that other people also had issues with delayed push notifications. I guess it takes an human to check out the issue and not rely on there AI robots to review issues.
Thanks! The link should be useful in the future. Since this is the first time it's happened to me, I thought it may have been related to the June 2024 deadline to make the switch to the new API (which I actually did from the beginning). The deadline is actually June 20th.