OneSignal issues
Hi, I have recently attempted to integrate OneSignal with Novu, and I am not sure the documentation answered some questions well enough or I probably didn't understand it well enough.
I went as far as adding the credentials from onesignal in and that bit is fine, I added the sdk to my frontend application and have setup novu to set the device token.
now this is where it gets confusing.
I use the user ID for registering subscribers in novu, and this id is what I assumed the device token will be, except it is used as external_id in onesignal, and I would need to retrieve the onesignal_id or player_id in order to have the correct device token. this would mean I will have to make a separate api call to my backend in order to store the device token and this step seems redundant to me.
I noticed that the onesignal implementation in novu uses the include_player_ids for device tokens, so the external id will not work, however onesignal supports the include_external_user_ids as an alternate to include_player_ids, and that would negate the need to fetch and use player_ids completely.
At this point, I wonder, would it make sense to have an option as part of the configuration of onesignal to indicate if you use player_id or external_ids and that switches between include_player_ids and include_external_user_ids ?
or have I completely missed something in my analysis?
I went as far as adding the credentials from onesignal in and that bit is fine, I added the sdk to my frontend application and have setup novu to set the device token.
now this is where it gets confusing.
I use the user ID for registering subscribers in novu, and this id is what I assumed the device token will be, except it is used as external_id in onesignal, and I would need to retrieve the onesignal_id or player_id in order to have the correct device token. this would mean I will have to make a separate api call to my backend in order to store the device token and this step seems redundant to me.
I noticed that the onesignal implementation in novu uses the include_player_ids for device tokens, so the external id will not work, however onesignal supports the include_external_user_ids as an alternate to include_player_ids, and that would negate the need to fetch and use player_ids completely.
At this point, I wonder, would it make sense to have an option as part of the configuration of onesignal to indicate if you use player_id or external_ids and that switches between include_player_ids and include_external_user_ids ?
or have I completely missed something in my analysis?
