Closed rankinit closed 3 years ago
I am experiencing this issue as well. apn command line works fine. system "apn ..." also works fine (no surprise). Just not getting any notifications sent using using Houston APN.
Anything else to verify, check? I hacked in a bunch of debug logging in Houston client.rb and no errors are returned, etc.
ruby version: ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-linux] Houston gem: 2.2.3
I experience the same issue where it works in the CLI with -e, -c and -m all set, but not sending from a persistent connection.
I logged all I could, and I receive no errors on the backend.
I ran out of ideas. Anyone managed to fix this?
houston (2.2.3)
EDIT: The problem was in one of the token. As soon as one of the device token is invalid, APS will stop sending notifications for all the futur token on that connection. I ended up running a Feedback Service job before pushing notifications, and it's working now.
A year later, I've found 2 tokens that work opposite of each other. Only Houston APN can send notifications to 1 of them, and only apn command-line can send to the other token. Both are running on the same production box.
Has anybody else seen this issue? Any suggestions?
Ruby 2.2 Rails 4
I followed the example code to send production notifications which does not work. However command line "apn push -e production.... " works. What do I have to do to get the production push code notifications working using the example code?
Obv. the example code was not copied verbatim ... the relevant device token & messages were changed. Currently I use the following code to send push notifications in production:
system "apn push \"#{device_token}\" -e production -c pro.pem -m \"#{message}\""