Tracker#set method no longer receives the expected response.

[dlikhten]

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]

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]

This happened today. I'll investigate more tomorrow.
On Sep 10, 2013 9:22 PM, "Francis Gulotta" notifications@github.com 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]

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

[xxx]

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

[reconbot]

Downgrading to 4.0.5 will solve this issue for now.

[dlikhten]

The offending commit: 3e1cb1c