Hey everybody,
Is anybody experiencing some issues with MobileMe in Lion?
I have Lion installed on a partition, just a complete new installation.
When I sync with MobileMe, I have it set to "Replace all information on this computer, things like system preferences, mail, notes, dock items etc etc..
But, it starts syncing, then in the status it says "Cancelling" - and stays like that.....for as long as I've left it..
But it'll also randomly pop up saying there is a conflict, either replace all information on MobileMe with the new information from Lion or fix later...obviously, I don't want to replace all information on MobileMe, because that'll effect Snow Leopard.. So I have to click Fix Later.. then it'll pop up about 15-30 mins later (Sometimes sooner..sometimes later). It'll also pop up a dialogue for each setting like Prefs, notes, mail etc.
Annoying.. If it wasn't for that, I'd keep using Lion.
This happened on the very first build, and each update including Dev 3.
I filed a report awhile back too.
Just wondering if anyone has come across this issue too?
And if there was anything I could try to maybe fix?
Thanks!
Is anybody experiencing some issues with MobileMe in Lion?
I have Lion installed on a partition, just a complete new installation.
When I sync with MobileMe, I have it set to "Replace all information on this computer, things like system preferences, mail, notes, dock items etc etc..
But, it starts syncing, then in the status it says "Cancelling" - and stays like that.....for as long as I've left it..
But it'll also randomly pop up saying there is a conflict, either replace all information on MobileMe with the new information from Lion or fix later...obviously, I don't want to replace all information on MobileMe, because that'll effect Snow Leopard.. So I have to click Fix Later.. then it'll pop up about 15-30 mins later (Sometimes sooner..sometimes later). It'll also pop up a dialogue for each setting like Prefs, notes, mail etc.
Annoying.. If it wasn't for that, I'd keep using Lion.
This happened on the very first build, and each update including Dev 3.
I filed a report awhile back too.
Just wondering if anyone has come across this issue too?
And if there was anything I could try to maybe fix?
Thanks!