我可以将 OneSignal 令牌导入 FCM 吗？

Question

I have several thousand OneSignal web push notification tokens I want to import to FCM. Is there a way to do this?

I see this endpoint which requires the https://fcm.googleapis.com/fcm/send/...key... endpoint that OneSignal gives me, but I don't know what to put in for auth and p256dh .

https://developers.google.com/instance-id/reference/server#create_registration_tokens_for_apns_tokens

Answer 1

So yes this can be done. First you will need to contact OneSignal support and get the public and private VAPID keys for your app. Each app in your dashboard will have a different set.

Next you will need to make an API call to OneSignal in order to export the users in a CSV file.

You can find the API url in the docs and use curl or use your favorite language. I used Node + Axios to make my calls. The API call will supply you with a link to download the CSV.

Here is the documentation https://documentation.onesignal.com/reference#csv-export

You want to make sure you add the "extra_fields" parameter to your request with the "web_auth" and "web_p256" fields added. The CSV will provide you with the other piece of the puzzle which is the endpoint url in their identifier column.

Once you have all this information you can now send pushes using a library such as web-push for Node

https://github.com/web-push-libs/web-push

Hope that helps!

EDIT

As Cedric stated the actual push payload is a little bit more complicated because you need to comply with the OneSignal Service worker data handling.

You can see the formatting starting at line 313 here

If you are using a library like web-push for Node to send your push payloads your payload would be formatted something like this for a standard push to a OneSignal service worker.

const uuidv1 = require('uuid/v1')
const webpush = require('web-push') 

let subscription = {
    endpoint: 'USER ENDPOINT URL',
    keys: {
        auth: 'USER AUTH KEY',
        p256dh: 'USER P256 KEY'
    }
}

let vapid = { private: 'VAPID PRIVATE KEY', public: 'VAPID PUBLIC KEY' }

// Format Message for OneSignal Service Worker
let notification = JSON.stringify({
    custom: {
        i: uuidv1(), //Generate UUID for the OneSignal Service worker to consume
        u: 'CLICK URL'
    },
    title: 'TOP TITLE',
    alert: 'MESSAGE BODY',
    icon: 'ICON IMAGE URL'
})

webpush.setVapidDetails('mailto: sendError@YourEmail.com', vapid.public, vapid.private)
webpush.sendNotification(subscription, notification)

Answer 2

It's much more complex than Dan's answer. If your users don't subscribe to your own service worker, it won't work. OS will send its default notification when an 'unknown' error occurs, which it will send "You have new updates" as a notification to the user even though you passed different payload. You also need to pass: "custom": { "i": uuidv1() } to your payload for it to work. (don't forget to install uuid first through npm and call it). Check out this link and you'll figure out what other payload props you need to pass.

Answer 3

Dan's answer explains how to use third party push library, not FCM itself.

I've imported OneSignal's public and private VAPID keys into Firebase project/Project settings/Cloud Messaging/Web Configuration/Web Push certificates.

Then in OneSignal's CSV export found test token in 'identifier' column, ie https://fcm.googleapis.com/fcm/send/SOME_TOKEN

Then tried sending the notification using:

curl --ssl-no-revoke -X POST -H "Authorization: key=SERVER_KEY" -H "Content-Type: application/json" -d "{\"to\": \"SOME_TOKEN\", \"notification\": { \"title\": \"Hello\", \"alert\": \"World\", \"icon\": \"https://example.com/icon.jpg\", \"image\": \"https://example.com/icon.jpg\", \"custom\": { \"i\": \"00000000-0000-4000-8000-000000000000\", \"u\": \"https://example.com\" } }}" "https://fcm.googleapis.com/fcm/send"

But it returns "MismatchSenderId" error.

Also tried updating push subscription to make use of exported columns web_auth and web_p256: https://developers.google.com/instance-id/reference/server#update_push_subscriptions but always getting "Request contains an invalid argument" error.

What am I missing?