-
Notifications
You must be signed in to change notification settings - Fork 20
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
[Bug]: Executing getPlayer
request with Identity Verification enabled is throwing an error
#19
Comments
@arquadrado Thanks for reporting this issue. We will look into reproducing the issued based on the details you provided. |
Hey @arquadrado , sorry for the delay. We are about to release updated version of our library. I will update this issue when its done. |
Hey @arquadrado Please let us know if the issue still persists. |
I'm receiving a similar error using
|
Closing as outdated. 400s have been added to all responses for a while now. |
What happened?
I am using the node client to interact with OneSignal's API and I am having trouble getting players since I enabled
Identity Verification
. I followed this and this documentation page but I always get a400
response.Steps to reproduce?
Just run this snippet with valid values, in my case I am trying to get a player which has the device type equal to
11
(email):What did you expect to happen?
I expected to receive the requested player. I am able to retrieve players without device
type=email
and I was printing some values inside the client code and it has the email auth hash available and builds the request with it. I am assuming it's something in the API itself and not the client.Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: