Safari push notifications using Node.js - safari-push-notifications

I have some queries below
How to integrate safari push notification using node.js after creating certificates of website.
How to get authentication token.
Device token
Please tell me the actual flow,I followed this link but, I get some version Issues.


firebase-admin send FCM to specific android using device token as authentication

Hello guys I am using firebase-admin, it works fine sending and receiving using notification topics, however our project requires to send FCM to specific android device using device token. I can't find example in the repository of firebase-admin
Several examples available at

Migrate parse "deviceToken" to FCM registration token

I have thousands of users on Parse, and we are sending push notifications to them using parse.
Now we are migrating to firebase and can't guarantee that all users will open the app so FCM gets the new FCM registration token.
The question is can I send to old Parse users given I have their Parse device token (from installation table)?
I'm pretty sure you can't just import the tokens used by to Firebase Cloud Messaging for use. What should be done is to register your client app users to FCM by adding it to your app.
More details can be found in the Migrate your Parse Android App to Firebase (or if you're using iOS) docs:
Suggested Migration Strategy: Migrating Device Tokens
At the time of writing, the Parse Android SDK uses an older version of the FCM registration tokens, not compatible with the features offered by Firebase Notifications.
You can get a new token by adding the FCM SDK to your app; however, this might invalidate the token used by the Parse SDK to receive notifications. If you want to avoid that, you can set up the Parse SDK to use both Parse's sender ID and your sender ID. In this way you don't invalidate the token used by the Parse SDK, but be aware that this workaround will stop working when Parse shuts down its project.
From my answer here.

Google SignIn in Android and IOS with backend server

I am developing an app in Android and IOS. I want to use the Google Sign In to login in the app.
In Android I use the client ID of the backend server, but in IOS I have to use the IOS app client ID to login.
Is not possible to use the backend server client ID in the IOS app?
Google Documentation
I work on the team at Google: yes, unfortunately, this is a known deficiency and inconsistency of the iOS SDK for Google Sign-In. We're working on some changes and I'll update this answer when this is resolved.
For now, your backend server will have to determine what client the token is coming from and check appropriate audience. Very sorry for the trouble :/

Can I use new Parse App API for upload iOS Push Certificates?

I'm wondering if I could use the new parse app api, for update information about ios certificates, more precisely, to upload them.
This is not supported by their Apps API.
Edit: Here is a list of what is supported via the endpoint:
...Client Side Class creation
...Client Push
...Revokable sessions
...Revoking a session on password chang

"backendError" when migrating Google marketplace App from v1 to v2 using UpgradeableApp API

We're trying to migrate an app from v1 (using openid) to v2 (Oauth 2.0) in the Google Apps Marketplace.
The old app is published in the old marketplace.
The new app is published in the Chrome Webstore.
We have associated the new app to the old app, using the webstore App id.
As a result, the install button in the old marketplace now says "Install App" (as opposed to the old "Add it now"). It works fine.
However we're also trying to migrate existing domains from the old app to the new app.
We are using the UpgradeableApp API, using an HTTP PUT request to this URL:
note we url-encoded the : in the old listing id with %3A, but even leaving the : the result is the same.
And signing it using 2-legged OAuth, using client Id and client secret of the old app, calculating and the adding the "Authorization" header to the request.
When we send the request, however, this is what we get back:
{"error":{"errors":[{"domain":"global","reason":"backendError","message":"Backend Error"}],"code":500,"message":"Backend Error"}}
with an HTTP status code 500 (internal server error).
This does not seem to be an authentication error message, but it is not very clear what is causing the error... Something wrong on our side? Something temporarily wrong on Google's side (that is what I would assume, from "Backend Error")?
Has anyone encountered this cryptic error message before, while using this API?
We can provide a full network trace (with the real listing id, app id and domain names) as a private message, if necessary.