-
Notifications
You must be signed in to change notification settings - Fork 84
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
Tracker#set method no longer receives the expected response. #123
Comments
It doesn't appear they have changed their api, is this ongoing? The mixpanel blessed gem does look interesting, however it's premature to change over to it. |
This happened today. I'll investigate more tomorrow.
|
I just made a manual request to mixpanel's api with the data, the response is not a JSON, but rather an integer. |
+1. We have the exact same issue since upgrade to 4.0.7 from 4.0.5 yesterday. |
Downgrading to |
The offending commit: 3e1cb1c |
Looks like mixpanel may have changed their API. The #set no longer works.
Site note: They now have this nifty https://github.com/mixpanel/mixpanel-ruby gem which just handles the ruby side of transmission, but doesn't do client side middleware, or the async: true feature.
Sounds like we basically should wrap all ruby-side calls with invocations of the original gem.
The text was updated successfully, but these errors were encountered: