This repository has been archived by the owner on Mar 9, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 92
Previous worker not sending notifications for new Apns Apps #141
Comments
Yep, this is by design. See https://github.com/ileitch/rapns/wiki/Hot-App-Updates I am tempted to change this behavior though and have the new apps auto-loaded. |
oh, Ok, Thanks for the response |
If someone stumbles accross this, Heroku doesn't support signals |
Reopening this as a reminder to myself to work on improving this case. |
So is there anyway to remedy this "issue" on Heroku given the lack of support for signals? Thanks again for this great gem! |
@y2kRules Add the heroku-api gem And issue a heroku.post_ps_restart(ENV["HEROKU_APP_NAME"], 'ps' => 'rapns.1') whenever you want to restart the worker |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi @ileitch, first of all thanks for the great work on the rapns gem,
I'm having a small issue and wanted to ask you about it:
When my rapns worker is running and I create a new Apns App, notifications are not send for this new app unless I restart the worker. Is it by design? have you run into this problem before? how have you addressed it?
I'm leaving you a small log sample from my app running on heroku. You can see there that I have to restart the worker so the notifications for the new app are sent.
Thanks in advance,
SM
The text was updated successfully, but these errors were encountered: