This happens because the app always multiplies timemodified by 1000 because it assumes the timestamp is in seconds, but when creating an offline entry the timestamp is in milliseconds. This probably affects timecreated too.

Also, I saw that in the sync process we're probably comparing an "online timemodified" (seconds) with an "offline timemodified" (milliseconds).

We should probably store the times in seconds in the app DB, or convert them as soon as they're read to be sure they're consistent everywhere.