search

OneSignal / OneSignal-Cordova-SDK

OneSignal is a free push notification service for mobile apps. This plugin makes it easy to integrate your Ionic, PhoneGap CLI, PhoneGap Build, Cordova, or Sencha Touch app with OneSignal. Supports Android, iOS, and Amazon's Fire OS platforms. https://onesignal.com
Other
251 stars 199 forks source link

[question]: Why is my subscription id always different than the OneSignal portal? #950

Closed RZR666 closed 3 months ago

RZR666 commented 11 months ago

How can we help?

So, I'm sending the below to my database,

window.plugins.OneSignal.User.pushSubscription.id

and I recieve "2e42c94b-d8e8-4b98-8f3b-c7e4947e22ca" which is completely different to my Subscription ID that gets created on the OneSignal portal.

I've tried uninstalling and re-installing the app but I'm just getting the same issue.

Any help appreciated.

Thanks

Code of Conduct

RZR666 commented 11 months ago

ok for anyone else that's having the same issue ...

window.plugins.OneSignal.User.pushSubscription.id

I've no idea what that returns, it doesn't exist in my OneSignal portal, so I ignore this completely now.

Instead I use the external id that I set in the cordova plugin, to get the user on the api side, which strangely doesn't return any subscriptions even though one gets created on the One Signal portal and this is the only user i have.

$url = "https://onesignal.com/api/v1/apps/" . $one_signal_app_id . "/users/by/external_id/" . $user_uid;

the user contains a one signal id, which is the correct one on the portal with a subscription, and I can send push notifications using that.

I can only suspect that the change from being device centric has left a lot of inconsistencies.

jennantilla commented 11 months ago

Hi @RZR666 apologies for any confusion here. OneSignal.User.pushSubscription.id should indeed match the Subscription ID field found in the dashboard. Would you be able to share the logs from your device so we can dig into this deeper? Thanks!

RZR666 commented 11 months ago

I've sent them to one signal support, Ive not heard nothing back since.

It's returning the wrong subscription id from the api too, its a subscription id that doesn't exist on the one signal portal. So it's not an sdk issue, since the api is returning the same unknown id.

josephvoxone commented 10 months ago

Indeed I have the same issue, In the past, OneSignal used to operate based on UUID Device and like IMEI, which were derived from the device being used. However, now the UUID tends to change dynamically.

jennantilla commented 3 months ago

Hello everyone, apologies that this issue has gone stale. If this is still an issue for anyone, please feel free to provide the logs from your device so we can dig into this deeper. Thank you!