NoMethodError: undefined method `[]' for nil:NilClass

[eriknomitch]

pusher-client (master) works fine for a few messages until it (consistently and mysteriously) errors out with:

Dispatching global callbacks for pusher:error
Pusher : error : #<NoMethodError: undefined method `[]' for nil:NilClass>
Pusher : event received : channel: ; event: pusher:error

I am running asynchronously and have a binding to pusher:error. I'd also like to note that "channel: " looks blank (line 3).

I've checked my Pusher debug console and all of the messages look okay.

Thanks,
Erik

[eriknomitch]

I understand no one is under any obligations here, but unfortunately this is hanging up Prelang's new product development.

I'd be extremely grateful if someone came to the rescue.

@logankoester @zimbatm

Erik

[leggetter]

@eriknomitch have you raised a support ticket? Just so I know and can grab any information that may be available from it.

Also, what version of:

1. The gem are you using?
2. Ruby are you using?

Please provide any additional information too.

I'll discuss with the support team on Monday.

[leggetter]

@eriknomitch In addition to the info above, could you please provide a sample piece of code to replicate this? Thanks.

[eriknomitch]

@leggetter Thanks for getting back to me. Nope, I haven't raised a support ticket. Should I?

ruby 2.2.0p0 (2014-12-25 revision 49005) [x86_64-linux]

And from Gemfile.lock (of the Rails app which is using a Gem which requires pusher-client):

GIT
  remote: git://github.com/pusher/pusher-websocket-ruby.git
  revision: 247d125cc656439a07e74da7bf43da7317dfd5d3
  specs:
    pusher-client (0.6.0)
      json
      websocket (~> 1.0)

The same thing is happening on the released Gem.

I think this is going to be hard to reproduce on your end but I'll give you as much info as I can in a little bit.

[zimbatm]

Hi @eriknomitch , can you try without the use of async ? The implementation is using the Thread but the rest of the library (and maybe your code) is not thread-safe. I have also pushed a number of fixes in #46 if you want to try them out.