Google Sync for iOS devices is still in beta. We're constantly working on improvements, but we've listed below some known limitations of Google Sync for iPhone, iPad, and iPod touch.
Known Issues with all iOS versions
- Invalid Password Prompt. If you see an error message that reads "Invalid Password", it's likely that you'll need to unlock your account by solving a short CAPTCHA. Visit the appropriate link below and fill in your email address, password, and the letters in the CAPTCHA box:
General users and Google Apps customers: https://www.google.com/accounts/UnlockCaptcha
Google Apps customers not yet on the new infrastructure: https://www.google.com/a/your_domain.com/accounts/UnlockCaptcha. Be sure to replace your_domain.com with your actual domain name.
- iOS 5 only: iOS 5 has mailbox folder features not supported by Google Sync. In your Apple Mail client in iOS 5, you can create, delete, rename, and move a mail folder on your iOS device. These actions will only affect folders on your device, and these changes won't sync with your Google Account.
- We currently don't support editable drafts when composing email.
- When using Google Sync, certain actions in Gmail may have a different behavior than you're used to. For instance, if you "delete" a message from your Inbox, the default action is that it will archive the message and not delete it. To delete the message, you need to select Enable "Delete Email As Trash" for this device in your Google Sync settings. See our complete list of how actions taken on your device affect your Gmail interface.
Calendar: Issues with Accepting/Declining events:
- iOS device can't Accept/Maybe/Decline events from invitation emails received via POP3 polling.
- Accepting an event invitation from Google Calendar doesn't dismiss the existing event invitation on the device.
- Secondary calendar events with invites are read-only on iOS devices. The device can't Accept/Maybe/Decline events on secondary calendars.
- Accept/Maybe/Decline page has a field to Add Comments, but changes in this field will not be synced with Google Calendar.
Calendar: Issues with recurring events
- Attendee status changes may not sync. Under certain circumstances when you're invited to a series of recurring events, choosing Save for all events after accept/maybe/decline will only apply the change to the one selected event.
- Imported recurring events may not sync. If you've imported calendar entries from another calendar system into Google Calendar, you may find that only the first occurrence of the event is synchronized, or - in some cases - the event may not be synchronized at all. Events which occur multiple times per month (for example "the first and last Monday of each month") cannot be accurately represented in the Microsoft Exchange ActiveSync protocol. Recurring events created within Google Calendar will sync correctly.
- Duplicate event created when changes are made across daylight savings time. This issue arises If you edit an instance of the recurring event after the first event and remove the attendee, selecting Save for future events. In some cases, the iOS device doesn't correctly make these changes, and two separate event series are created that overlap a day. This problem often affects events created in the GMT timezone when the series of events spans a Daylight Savings Time boundary.
Example: If a series of recurring events is created in August and a change is made to an instance of the series in December, the iOS device will show both the original event and the changed instance in the Calendar application.
- Limited Contact Information. The iOS device can synchronize up to 3 email addresses. Phone number synchronization is limited to 2 Home numbers, 1 Home Fax, 1 Mobile, 1 Pager, 3 Work (one will be labeled 'Company Main') and one Work Fax number.
- iOS 4.0 only: Security restrictions force 1-min lockout. Many users are seeing an auto-lockout and password requirement, if the device is left idle for more than one minute (regardless of whether or not device management restrictions are set). This is due to a change in iOS4, and we are currently communicating with Apple for a fix. We're also working on a short-term workaround in the meantime.