If the notifications are received successfully on the iOS device without delayed_job, you could check 'target_ad.start_time' value is in correct timezone and in the future. Perhaps, the delay time is old and a new notification is not created.
Few other values to check include - valid device_token in your database, along with APN error messages within your logs (invalid certificates, null device tokens, payload length, etc) On Thursday, September 18, 2014 9:54:26 AM UTC-7, Chris Griffin wrote: > > I do. If I take delayed_job out of the equation the notifications work > fine. -- -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby --- You received this message because you are subscribed to the Google Groups "SD Ruby" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
