G’day @eboehnisch. Search listed you as founder, are you aware of these issues on DT To Go3? 2 similar issues were reported 4.5 months ago + 1.5 weeks ago. No urgency to resolve these issues. Team has been working on release 4 but I am very surprised there’s no urgency to fix these 2 critical issues. I can replicate 2 issues following steps listed.
1 Like
As noted in the second thread, these issues are resolved (and confirmed as resolved) in DEVONthink To Go 4. In addition, version 4’s internal support for versioning provides some relief from potential issues (though again, the issue isn’t happening in 4).
Also on bandwagon of non-sub apps, rely on DT3 DTToGo3 till they die.
This stance does not mean version 3 will continue on as long as you wish. Development has limited time and resources and prioritizes according to its capabilities and needs.
Do you mean that at some point, DT3 will stop functioning on my Mac, and DTTG3 will stop functioning on my iPhone?
Or maybe you mean that support for DT3 and DTTG3 will stop at some point, but the apps will continue to function?
As long as an update of macOS or new hardware won’t break it.
Both apps are in maintenance and yes, development will end at some point. Support will too eventually but in most cases, that’s my call. I still field support tickets about DEVONthink 2.x on rare occasion and even handled a DEVONnote ticket in the past six months. However, there are no implications or promises of fixes from development regarding out of development apps.
2 Likes
Thanks both for clarifying.
@eboehnisch @cgrunenberg bugs were introduced 4.5 months ago by release 3.8.11 that wasn’t there before. That’s months before release of DT To Go4. It’s a bug acknowledged by your team 4.5 months ago based on thread above. User losing his or her data in other thread. I reckon there should be urgency to fix bugs introduced by DT, not forcing us to pay yearly subscription for DT To Go4 to not have that bug.
Mate it’s 1 thing to put out big statement about DT business principles, then users copped with some raw decisions having to put up with bugs intro by DT 4.5 months ago. It’s not right.
1 Like
Our days, as for many people, have only 24 hours. The bug you are referring to is noted and will be fixed on our own schedule that takes all priorities into account, the release of major releases and everything that goes with it included. If the fix was for a bug reported a while ago and can be applied to the previous generation we might publish a maintenance release. We won’t, however, support older generations with bug fixes and adjustments to environment changes (like system upgrades) forever.
2 Likes
Eric thanks for replying. Of cause don’t expect DT to enhance for system upgrades nor intro new features for DT To Go3. Bugs were intro in DT To Go3 update 4.5 months ago therefore expectation is that developers should fix that rather that someone above replying bug not in 4, that’s condescending. Will stop posting and look forward to speedy fix. Enjoy your weekend.
For what it’s worth (I’m butting in because no one else has), I do not agree that the second thread you posted is a bug. OP did a day’s work, didn’t check that a sync was complete, and then did edits to a file that post-dated the original edits in a file that hadn’t synced. They didn’t have sync conflict duplicates enabled and didn’t have a back-up. That is all human error, not a bug.
If you make edits on a file that post-date earlier edits you’ve done, they are saved. That is how all auto-save functions work. Not checking that earlier edits had synced properly first is generally an error you only make once in my experience, and not having sync conflict duplicates enabled is like driving without a seatbelt. You can do it, but at some point you’re going to have a collision and physics will take over 
6 Likes
Respectfully you should test and see. IT IS a bug. Won’t be so worried if didn’t happen to me couple of times. Couldn’t figure out why and had same thought about sync might not be completed. Saw OP’s report on second thread and search here and also found first thread with same bug.
Can replicate BUGS reported. Try it yourself following steps listed in those threads. Bug is because file on DT To Go3 doesn’t refresh if file “Doc123.md” currently highlighted on DT To Go3 is the same file “Doc123.md” that was updated on DT desktop prior to sync. If you don’t select another file on DT To Go3 after sync completed you will notice “Doc123.md” has not been updated. You must select another file on DT To Go3 for “Doc123.md” to be updated on DT To Go3. Current selected file on DT To Go3 won’t update unless you select another file. Bug is on DT To Go3 not updating current selected file when that file has been updated on DT desktop. “Doc123.md” will only update on DT To Go3 if you select another file or shutdown DT To Go3 and restart. After sync walk to another room to continue working DT To Go3 “Doc123.md” will overwrite all your work on DT desktop “Doc123.md” on your next sync. I do that often working on iPad on living room or garden for a change in work environment. No error no duplicate files on your next sync. DT To Go3 “Doc123.md” will overwrite DT “Doc123.md”. Bug is there try it yourself. Had work disappeared and couldn’t figure out why till saw reports from those 2 threads. Bug has been there for 4.5 months.
I get people jumping in and defending DT on this discourse though you should first test steps listed in both threads. It is a serious bug and losing work is not fun. Worries me a lot. Have to remind self to select another file on DT To Go3 every time after a sync. Please try it yourself and you will see the bug.
1 Like
I am the person who reported refresh bug mths ago before DTTG4 came out. Have moved on to to other app. Still have some old data sitting on DTTG v3. Agree that is it strange non refresh not addressed so far 
I investigated the issue today. It happens when you, e.g., …
- Open a PDF on your iPad in editing mode
- Change the same PDF on your Mac
- And sync
On the iPad, the changes coming in from the Mac are saved but the document you are currently editing is not reloaded with the changes. This is, actually, intentional so that you don’t lose your local changes. As we are dealing with a variety of documents formats of which not all would support granular merging of changes on both sides — something which would require rather sophisticated mechanism of which even Git only implements one, for plain text — we chose the “whoever saves later, wins”.
Technically, editing a document prevents it from being force-updated from an external source such as sync.
1 Like
Apologies for not being clear with my explanation. It is a markdown file not PDF. Working in project management & heavily use monthly markdown files. Every month solely work on 1 markdown file linking images | slip note | PDF to it. Was very easy to spot problem on DTTG 3.8.11 because did not see ‘flashing’ after completed sync. DTTG did a ‘flash’ refreshing that month’s markdown file every completed sync. Updating DTTG file of work I did on Mac. Initiate sync from DTTG because Mac is setup for incoming connections. DTTG always flashed refreshing files before 3.8.11. Made it easy to spot something was wrong from 3.8.11 onwards. Selected markdown file only refreshes after switching to another month’s file on DTTG. Did not have problem before 3.8.11.
This is the same for Markdown. While you’re editing it, it is never overwritten by external changes as otherwise whatever you’d be typing in that same moment would be lost.
DT & DTT3 are not in edit mode. Typical process markdown file DecemberJournal
- FYI sync is setup for local network.
- sync DT & DTTG making sure both updated every morning.
- usually work & read in our WFH/study room during day. Including updating monthly personal journal DecemberJournal on DT Mac Studio.
- evening preference is to spend time with others in family room.
- sync DT & DTTG before joining others in family room. Both in preview mode. Not edit or source mode.
- because I do bulk of writing on 1 monthly journal. Therefore DecemberJournal usually currently selected file on both DT & DTTG. Both in preview mode before sync.
- sync always initiated on DTTG. DTTG used to ‘flash’ prior to 3.8.11 - refreshes file updating changes done on DT. Noticed DTTG does not refresh file from 3.8.11 thereafter.
- shut down Studio before going to family room.
- DecemberJournal on DTTG reveals changes on Studio DT not updated on DTTG. DTTG DecemberJournal will only update after tap on another journal on DTTG and back to DecemberJournal. DTTG DecemberJournal finally shows changes made on DT. Prior to 3.8.11 auto refreshed file after sync not having to select another journal & going back to current.
Bluefrog confirmed twice - ‘I have reproduced an issue’ & ‘the issue isn’t happening in 4’.
Do you have 3.8.10 to examine process above? You will see the difference. 3.8.11 introduced bug.
1 Like
@BLUEFROG Have you opened an issue for this including step-by-step instructions on how to produce the behavior as well as what the expected behavior is? Thanks.
2 Likes
I am filing one now.
Issue filed.
2 Likes