Thomas Kollbach

It seems this issue is not present in 2.0.1 anymore. Using Resque with a single persistent connection.

@k3mm0tar True, I think I had a problem in my test setup. Now it does the same thing here as well.

It is a bug I the gem. More precisely in my update to it. Please use either an older version or my fork (https://github.com/toto/APNS) until it is fixed.

@wlipa indeed, that is a bug I introduced when updating the lib. Will have a look why the tests did not catch this, they should have.

I verified that this is indeed the cause of the multi-notification problem. @theosp can you please bump the bundle version as well (https://github.com/toto/APNS/commit/f134e9057765716a42dc6bfb086e96e1daa1a249), so @jpoz can quickly merge this in....

True, unfortunately only @jpoz can do that. As he does not seem to notice this thread, I will try him via mail.

Thanks for merging. would be glad to help. I will make sure to build a regression test for this problem. Currently only the single notification is tested, not what get's...

I have cleaned up a few things and added patches. Take a look at https://github.com/toto/APNS. I will do a new PR, so @jpoz can take a look. I bumped the...

Also I should note that I use my 1.1.1 code in production sending out push to >100k devices - including `content_availible`pushes. So the format implementation is robust.

\o/