9to5 / pushr-gcm

PushrGCM

Please see pushr-core for more information.

pushr-gcm's Issues

Android notification failing all the time -- working with typhoeus/curl

This is what I have in the log: notice that it said Error and then delivered even though it never was delivered.

2015-06-17_17:43:09.15713 [2015-06-17 10:43:09 -0700] ERROR: [android: ConnectionGcm 1] Authentication exception received.
2015-06-17_17:43:09.15721 [2015-06-17 10:43:09 -0700] INFO: [android: ConnectionGcm 1] Message delivered to {"type":"Pushr::MessageGcm","app":"android","registration_ids":["MYID"],"notification_key":"ALERT_UPDATE_AVAILABLE","collapse_key":"ALERT_UPDATE_AVAILABLE","delay_while_idle":null,"time_to_live":7200,"data":{"alert_id":"ALERT_UPDATE_AVAILABLE","alert_args":["Zedd: ","10:43 am "],"alert_time":1434562988,"delivery_confirmation":false}}

I tried using the same hash.to_json with typhoeus and in curl, it worked successfully.

How do you create GCM Feedback objects?

The APNS side of the house provides ConfigurationApnsFeedback.create to define a feedback object in Redis. How do we do the same for GCM? I don't see any feedback running for Gcm, so I assume I need to create a Feedback object in Redis.

YML Config data should be validated

would be super helpful if the required keys in the YML would be validated