Beginning May 1, 2012, we're ending our support for the small percentage of mobile browsers that can't use cookies. This update will only affect older generation mobile browsers, primarily based in Japan, that don't support authentication cookies for signing in to Google services. Most mobile phones will not be affected.

What's changing?

When signing in to a Google service (like Gmail), after you provide your username and password, your mobile browser receives an authentication token. This allows you to access Gmail, Google Calendar, and other Google services without having to sign in everytime. Authentication tokens are typically stored in the form of a cookie. A few older mobile browsers don't support cookies, and so we temporarily retained a legacy mechanism for authentication.

In order to focus on new feature development, we're ending this legacy mechanism. Beginning May 1, 2012, we will support only mobile browsers that are able to use cookies. On these legacy mobile browsers, you can continue to use other Google services that don't require user login, such as Search and Maps.

How do I know if my mobile browser is affected?

If you're using an older mobile browser that doesn't support authentication cookies, you'll see an alert when you try to sign in to your Google Account or Google Apps account.

If you have an unsupported mobile browser, we suggest you check the mobile browser requirements for Gmail to find a compatible device. We are working to provide the best experience with Google products using the technologies provided by modern mobile browsers.

Editions included:
Google Apps, Google Apps for Business, Government and Education

For more information:
http://support.google.com/a/bin/answer.py?&answer=2473579

whatsnew.googleapps.com
Get these product update alerts by email
Subscribe to the RSS feed of these updates