What other solutions are you guys using? I'm about to give up on Spanning Sync because of this and ask for a refund.
Unfortunate that it's happened this way, but there hasn't even been any update to the Google discussion for this problem since June 10 - and that discussion seems to indicate the Spanning Sync devs are having issues communicating with Google. The last post was from a USER pleading for some relief, and there was no reply. Given that, I'm not sure Spanning Sync has a very high likelihood of any sort of workaround, or that Google has any sort of fix coming in the near future. Devs: It's been nearly a month now - should you not be considering alternative strategies? Apparently there are other sync programs that do NOT have this issue so other methods clearly exist. I appreciate your posting to let everyone know it's Google's problem, and I can appreciate that - but it doesn't look like Google is going to fix it, so either you need to implement a workaround or take steps to discontinue Spanning Sync, at least in its current form. Nothing personal - I'm just saying what many are thinking. -- 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.
