I previously setup an Appcelerator Titanium project with push notifications (as per my Stack Overflow question How to configure Android Push Notifications (GCM) in Appcelerator Titanium Dashboard?) and for some months my Android app has been receiving the appropriate push notification from GCM, but I'm now receiving reports that this no longer works from end-users.
The flow usually goes like this...
Android app sends android push token to my Java server
Java server persists the Android push token
Java server sets up Amazon Web Service SNS endpoint for GCM and stores this endpoint for later use.
(some time passes)
Java server invokes Amazon Web Service SNS endpoint with a GCM payload
Amazon SNS passes message to Google GCM
GCM passes message to ti.cloud / ti.cloudpush
Phone displays push notification
The app does receive the push notification and I display an application dialog to show the contents of the message, but NO system-tray push notification is displayed, whereas I thought it was doing this in the past. No system sound is played either.
I can see that if the app is not running, then when the push notification is received the app is launched, but if the display isn't on (or locked) then the message will not be discovered for some time. I really need the native/system push notification to be in the tray.
Does anyone know why system / status notifications are not displayed? Should it be when using the ti.cloud / ti.cloudpush for Android?
Thanks
Rob.
Related
This question already has an answer here:
How to send In-APP Notification in Firebase using Python SDK for Android | iOS
(1 answer)
Closed 4 months ago.
Is it possible to send in-app notification from spring boot app?
Based on the docs and sdk firebase-admin I could send push notifications. But for in app messaging I am not sure that will help send notifications from backend server
In-app messaging, as its name implies, is for messages that are triggered from (and displayed) inside the app. When the user is not actively using the app, you'll usually instead want to send a notification to Cloud Messaging, with shows up in the notification panel.
There is no direct way to trigger In-app messaging from your own server, but since the triggers are based on Analytics events - you could send a message from your server to the device (for example as a data message through FCM) and then use that in the app as a signal to log a certain analytics event that then triggers In-app messaging.
Also see:
Firebase In-app messaging send message whenever we need option?
How to send In-APP Notification in Firebase using Python SDK for Android | iOS
I searched some notification library for react-native.
https://github.com/zo0r/react-native-push-notification
This works well for Android but it requires Apns for ios
I would like to find some libraries that doen not require Apns and simple.
There is no avoiding using APNS for remote push notifications.
In order to receive data in certain scenarios, such as having your app running in the background, phone being offline and later receiving a notification once it is back online, your device must have a unique app-specific device token generated by Apple. You can then use a service such as FCM or AWS SNS to deliver the notification to clients.
Also, for Android, you will need to use GCM to generate the device token.
You can, for testing purposes, you can use react-native-push-notifications' PushNotification.localNotificationSchedule to create a dummy local notification.
Here is a good tutorial for setting up remote push notifications with APNS and FCM: https://www.appcoda.com/firebase-push-notifications/.
We have push notifications working successfully. Backend event source is a Worklight adapter written in JS using the 'WL.Server.createDefaultNotification' and 'WL.Server.notifyAllDevices' API calls to send unicast notifications. In the front-end, the app is registered for push notification call back using 'WL.Client.Push.registerEventSourceCallback' JS API.
These particular scenarios are not working:
App is open in the background after login. Notification message is received, but user does not tap notification banner message - and instead just opens app by touching app icon. Notification callback method is not called - and subsequently payload from the backend is not available for the method.
App is open in the background after login. Notification message is received which only has iOS badge change and payload but no notification message for the banner or lock screen. In which case user has nothing to tap on. When user opens the app again - notification callback is not called.
Knowledgecenter documentation seems to indicate that the callback method should be getting invoked even if the app is running in the background. This is with Worklight 6.2.0.1.
Push is indeed supposed to work as you've describe. This is a bug.
This is no manual workaround for this.
If you are an IBM customer or Business Partner you will need to open a PMR (support ticket).
I'm creating an instant messaging application. imagine something like skype or yahoo messenger.
Now our server only sends push notification(for new messages) on when the app is on background/multitasked/minimized. But sometimes the server fails to detect that our app is on background, so sometimes it doesn't send push notification even if the app is on background.
Now I'm thinking that our server should just always send push notifications to device even if it is in foreground(so all messages will have a push notif), but we won't show it(the apns) when in foreground. This way, the server won't need to detect if the app is on background or not.
Do you think it's okay, or there will be a sideeffect of always sending apns, you see, if you are chatting whole day on foreground, the client will receive apns but won't show it?
No problem to send lots of notification without reading it, if the payload is different.
You are not forced to show notifications with an alert when a notification is received in foreground.
I am working on an iPhone application and I was wondering if I can send a command from my server to activate my application, at which point my app would contact the server with my payload.
You could send a notification to your app saying there are changes.
If the user decides to start of the app as a result of the notification, you could then check for the payload.
You can't automatically start the app with APS though.