I did a quick test of the approach that I think you meant:
- On lifecycle, I went into “application registered for remote notifications”
- There, I did a set value for a device variable that I just named “push_id” to equal the token from the event data - application registered for remote notifications
Then on a separate screen (after user logged in, so safely after the push_id was saved), I used a Run API Service to push the push_id to my Bubble backend, saving it under the User in a field I made also called push_id.
So it worked i think? But I noticed on the Bubble backend that what was saved was a 64 character long combo of numbers and characters.
What do I do with this, do you know?
I noticed that the Player ID on my OneSignal dashboard is a different, shorter combination of characters, and I looked up the length of a UDID and it seemed to also be shorter.
Just curious to get your advice on:
What is this 64 character combination? Is it useful, if so how do I use it?
Still feeling my way around DropSource/OneSignal/Bubble
Thanks so much for the support!