Failure to syn Completion status between Shuffle & Tracks

[GoogleCodeExporter]

What steps will reproduce the problem?
1a. Mark an action "complete" in Shuffle and then syn with Tracks. 
1b. No change of completion status in Tracks (ie. remain Not-complete)
or 
2a. Mark an action "complete" in Tracks and then syn with Shuffle. 
2b. No change of completion status in Shuffle (ie. remain active)

What is the expected output? What do you see instead?
as mentioned above in 1b and 2b. 

What version of the product are you using? On what operating system?
Shuffle 1.7, Tracks @ mygtdify.com

Please provide any additional information below.

Original issue reported on code.google.com by chestert...@gmail.com on 14 Apr 2011 at 3:41

[GoogleCodeExporter]

I seem to encounter a similar problem. I start with install of Shuffle 1.7.0 
from the Android Market and sync to private Tracks installation on my LAN 
(BitNami stack running on Win 7 SP1 64bit, with ruby version upgraded to 
1.8.7). Sync works as expected and actions, contexts and projects from Tracks 
appear in Shuffle. I then mark item completed in Tracks and sync again. The 
item appears completed in Tracks, however still appears as incomplete in 
Shuffle. 

I did not experience this behavior when running Shuffle 1.6.3 on Android 2.1. 
To test I downgraded to 1.6.3 installed from .apk from this site. This behavior 
does not occur in 1.6.3; if I mark item completed in Tracks and sync, the item 
does appear completed in Shuffle.

I am using Samsung Fascinate with Android 2.2 and rooted Nook Color with 
Cyanogen Mod 7.0.0 (Android 2.3). On both devices I experience this problem 
running Shuffle 1.7.0 and do not experience it if downgrading to 1.6.3.

Original comment by qul...@gmail.com on 5 May 2011 at 7:40

[GoogleCodeExporter]

I've analyzed this problem a bit since it's bugging the <deleted/> out of me.

Issue 1, "Completing in Shuffle does not sync to Tracks":
This turns out to be trivial to fix in the current code, completing a Task 
would not update its modified date, so it is not considered for synchronizing 
out to Tracks.

I've attached a patch that corrects this problem for me.

Original comment by jmbreue...@googlemail.com on 27 Jul 2011 at 11:03

Attachments:

• updateModificationDateWhenCompleting.patch

[GoogleCodeExporter]

