Question

I know there is unique registartionId get from users email address for sending message to his device, but also do i need to have different authenctication id for each user?

If I am right we just need registrationId to send message to user, where as AuthenticationId is static, which is use to send message to user with registration id.

but in my case, I got Authentication Token using my developer email address, and if send message to the same email address I receive message. and If I send message to another user using registration id received from his email address and using authentication token got from my developer account email address user didn’t receive message.

and again if I use authentication token got from user’s email address and password and using his registration id user receive message.

Answer 1

The authenticationToken confirms that you have a valid Google account and thus are in general allowed to send C2DM messages. The registrationToken is directly tied to a user’s device and your application. It allows your application to use your authenticationToken to send a message to the user’s device.

You need one authenticationToken to send messages to all devices for which you have registrationTokens. Note however, that you should pick up a new authenticationToken every time you start sending messages, as those can be changed by Google at random.

I recall reading that Google advises to use different mail accounts for sending and receiving.