No PushNotification received using FCM in swift 4 - push-notification

I have followed the steps given in https://firebase.google.com/docs/cloud-messaging/ios/client.
There are no errors while running the app but I am unable to receive the push notifications.
GoogleService-Info.plist has been added.
Enabled push notification services apple account as well as in the Xcode under capabilities.
Build the app in an external device rather than the simulator.
Is there any piece of code or step that I have missed out? Can someone help me sort this out?

Related

Can FCM push notifications in Electron App

I'm trying to send notifications from Firebase Cloud Messaging (FCM) to a window app (window form for example) but it doesn't seem to be possible (since fcm only supports android/ios/webapp, for here and here).
So trying building Electron app to be able to receive and display notifications from fcm (slack is built from electron js and also displays notifications, here), and found the electron-push-receiver allowing it to receive notifications from FCM
But it seems that there is no update for a long time, so there is a issue#80
Now is it possible to build electron application that can receive notifications from FCM?
Thank you very much!
I just implemented FCM in my Electron app earlier today by following the guide here:
https://github.com/CydeSwype/electron-fcm-demo
Screenshot of FCM working in an Electron app
I was skeptical at first as well, given that the repo hasn't been updated in a while, but was pleasantly surprised that it still works.
If you have any further questions, go ahead and I'll try to help :)
I also got this working with electron-push-receiver, though I had to do a workaround for more recent versions of Electron.
I looked at the firebase-admin.messaging Node package but that is only for privileged environments.
The HTTP 503 issue you linked it seems was just another outage that has been resolved; I can still register for push notifications with this setup.

Firebase Cloud Messaging - Identify delivery status for a particular push notification message

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.

Push notifications when user force quits the app

I have implemented onesignal in my iOS app as per the setup instructions given here (https://documentation.onesignal.com/docs/ios-sdk-setup).
When I install the app for the first time, I get notification from Onesignal dashboard.
When I kill the app, I still seem to get the notification.
But when I launch the app again, I stopped receiving any notification until I uninstall and install the app again.
So am I missing anything here? Do we receive push notification even if app is killed by the user?
You can receive push notifications on your app whether it is active, in background or killed using the NotificationServiceExtension.
The OneSignal documentation shows how to do this:
https://documentation.onesignal.com/docs/silent-notifications
Relevant Apple Docs:
https://developer.apple.com/documentation/usernotifications/unnotificationserviceextension

FCM console push test is currently broken? (Android)

I've been using FCM console(web) to test push notification for Android smartphone.
I use push token from Android device, but FCM console says "Completed" and it's not delivered.
It worked fine before, but recent few days, it's not working.
Is there anyone facing same problem?
I got an answer from FCM support team.
Thank you for that information.
It would seem that you are affected by the changes made between July
31 and August 1st. We rolled out a change to Firebase Notifications to
filter apps by GMP App Id rather than by package name. This change was
purely internal and should have had no effect on visible behavior as
all apps using Firebase should have had both package name and app id
set to match. However, we are now seeing some apps that have the wrong
app id set and this is causing messages to not be delivered (or in
some cases to be delivered to the wrong app if an app has the app id
of another app). These apps have a bug that was previously masked but
is now exposed.
We are investigating ways in which apps have sent these incorrect app
ids and ways in which we can catch them and warn app developers.
For now, the Firebase Notifications console will only work with apps
that use the FCM SDK. We recommend updating to the latest version of
the FCM SDK in order to mitigate the issue, but in case you don't want
to migrate to FCM SDK, you can still use your own server to send push
notifications.
Apologies for the inconvenience this may have caused. Please let me
know if there's anything else I could help with.
Regards,

Apple Push Notification: Device registered, but not receiving notification

I have an ios app that uses IBM Bluemix MobileFirst Push notification. In the Bluemix console, I can see my device is registered. But when I sent notification from the console, I didn't see it on the device.
I have followed apple tech note and installed ersistentConnectionLogging.mobileconfig. The log files related to apsd is at https://drive.google.com/file/d/0B5Up86Av5djnb0VDUEQ4STFWSzA/view?usp=sharing.
the mobile is connected via cellular data.
Can you please help me to look at the log and see what is wrong?
Thanks Josh for your great help to find out that my Bluemix app is in the sand box while my provisioning is for the production env.
How to move to the production mode, see https://mobile.ng.bluemix.net/imfpushrestapidocs/#!/applications/put_apps_applicationId_settings

Resources