We have a web application in PHP through which we sent events android push notification to users on our app.On web we have provided a select,after what time do they need alert 15min,30min for that event.A alert push notification is to be send on the device before 15 and 30 min start of the event.We have a corn job which sends a push notification to be send on the device before 15 and 30 min start of the event
Problem area:
We our getting a push notification when we post it but we are not getting notification for the alerts.Corn job working fine. We our receiving success response from the Google.But not receiving notification on phone
can any one suggest what else need to be done on this.
Related
I am using the MS example for showing a local notification. I am scheduling a daily repeating notification and need to modify the title and message each day based on an API call. I tried modifying the title & message that is sent to iOSNotificationManager.ReceiveNotification() at L31 in iOSNotificationReceiver.cs, but the original title/body is always shown in the notification.
I thought maybe I could not show the original notification and create a new notification to be shown in 1 second; janky I know but it was an idea. The trouble I ran into here is that the original notification is shown even if I return at L72 in iOSNotificationManager.cs before NotificationReceived?.Invoke(null, args); is called.
So how do I modify the title and message when just as the notification is being shown? This works perfectly fine in Android.
One thing I could do is only schedule 1 notification and when the notification is shown schedule tomorrows notification. However, if for some reason the notification was never shown one day then the next day would not be schedule therefor canceling the daily scheduled notification.
https://learn.microsoft.com/en-us/samples/xamarin/xamarin-forms-samples/local-notifications/
Modifying the data shown in a notification for iOS is impossible after the notification has been set. There is no callback method that can be used in iOS like on Android when a notification is shown.
To set the daily notification on repeat with different message the best course of action is to use push notifications. However, not having push notifications setup I set up 64 notifications, which is the max iOS allows, for the next 64 days.
Note: iOS only allows 64 notifications to be set per app.
I'm working on an app that receives notifications using Firebase Cloud Messaging in flutter.
I can receive notifications in Background, Terminated, and Foreground perfectly.
However, when I try to turn off(Shut it down) my phone and send notifications from FCM Console I only receive the latest sent notification or sometimes I don't receive anything at all.
For example, I sent 4 notifications from the FCM console when my Phone is shut down(dead) when I turn it on again. Instead of receiving 1, 2, 3, 4 notifications I only receive the last notification 4 and sometimes none at all!
Any links to read and any details as to why this behaviour is occuring is a very big help.
I do use onesignal API to send/ receive push notifications.
Is there a way to send/receive web notification only when user is online: if offline, then push is discarded (online = browser opened)
ex: user1 has his browser closed. A notification is sent.
Normally, he will get it next time he opens his browser.
Is there a way a discard that notification ?
(sent when he was offline)
Yes, you can achieve this with the TIME TO LIVE option, by default is 3 days but you can set to 0 and the message will be discarded if the user is offline.
Source
I've configured the push notifications following this guide and when calling the watch endpoint I get an expiration of about one week.
During this period I expect to receive notification to the Pub/Sub topic I've configured without the need to call the watch endpoint some time before the expiration date.
However what happens is that after about one day I'm not receiving notifications anymore and calling the watch endpoint doesn't help.
Why GMail has stopped to send notification to the subscription endpoint?
Push Notification had been executed and worked perfectly in my
application. (I made use of worklight push notification module IBM
LINK)
There was a scenario which i experienced during the
notification received in the application android device.
The push notification is received perfectly in all the situtaion except when i am in the Login Screen(When i am in the login screen of the application the push notification is not received in my application).
Question :
Why push notification is not received in the application ?
What is the client side (Device side) architecture/execution flow , by which i can
understand when is the PushNotification Receiver (Broad Cast
Receiver) in device is ready to receive the notification and when it
can't receive notifications ?
This is the expected behavior.
You've implemented event source-based pus notifications. In this type of push notifications you must first login in order to receive notification. This is why while you're at the login screen, you will not receive the notification.
If you are using either Worklight 6.2 or MobileFirst Platform 6.3, you can use tag or broadcast-based notifications which do not require a login.
You can read more about these at the IBM MobileFirst Platform developer center.
Here is a rundown of possible scenarios:
Application is closed - notification arrives to device - by opening the application / tapping the notification in the notification bar, you will get a login screen. After you login you will actually see the payload (in the way you choose to, that's purely applicative). You will not see the actual payload, because you don't want user B for example to see the payload of user A.
Application is opened - you are logged in, but the app is in the background - notification arrives to the device - by tapping the notification or bringing the application to the foreground, because you are already logged in, you'll see the payload
Application is opened - you are NOT logged in - notification arrives to the device - you will not be able to see the payload, because you are not logged in.
Application is opened - you are logged in, and the app is in the foreground - notification arrives to the device - you will immediately see the payload (per your applicative code)