-
Notifications
You must be signed in to change notification settings - Fork 128
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
list_account_subscriptions example incorrect #675
Comments
I saw in another issue that you're using the The This change was introduced with pull request #619 and is included in the breaking changes section of the CHANGELOG for the 4.x release. I apologize for the confusion. We will look into adding more visibility to these differences to the README. |
@douglasmiller you may want to update the getting started, as this is right at the top:
|
Where are you seeing that? The GETTING_STARTED on master has 4.0. If there's something off, I'd like to fix it. |
Sorry @douglasmiller , this may be ANOTHER 3.0 issue. I upgraded the gem to 4.0 as you requested and this is the method:
and I get this:
|
Relevant trace...
|
@douglasmiller any updates on this one? I see it's still closed even though it appears broken. |
The ruby 3.0.0 fixes were not included in the 4.0.0 client library release. They were merged up to the 4.x client branch in #671 which we will be releasing soon. |
ahh - that explains what I just found. When I use this: I get errors but when I reference the github branch directly:
Then it works properly. Count still doesn't work, which I know you are fixing, but good to know about the other situation. You guys really need to update your README for these situations. I wasted the day. |
@noctivityinc I just published the 4.0.1 version of the client which fixes this ruby 3.x issue with the |
The list_account_subscriptions example says this:
Which is incorrect and caused a validation error. You need to send params directly, like this:
Please update the README and docs.
The text was updated successfully, but these errors were encountered: