I am investigating AUTHENTICATION_FAILED error which occurs when I regist C2DM by using the ChromeToPhone application.
The C2DM reference document says as below. But actual behaviour, however, is a little different from that document. I have some questions about this.
AUTHENTICATION_FAILED : Bad password. The application should ask the user to enter his/her password, and let user retry manually later. Fix on the device side
[1] Change the password
- Change the password of Google account by using the PC.
- My android phone shows
Sync errorat the view of Settings::Accounts & sync::(My Google account). - I succeed in the registration of c2dm on my android phone by using the ChromeToPhone application.
- Next, Reboot the android phone.
- The C2DM registration returns the
AUTHENTICATION_FAILEDerror.
1st question:
I think it should return AUTHENTICATION_FAILED error on step3. But Why I succeed?
[2] Delete the account
- Delete the Google account by using the PC.
- My android phone shows
Sync OKat the Settings::Accounts & sync::(My Google account). - Next, Reboot the android phone.
- The C2DM registration returns the
AUTHENTICATION_FAILEDerror.
2nd question:
[2] is not the conditon of ‘Bad password’. Do you know another conditon that AUTHENTICATION_FAILED will be returned like this?
[3] Multi account
- Change the password of Google account.
- Add another valid Google account to my android phone.
- Reboot the android phone.
- The C2DM registration returns the
AUTHENTICATION_FAILEDerror.
3rd question:
Does the primary Google account on the phone have to be valid to succeed in the C2DM registration?
Thank you for reading this question. Please answer my question, if you like.
In your “[1] Change the password” use case, step 3. Did you try to uninstall ChromeToPhone from device completely, install it again. Would it register C2DM successfully after that? If you didn’t do that it could have C2DM token already available that’s why it doesn’t bother about changed password.