Skip to content
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

Open
dlikhten opened this issue Sep 10, 2013 · 6 comments
Open

Tracker#set method no longer receives the expected response. #123

dlikhten opened this issue Sep 10, 2013 · 6 comments

Comments

@dlikhten
Copy link

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.

NoMethodError: undefined method `body' for 1:Fixnum
from /Users/dlikhten/.rvm/gems/ruby-2.0.0-p247@global/gems/mixpanel-4.0.7/lib/mixpanel/tracker.rb:71:in `parse_response'
@reconbot
Copy link
Contributor

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.

@dlikhten
Copy link
Author

This happened today. I'll investigate more tomorrow.
On Sep 10, 2013 9:22 PM, "Francis Gulotta" [email protected] wrote:

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.


Reply to this email directly or view it on GitHubhttps://github.com//issues/123#issuecomment-24207026
.

@dlikhten
Copy link
Author

I just made a manual request to mixpanel's api with the data, the response is not a JSON, but rather an integer.

@xxx
Copy link

xxx commented Sep 11, 2013

+1. We have the exact same issue since upgrade to 4.0.7 from 4.0.5 yesterday.

@reconbot
Copy link
Contributor

Downgrading to 4.0.5 will solve this issue for now.

@dlikhten
Copy link
Author

The offending commit: 3e1cb1c

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants