Tomdroid does not send the "create-data" field in JSON when web syncing

Watch out, I made a typo. The missing field is "create-date"

As I am currently working on a sync server and looking at the lowel data that tomdroid transfers, it would also be very helpful to get the raw JSON data tomdroid sends into the log (via TLog). The JSON tomdroid *reveices* is already logged, but the raw JSON that is send over the wire will be as helpful.

Thanks for reporting this bug. Can you try the latest revision and let me know if this is fixed?

The data sent is being logged, afaics, at SnowySyncService.java line 397:

TLog.v(TAG, "pushing data to remote service: {0}",data.toString());

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Noah, thanks for your fast fix. Please push your bugfixes only to
lp:tomdroid otherwise it will get confusing. I already merged your
recent changes for now.
Thanks!

On 03/11/12 13:21, NoahY wrote:
> Thanks for reporting this bug. Can you try the latest revision and
> let me know if this is fixed?
>
> The data sent is being logged, afaics, at SnowySyncService.java
> line 397:
>
> TLog.v(TAG, "pushing data to remote service:
> {0}",data.toString());
>
>
> ** Changed in: tomdroid Status: New => Fix Committed
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCVIswACgkQXeaPvgR0RGch+wCfa5domMXhaOK8mPlFXMNDCzT6
Oh8AoNTdT/+s51jalaLGVcioTV9EA0sy
=exGF
-----END PGP SIGNATURE-----

unfortunately, that does only fix it half :/ Stefan just send me a new build with the fix in place and i tested again: The last-metadata-change-date is now set correctly, but the create-date field is still send incorrectly. I assume that is because create-date is not well-formated, using .format3339(false) ?

Here is the sniffed JSON:
185312 [DEBUG] Rainy.WebService.RequestLogFilterAttribute->RequestFilter - Received request at: //api/1.0/johndoe/notes
JSON Data received:
{
 Username: johndoe,
 latest-sync-revision: 1,
 note-changes:
 [
  {
   title: asdfg,
   note-content: dggdtv,
   note-content-version: 0.3,
   guid: f5614cc3-bdf6-4e86-b2ff-3c2da525d881,
   create-date: "1970-01-01T00:00:00.0000000+00:00",
   last-change-date: "2012-11-03T14:38:33.0000000+00:00",
   last-metadata-change-date: "2012-11-03T14:38:33.0000000+00:00",
   last-sync-revision: 0,
   tags: []
  }
 ],

(observe that last-metadata-change-date now is changed, which inidicates that new build stefan send me already includes the fix).

I think I see the problem; Tomdroid doesn't store create dates in the database yet so they are given as the epoch date. Someone will have to modify the database to store them. Anyway, that create date should allow you to sync, since it is formatted properly, afaics.

Storing the epoch-date on the sync server is no problem, but when tomboy pulls the note it performs some date calculations and somehow tries to substract from the epoch date (which will cause an overflow exception). As a workaround, one could send a newer timestamp as the create-date, like i.e. 1.1.2000. That might fix the sync issues without having to patch tomboy.

Nonetheless, tomdroid should store the create-date for a note, since it is usefull information to the user. So maybe put this into a another bugreport titled "Save note creation date in the database".

By the way, the sync server I am working on is now on github and has extensive logging, might be usefull for any tomdroid user or developer: https://github.com/Dynalon/Rainy

i changed the date to 1.1.2000 ;-) and created a new bug for storing the create date