Hi, everyone, i used GCM days ago and it work well. but now i can't receiver any push messages, server send the message ok, and the log is: 07-12 14:20:50.735: D/ihsgcm(2239): send result error code name is null, whole result is [ messageId=0:1342074228753551%921c249af9fd7ecd ]
but i can't receiver any push message with my client, and i tried use the google example(gcm client), it can't receive any one. dan all the clients didn't print any logs. please help me. On Wednesday, July 11, 2012 4:00:25 AM UTC+8, Senad wrote: > > Nevermind my last post.. I've figured out I used the wrong senderID.. > > One have to use the ID generated in the address bar.. e.g: > > https://code.google.com/apis/console/?pli=1#project:*64654065106* > > > Thanks, > Senad > > > > On Tuesday, July 3, 2012 12:11:25 PM UTC+2, Senad wrote: >> >> Hi, >> >> I've had C2DM implemented and working as well and now switched everything >> to work with GCM. >> >> The serverside seems to work well, meaning I'm getting the >> InvalidRegistration >> which is expected because I cannot register with my device. >> I've setup new API Project and registered my project with brand new >> Project ID which I've set to be the Sender ID in my app but I keep getting >> the INVALID_SENDER error. >> >> >> Any help appreciated.. >> >> (I've opened a new topic for my issue as well but as I'm new to this >> group it takes forever to get populated :( ) >> >> Thanks, >> Senad >> >> >> >> On Friday, June 29, 2012 4:22:02 AM UTC+2, RyanMC wrote: >>> >>> We are in the final stages of developing an app that had utilized C2DM >>> for push notification, and decided to swap over to the new GCM since we >>> hadn't released yet and it seemed like a good idea. >>> >>> However, this is proving to be a giant headache. We have the JSON and >>> headers formatting correctly and we get back a valid response, but the >>> failed count is always 1 and the error message is UNAVAILABLE. The >>> documentation says to just try again, but this has proved pointless as it >>> always returns the same result. I have seen several posts on stackoverflow >>> and other sites that list a similar problem. Has anyone been able to get >>> the new GCM stuff working? We are using a php backend to handle the push >>> notifications. We are using the standard CURL library, and as far as I can >>> tell the JSON is valid, and works as we do get a result. Prior to swapping >>> out the old message attribute with the new data attribute it would fail to >>> return any result, so I am pretty confident we have it right. >>> >>> Any thoughts would be appreciated. >>> >> -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
