Hi

"Type" is a reserve word in rails 3.2, migrations need to change. All 3 tables has Type reserved field

vamshi

it looks like :expiry is not handed on to APNS in the #to_json method

APNs document says it accepts 4KB of payload but BinaryNotificationValidator limits it to 256 bytes. I think it should be 4096. Or am I missing something?

errors in the error log do not list what the invalid token was - this is pretty annoying, and
the only remedy is then to look in the database.

When surfacing the error, the device token should be included in the error message

  [ERROR] [Push::DeliveryError, Unable to deliver message 12345, received APNS error 8 (Invalid token)'

Using Rails 4.0.2 with Ruby 2.12p95. I'm trying to include the content_available attribute in my push message, Everything works fine when I don't include content_available. When I include content_available :

Error = unknown attribute: content_available

Here's a snippet :

        apns_msg = {
          app: 'FEMA',
          device: device.push_token,
          alert: headline,
          sound: 'default',
          badge: device.local_alerts.count + 1,
          content_available: 1, # use this if you want the iOS app to auto launch upon receiving this notification
          attributes_for_device: { identifier: alert.identifier }
        }
        apns_msg[ :expiry ] = time_to_live if ( time_to_live.present? )
        Push::MessageApns.create( apns_msg )

Maybe it's because of the check in message_apns.rb for ActiveModel::MassAssignmentSecurity? Didn't that go away in Rails 4?

attr_accessible :app, :device, :alert, :badge, :sound, :expiry, :attributes_for_device, :content_available if defined?(ActiveModel::MassAssignmentSecurity)

I had to change the first line to this in order for it to work.
string_or_json = properties[:alert]
The read_attribute(:alert) returns nothing. And thus no text in the notification that's sent.