-
Notifications
You must be signed in to change notification settings - Fork 28
broken on Parse-Server 2.3.3 #33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can you provide more informations please? The changes on Parse-server were not supposed to affect adapters |
when i push in the cloud it returns a promise resolved to true but I noticed on my one signal dashboard a new user is added without a device. Before this would not create a new one, < v2.3.3. The device and platform will be empty, subscribed will be set to "no" and not like the picture shown I can't reproduce again since I have downgraded back to 2.3.2 but I will be happy to help. Im guessing the deviceToken is not being returned in I do not know about IOS yet since I have only tested it on android. |
i forked the repo and updated some stuff to change it to sending the playerID instead of the deviceToken. the catch is that you have to get the playerID on the client using their provided SDKs, which is fine in my case of the project. it's not 2.3.3's fault, something changed in one signal's REST api |
Uh oh!
There was an error while loading. Please reload this page.
caused by parse-community/parse-server#3080.
deviceToken is not being sent
The text was updated successfully, but these errors were encountered: