Async requests have stopped working in 4.1.0

[Radagaisus]

Hey,

It seems like asynchronous requests have stopped working in the most recent version of the gem (4.1.0 and 4.1.1).

Our usage is very simple:

$mixpanel = Mixpanel::Tracker.new($mixpanel_api_token, {async: true})
# And anywhere else in the app..
$mixpanel.track(event, params)

With the async parameter, requests are not received by Mixpanel. Without it, it works fine. Tested on Rails 3.2.13 and Ruby 1.9.3p327.

Would love to provide more information if needed.

On a different note: It's great that we now have an official gem supported by the Mixpanel team, but this one provides much more functionality and ease of use. Would be great to see it continue being maintained, at least until the official gem provides the same capabilities :-)

[zevarito]

Hi,

I am not providing support for this gem anymore, are you able to downgrade
a couple of versions to see if it works?

I could not promise to tackle your issue because you know end of year are
busy days but if you couldn't find a solution downgrading the gem version I
could see how I can help you.

Good luck!

On Sat, Dec 28, 2013 at 5:38 AM, Almog Melamed [email protected]:

Hey,

It seems like asynchronous requests have stopped working in the most
recent version of the gem (4.1.0 and 4.1.1).

Our usage is very simple:

$mixpanel = Mixpanel::Tracker.new($mixpanel_api_token, {async: true})

And anywhere else in the app..

$mixpanel.track(event, params)

With the async parameter, requests are not received by Mixpanel. Without
it, it works fine. Tested on Rails 3.2.13 and Ruby 1.9.3p327.

Would love to provide more information if needed.

On a different note: It's great that we now have an official gem supported
by the Mixpanel team, but this one provides much more functionality and
ease of use. Would be great to see it continue being maintained, at least
until the official gem provides the same capabilities :-)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/132
.

Alvaro

[evaniainbrooks]

Likely it is the same issue as this: #127