We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently if you run go get https://github.com/OneSignal/onesignal-go-api you get the 1.0.4 version.
go get https://github.com/OneSignal/onesignal-go-api
This version has a wrong interface for the CreateNotification request. It includes the Tag key instead of the Filters array.
When will a new version be out? this is blocking us from evaluating one signal
run `go get https://github.com/OneSignal/onesignal-go-api` in a golang project
I expected to get the files as they are in the master branch
No response
The text was updated successfully, but these errors were encountered:
Hello i have same problem.
Sorry, something went wrong.
is there any progress ?
Also, in version 1.0.4, NewNotification sets isIos to true for no reason
NewNotification
isIos
true
I was also running into this issue, you have to specifically select the /v2 package version, otherwise, you will only be able to pull up to v1.0.4.
/v2
v1.0.4
go get -u github.com/OneSignal/onesignal-go-api/v2
change all import with
github.com/OneSignal/onesignal-go-api/v2
in all code
go mod tidy go mod vendor
No branches or pull requests
What happened?
Currently if you run
go get https://github.com/OneSignal/onesignal-go-api
you get the 1.0.4 version.This version has a wrong interface for the CreateNotification request. It includes the Tag key instead of the Filters array.
When will a new version be out? this is blocking us from evaluating one signal
Steps to reproduce?
What did you expect to happen?
I expected to get the files as they are in the master branch
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: