Google Cloud Messaging for Chrome Error 500

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Set Up developers.google.com/oauthplayground to test GCM for Chrome
2. Use your own OAuth credentials
3. try to POST a message:

POST https://www.googleapis.com/gcm_for_chrome/v1/messages
Host: www.googleapis.com
Autherization: Bearer ppppppppppppppppppppppppppppppppppppppppp

{

'channelId': '111111111111111/ffffffffffffffffffffffffffffffff',
'subchannelId':'0',
'payload':'YEA'

}




What is the expected output? What do you see instead?

I expected an acknowledgment of a succesful delivery. 
I get this instead:

HTTP/1.1 500 Internal Server Error
Content-length: 52
X-xss-protection: 1; mode=block
X-content-type-options: nosniff
X-google-cache-control: remote-fetch
-content-encoding: gzip
Server: GSE
Reason: Internal Server Error
Via: HTTP/1.1 GWA
Cache-control: private, max-age=0
Date: Mon, 20 May 2013 17:13:22 GMT
X-frame-options: SAMEORIGIN
Content-type: application/json; charset=UTF-8
Expires: Mon, 20 May 2013 17:13:22 GMT
{
 "error": {
  "code": 500,
  "message": null
 }
}



What version of the product are you using? On what operating system?
Chrome 28.0.1500.11 (Official Build 199640) dev-m, 64 bit Win7

Please provide any additional information below.

Another user posted this on stackoverflow and hasn't received much infomation.

http://stackoverflow.com/questions/16545721/google-cloud-messaging-for-chrome-er
ror-500

Original issue reported on code.google.com by r...@andymark.com on 20 May 2013 at 5:59

[GoogleCodeExporter]

I am facing similar issues but after integrated Oauth2.
Client that authorised Plus and Oauth2 api can not receive push Gcm.
Internal server error 500, received in sudden 

Original comment by luongson...@gmail.com on 21 Feb 2015 at 3:23