I am working on Push Notifications for Samsung Gear S3 using Tizen Wearable Web Application. My application got Approval from the Tizen team to use the Push Notifications. I followed the guidelines of Push Notifications and integrated the Push Notifications code in my application.
I am able to receive RegId using
tizen.push.registerService(service,registerSuccessCallback,errorCallback);
Now when I am connecting to the Push Service using below method,
tizen.push.connectService(notificationCallback, errorCallback);
I am not receiving any notifications. I tried on both emulator and real device (Samsung Gear S3 Class 2.3.2.1).
When I sent the push notification from the server, I got the success response from the push server
Request :
{
"regID": "XXXXXXXX",
"requestID": "273f0307",
"sender": "Madhu",
"message": "badgeOption=INCREASE&badgeNumber=1&action=ALERT&alertMessage=Hi I am a Test Notification"
}
Response :
{"results": [{"regID": "XXXXXXXXX","requestID": "273f0307","statusCode": 1000,"statusMsg": "Success"}]
}
Even though I am receiving success response from the Push Server its not delivering the Push Notifications to the device/emulator.
Please provide the solution how can I get the push notifications deliver to my application.
I was having a similar problem. I discovered an error in the logs that indicated that it was looking for the "appData" field. The documentation says that you can include EITHER "appData" or "message", but it appears that you must have BOTH present in 2.3.2. Tizen 3.0 doesn't seem to care.
Related
Hello stack overflow community, I'm using the cross- platform FCM (Firebase Cloud Messaging) to send push notifications from my server developed with spring-boot java to my application developed with android studio java. I have an issue which is sometimes I send the push notification from the server and everything is fine (the response i get indicates that the push notification has been sent) but I don't receive it on my mobile app.
I should resend it many times to receive the last notification I sent. And sometimes I must wait almost 15 minutes to receive one notification. I want to know if the problem is with my code or in the server of firebase.
Does anyone facing issue with fcm to delivery push notification with HTTP v1?
I've an scenario in which I'm having strange issue. When I'm running an debug build or release build in my mobile, I'm able to receive push notification in device with high priority but when I'm sending push notification to those users who have downloaded same build from play store, they're not receiving push notification on device side.
While I'm not getting any error response from fcm service https://fcm.googleapis.com/.../projects/messages:send when sending push notification to client who have downloaded from play store. While using same API, it's delivering push to client's device who've installed direct .apk file.
Can anyone have an idea or might have faced similar issue in past?
Is it possible to identify whether a particular push notification message was delivered to a particular token via Firebase Cloud Messaging? And, if so, is it possible to do so via an API call or by listening to some callback?
I know that I can look at aggregate statistics in the console and even segment those statistics through analytics tags, but cannot find a way to get more discrete information.
I also know that the API will synchronously respond if a token is invalid but the process by which Apple and Google invalidate tokens is a bit opaque (to me) and doesn't help if someone simply turned off push notifications for my app.
Thanks!
Jason
If someone turned off push notification – you can check it with code
Swift ios check if remote push notifications are enabled in ios9 and ios10
Android app - detect if app push notification is off
But user can be offline, or APNs / Firebase service – can get some problems and your notification will be drop. You can check delivery status with some code in iOS and Android applications.
If you need check, delivery status for some push you can make push notification extension (in iOS). For send status about delivered notification in your API. More info about push notification extension.
https://developer.apple.com/documentation/usernotifications/unnotificationserviceextension
It can be helpful
https://developer.apple.com/documentation/usernotifications
https://developer.apple.com/documentation/usernotifications/modifying_content_in_newly_delivered_notifications
https://firebase.google.com/docs/cloud-messaging/understand-delivery
https://firebase.google.com/docs/cloud-messaging/android/receive#handling_messages About handling messages in Android (you can send status delivered too)
I hope this answer will help with your problem.
UPD:
https://firebase.google.com/docs/cloud-messaging/understand-delivery
Received (available only on Android devices) — The data message or
notification message has been received by the app. This data is
available when the receiving Android device has FCM SDK 18.0.1 or
higher installed.
I have an Azure Web Service which is using an Azure Notification Hub to push data notifications using FCM via Firebase to a Xamarin Android App. Initially the app is getting a token which is posted to the web service. The web service then sends it with the data to the notification hub which is sending it to Firebase. The response back from the hub is indicating a successful transfer it seems from the notification properties and the ReqID property. But the notification is not reaching the app. Is there a way to see individual notifications' status on the Firebase site? Currently I don't see anything under the "Cloud" report for Data.
[
Thanks for asking question! One of the notification failure point could be when sending it from FCM to user device. To confirm this, you may try getting a delivery receipt from FCM.
You may refer to this article Receive delivery receipts. It says for Android and Chrome client apps, you can get delivery receipts which can be sent from FCM to your app server. To enable this feature, the message your app server sends to FCM must include the field delivery_receipt_requested. When this field is set to true, FCM sends a delivery receipt when a device confirms that it received a particular message. Also check for firewall on the user's network.
My setup include a webapp, a backend server and an android app.
I want to be able to chat between my android app and webapp.
Init:
Android app has subscribed to the topic /topics/chatGroupName
Similarly on browser, I get the registrationToken and send it to my server where I use code similar in https://github.com/ToothlessGear/node-gcm/pull/211/files (addToTopicNoRetry) to subscribe the browser to the topic: /topics/chatGroupName
When I send a message from the web, I use my backend server to send a GCM message on a topic like /topics/chatGroupName and the android app receives this message.
But when I send GCM message from Android app on this topic /topics/chatGroupName, I dont get any notification on the browser app.
Even my https://iid.googleapis.com/iid/info/REGISTRATION_TOKEN?details=true shows that this registration token has already subscribed to /topics/chatGroupName
Firebase has now released javascript library that supports FCM push notifications with support for topics.
Ref: https://firebase.google.com/docs/cloud-messaging/js/client