|
To All GooSync Users. Below is a list of current issues we have discovered with your help. If you find your problem on this list please be patient and we'll keep you informed of the status of a fix. If your problem isn't on this list, post the details in a new post on the group and please include the following details: 1. GooSync username 2. Device type 3. Any error messages on your device Current Issues------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Description: Google rejects events being added that contain attendees. Status: This only seems to affect a small number of attendees for some unknown reason. We are working with Google on tracking down the bug.
Updated: 14:40 BST 24/05/07 by Matt (GooSync Support) Description: Repeat exceptions created on Palm OS devices are not sent to Google. Status: The problem is caused because GooSync is detecting these repeat changes as double modifications (changed on both the device and in Google before the sync). When this happens the Google data takes priority and is sent to the device, overwriting the device change. When this happens with repeat exceptions (when an entry has been modified or deleted out of a repeated event) any deleted instances are re-created on the device and any changed entries are reverted back to their original state. However, with changed entries (such as your event that had a time change) these are sent during the sync as additional, single events. Meaning that they get treated as separate events and appear alongside the repeated event.
Updated: 14:20 BST 28/06/07 by Stuart (GooSync Support)
Kind Regards
|
| ||||||||||||||||||||||||||||
| Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy |
| ©2009 Google |