Sub-issue 2, "Completing in Tracks does not sync to Shuffle":
Here the problem is that the local ID of the updated record is not initialized 
when writing the updated data from tracks into the Tasks' ContentResolver.
Therefore, the existing record is not updated.
[I do not know what Android's API did with the record in that case.]

Attached is a patch that corrects this half of the problem for me.
[To fix both parts of this issue, both patches need to be applied!]

Original comment by jmbreue...@googlemail.com on 27 Jul 2011 at 11:44

Attachments:

• retainIdWhenUpdatingFromTracks.patch

[GoogleCodeExporter]

I can confirm that both patches work as advertised. Applied to hg head shuffle 
(1.7.x) they make completion sync possible both ways with Tracks 2.0.

As a side note I have to say the name of TaskSynchronized.deleteEntity method 
(modified in second patch) is quite confusing, since it actually merges the 
entity if it's found from Tracks. The name should be handleMissingEntity or 
something similar, since it actually handles all entities which are found from 
tracks but missing from the todo.xml retrieved from Tracks Rest API.

Original comment by jaakko.s...@gmail.com on 10 Sep 2011 at 2:28

[GoogleCodeExporter]

s/found from tracks but/found from Shuffle but/g

Original comment by jaakko.s...@gmail.com on 10 Sep 2011 at 2:30

[GoogleCodeExporter]

Hi guys.  I am the one who initially post this issue.  And thanks very much for 
you guys' work.  

I have downloaded the patches, but just have no clue of how to use them ( I am 
not a pc tecnical person, oviously) Would someone pls explain it in steps?  
Thanks.   

Original comment by chestert...@gmail.com on 11 Sep 2011 at 5:40

[GoogleCodeExporter]

If you're interested to test this and a couple of other Tracks patches, you can 
use a temporary installation package I've built. The issues it fixes are #268, 
#238, #269 & #270. It's built from my cloned android-shuffle source tree 
http://code.google.com/r/jaakkosipari-shuffle-tracks-sync-patches/.

Be aware, however, that:
- I take no responsibility of lost data or any other problems this installation 
package or modified Shuffle application might cause you.
- Removing your current Shuffle installation will remove all your Shuffle data, 
unless you have managed to synchronize it to Tracks or have backed up the data 
some other way.
- You must remove your current Shuffle installation before installing this 
package (otherwise Android will just say that installation failed). This is 
probably because it has a different signature than the official package from 
Android Market.
- You must enable "Allow installation from unknown sources" to allow Android to 
install this package. See Settings / Applications.
- You must remove this installation package before returning to an official 
Market-version of Shuffle.
- This is really only meant to be a temporary solution before these patches are 
applied to the official source tree and released as a new Shuffle release via 
Android Market.

Keeping all of the above in mind, you can download my package from: 
http://ukuti.net/MyShuffleSigned.apk

Original comment by jaakko.s...@gmail.com on 5 Oct 2011 at 8:48

[GoogleCodeExporter]

Thanks Jaakko. Im using it. Until now its ok for the fixes. But Im having 
problem syncing with my tracks 2.0. When I sync complete actions from shuffler 
to tracks its not working. Even that, u already help a lot!

Original comment by vinicius...@gmail.com on 6 Oct 2011 at 2:50

[GoogleCodeExporter]

Since the synchronization (of the complete status, as well as of everything 
else) uses the time stamps of the events on the server and within shuffle, the 
"waiting period" between making a change and synchronizing shuffle needs to be 
larger than the clock offset between the server and the android device.

I have a few half-baked ideas about that, but for now - since my server is 
ntp-synchronized anyway - I "fixed" that problem for myself by using 
"ClockSync" on the android device.

Original comment by jmbreue...@googlemail.com on 6 Oct 2011 at 6:50

[GoogleCodeExporter]

That .apk link doesn't seem to work...

Original comment by joemburg...@gmail.com on 17 Oct 2011 at 12:41

[GoogleCodeExporter]

Original comment by andybry...@gmail.com on 6 Nov 2011 at 7:44

• Added labels: tracks

[GoogleCodeExporter]

I've just checked to see that both patches are NOT applied to the versions 
1.7.2 and 1.7.3 released in the mean time.

What needs to be done to get those two one-liner fixes applied?

Original comment by jmbreue...@googlemail.com on 10 Jan 2012 at 12:10

[GoogleCodeExporter]

I'll add these in to v2.0.0

Original comment by andybry...@gmail.com on 27 Mar 2012 at 6:47

• Changed state: Started

[GoogleCodeExporter]

Issue 127 has been merged into this issue.

Original comment by andybry...@gmail.com on 27 Mar 2012 at 6:49

[GoogleCodeExporter]

Issue 129 has been merged into this issue.

Original comment by andybry...@gmail.com on 27 Mar 2012 at 6:50

[GoogleCodeExporter]

Hmm, runningTracks 2.0.0 but after synchronizing, actions marked done in Tracks 
are not marked done in Shuffle (issue 2 in the original post). On the other 
hand, when I mark a task complete in Shuffle and sync, the task is marked done 
in Tracks, so that works fine. I run shuffle 2.0.0 in Android 2.3.4. I sync 
with tracks.smaijn.net which runs Tracks 2.0 . Same issue?

Original comment by ingrid.d...@gmail.com on 21 Apr 2012 at 7:39

[GoogleCodeExporter]

Yep, still exactly the same issue as described by ingrid in comment 16. also 
running Tracks 2.0 on android 2.3.6. I sync with tracks.tra.in.

Original comment by JJZijder...@gmail.com on 23 Apr 2012 at 7:49

[GoogleCodeExporter]

just tested (25/8/2012 5:13) this issue with following configuration:
o Tracks 2.1 running on my laptop; 
o shuffle 2.0.2 (tested on)

I confirm that also with these versions:
o marking an action complete on Tracks is NOT synced to Shuffle
o marking an action complete in Shuffle is CORRECTLY synced to Tracks

It would be great if this can be fixed in the next version of Shuffle.

Original comment by bas.aan....@gmail.com on 25 Aug 2012 at 6:15

[GoogleCodeExporter]

I can confirm that the behaviour in comment 18 is true.

Original comment by jckeert...@gmail.com on 31 Aug 2012 at 8:23

[GoogleCodeExporter]

I still see this happen.

Original comment by eyecre...@gmail.com on 6 Oct 2013 at 9:32

[GoogleCodeExporter]

Any updates on this?

I'm in search for a self-hosted GTD-Solution.

Tracks and Shuffle look promising.

Original comment by donrau...@gmail.com on 21 Jan 2014 at 7:22

[GoogleCodeExporter]

Hi,

I gave up the GTD solution consisting of Tracks and Shuffle, because of 
these synchr. problems that were never solved (as far as I know).

Just for your information: I am now using Mememto database app on 
Android, which syncs with Google docs. Maybe not ideal, but is working 
for me.

Hope this helps,

Original comment by bas.aan....@gmail.com on 21 Jan 2014 at 7:34

[GoogleCodeExporter]

Thanks for the hint.

But the point is, that I want away from the cloud based data storages.
Just not enough privacy.

Is there still active development for shuffle? 

Original comment by donrau...@gmail.com on 21 Jan 2014 at 7:50

[GoogleCodeExporter]

I went another way. I used Mailgun to forward emails to Tracks as a way to
add todos asynchronously, and the Tracks mobile interface is good enough to
review/complete items. So I'm still using Tracks (self-hosted), but not
using Shuffle anymore.

Original comment by greg.sut...@gmail.com on 21 Jan 2014 at 7:55

[GoogleCodeExporter]

I've been using Shuffle with Tracks hosted at Heroku for 1.5 years. Yep, the 
synchronization is somewhat buggy but in general it either works fine or I have 
already figured out some sort of a workaround. For example, I always mark tasks 
as complete in Shuffle and only delete them in Tracks. I was even going to fix 
some issues, but while reading the code I was able to figure out a workaround

Original comment by maksim.a...@gmail.com on 21 Jan 2014 at 8:01

[GoogleCodeExporter]

according to source changelog, 
it still under development, 
just nobody release any new version.

Original comment by andcy...@gmail.com on 21 Jan 2014 at 8:06

[GoogleCodeExporter]

I may be mistaken, but it was looking that the developer is going to drop 
Tracks support in the next version in favor of Shuffle Server hosted in Google 
App Engine.

Original comment by maksim.a...@gmail.com on 21 Jan 2014 at 8:14

[GoogleCodeExporter]

o~k,
anyway, I already take http://www.toodledo.com/ as replacement years ago,
there is no free lunch.

Original comment by andcy...@gmail.com on 21 Jan 2014 at 8:20

[GoogleCodeExporter]

I would be very happy to go with Shuffle Android client + Shuffle GAE server, 
but I can't get the latter to work. I opened the issue #325 but it's still 
unanswered...
http://code.google.com/p/android-shuffle/issues/detail?id=325

Original comment by noimelem...@gmail.com on 21 Jan 2014 at 8:25

[GoogleCodeExporter]

I love shuffle, it is a great app! I'm having similar synchronisation issues 
and would love to see this issue being solved.

Original comment by alex.kla...@gmx.de on 24 Feb 2014 at 11:09