I originally tested SS for the trial period. The setup was: 1 user side on an iMac 1 user side on a MacBook 1 iPhone
Everything went quite well. That was my testing environment. Upon success there, I amped it up to my real setting. The real setting was: 2 user sides on an iMac 2 user sides on a MacBook Pro 2 user sides on another MacBook Pro 2 Android phones All of these locations needed the same calendar data. I wiped all syncing data clear in all devices, and all calendars were clean. SS was installed to handle all of the calendar data for all 8 locations. Almost immediately SS did a poor job. There is a single, consistent bug that we simply cannot rid of. When entering calendar data on any of the user sides, sometimes that data will somehow localize: it will exist as a double event on that machine, and either not sync or sync as a ghost. If I go to the google web calendar and delete the event, that delete action will not sync through to the machine the event was made on. Or, if there are two copies of the event on that machine (a result of some error), it will delete the event data taht was pushed back through from google servers, but not the original. It seems to only happen if we are entering a couple of events at once, of if SS engages in the middle of editing calendar data. This is going to make SS prohibitive to use. We did everything correct in set-up. This is an application bug, and I really don't want to have to go through the process of getting our money back. We really do want the service to work. -- You received this message because you are subscribed to the Google Groups "Spanning Sync" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/spanningsync?hl=en.
