Google calendar sync is inconsistent

[mobileorg-android on behalf of hjh]

Why would MobileOrg refuse to sync into the phone calendar all of the files
that were pushed?

I just noticed my phone calendar was missing about 80-90% of the scheduled
items that were properly imported into the MobileOrg database. So I thought
I could fix it by clearing the database and re-importing. Same result --
missing almost everything.

So then I added a node in one of the files that wasn't syncing well,
pushed, cleared the db, and resynced. Then I got the scheduled events from
the changed file, but the phone calendar was missing events from another
file -- and that file was syncing ok before!

I'll try clearing all the app data (not only the database) and resyncing.
If it still doesn't work, I'll have to conclude that the checksums are
cached somewhere.

hjh

[mobileorg-android on behalf of Henning Weiss]

When hitting the "clear database" option in the preferences, all calendar
data should be deleted. You might also want to try to delete or change the
android calendar you are using.

Henning


On Sat, Apr 20, 2013 at 2:24 PM, mobileorg-android on behalf of hjh <

Post by mobileorg-android on behalf of hjh
Why would MobileOrg refuse to sync into the phone calendar all of the
files that were pushed?
I just noticed my phone calendar was missing about 80-90% of the scheduled
items that were properly imported into the MobileOrg database. So I thought
I could fix it by clearing the database and re-importing. Same result --
missing almost everything.
So then I added a node in one of the files that wasn't syncing well,
pushed, cleared the db, and resynced. Then I got the scheduled events from
the changed file, but the phone calendar was missing events from another
file -- and that file was syncing ok before!
I'll try clearing all the app data (not only the database) and resyncing.
If it still doesn't work, I'll have to conclude that the checksums are
cached somewhere.
hjh
--
You received this message because you are subscribed to the Google Groups
"mobileorg-android" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/mobileorg-android?hl=en
.
For more options, visit https://groups.google.com/groups/opt_out.

[mobileorg-android on behalf of hjh]

On Apr 20, 2013 10:44 PM, "mobileorg-android on behalf of Henning Weiss" <

Post by mobileorg-android on behalf of Henning Weiss
When hitting the "clear database" option in the preferences, all calendar

data should be deleted. You might also want to try to delete or change the
android calendar you are using.

Clearing the app data did it.

I remember now that I had a failed sync a couple of days before noticing
the phone calendar problem. Is there possibly something in MobileOrg's
logic that gets confused if one or more files failed to download? A
possible explanation for the behavior I saw is that MobileOrg thought it
didn't have to sync those items to the phone calendar because it "already
processed" that file (when in fact, something went wrong and processing
hadn't finished). If that's the case, merely resyncing wouldn't work
because the file's checksum didn't change.

hjh

[mobileorg-android on behalf of Henning Weiss]

On Sun, Apr 21, 2013 at 2:46 AM, mobileorg-android on behalf of hjh <

Post by mobileorg-android on behalf of hjh
On Apr 20, 2013 10:44 PM, "mobileorg-android on behalf of Henning Weiss" <

Post by mobileorg-android on behalf of Henning Weiss
When hitting the "clear database" option in the preferences, all

calendar data should be deleted. You might also want to try to delete or
change the android calendar you are using.
Clearing the app data did it.
I remember now that I had a failed sync a couple of days before noticing
the phone calendar problem. Is there possibly something in MobileOrg's
logic that gets confused if one or more files failed to download? A
possible explanation for the behavior I saw is that MobileOrg thought it
didn't have to sync those items to the phone calendar because it "already
processed" that file (when in fact, something went wrong and processing
hadn't finished). If that's the case, merely resyncing wouldn't work
because the file's checksum didn't change.
hjh

Which synchronizer are you using?

Henning

[mobileorg-android on behalf of hjh]

On Apr 21, 2013 6:19 PM, "mobileorg-android on behalf of Henning Weiss" <

Post by mobileorg-android on behalf of Henning Weiss
Which synchronizer are you using?

Currently Ubuntu One. It /usually/ works, but there is this funny thing
that happens a lot on the mainland, where you send the request for some
content and the reply never comes back. It's sporadic. A similar problem is
sometimes a slow DNS: the request times out once, and then comes back
quickly the second try.

Likely, for most MobileOrg users, the network Just Works so some
fault-tolerance issues never get discovered, until I hit them *giggle*

hjh

[mobileorg-android on behalf of Henning Weiss]

On Sun, Apr 21, 2013 at 3:01 PM, mobileorg-android on behalf of hjh <

Post by mobileorg-android on behalf of hjh
On Apr 21, 2013 6:19 PM, "mobileorg-android on behalf of Henning Weiss" <

Post by mobileorg-android on behalf of Henning Weiss
Which synchronizer are you using?

Currently Ubuntu One. It /usually/ works, but there is this funny thing
that happens a lot on the mainland, where you send the request for some
content and the reply never comes back. It's sporadic. A similar problem is
sometimes a slow DNS: the request times out once, and then comes back
quickly the second try.
We have had a discussion about the Ubuntu One synchronizer here<https://github.com/matburt/mobileorg-android/issues/265>.The

next version will have a timeout that hopefully will prevent this issue
from happening.

Post by mobileorg-android on behalf of hjh
Likely, for most MobileOrg users, the network Just Works so some
fault-tolerance issues never get discovered, until I hit them *giggle*

Yeah, this makes it relatively difficult for us to troubleshoot and test.
The next version will also have a wifi-only synchronization option. Maybe
this could serve as a workaround in case you are experiencing too many
problems with MobileOrg and your DNS.

Henning

[mobileorg-android on behalf of hjh]

On Apr 22, 2013 8:17 PM, "mobileorg-android on behalf of Henning Weiss" <

Post by mobileorg-android on behalf of Henning Weiss
Yeah, this makes it relatively difficult for us to troubleshoot and test.

The next version will also have a wifi-only synchronization option. Maybe
this could serve as a workaround in case you are experiencing too many
problems with MobileOrg and your DNS.

The slow response from the DNS occurs on the home network (WiFi) as well,
not only the mobile data connection.

hjh