gcm.unregister()/register() fails after user logs out of chrome profile, and log back in

[Keven Wang]

gcm.unregister() and register() return the error: "Profile was not signed in."

This only happens when log out, and log back into Chrome profile.

[Keven Wang]

As additional info, my gcm-internal page looks like follows:

[Filip Gorski]

Hi, Keven,

chrome.gcm is currently only available with a signed in profile, hence the message.

With Chrome 39 we will be gradually enabling signed out profiles to take advantage of it. You can start testing it out canary and dev channels (which are fully enabled to take advantage of the new capability).

Thanks.

Filip

[Keven Wang]

This is great news! This can drive adoption of GCM service.

The bug I filed is different. This bug happens when user IS logged into chrome profile. register() and unregister() fails when user logs out once, and log back in.

[Filip Gorski]

Hey, Keven

We traced the problem and fixed it earlier this week.

thanks.

Filip

[Keven Wang]

Great news! What version of Chrome will it ship in? So I will look out for it.

Thanks!

Keven sent from smartphone

--
You received this message because you are subscribed to a topic in the Google Groups "GCM for Chrome feedback" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gcm-for-chrome-feedback/Q_HHWcELCkA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gcm-for-chrome-fe...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Filip Gorski]

Hi, Keven,

The fix was merged to Chrome 40 (should be available in beta soon).

We also checked that the particular problem we were chasing is not active in Chrome 39.

Please let me know if you can reproduce this issue on the latest builds later this week.

Thanks.

Filip