Apple has just released DEVONthink To Go 1.4.3 to the App Store. The maintenance update makes the app display RTF documents again on iOS 8. Also, it brings new iOS-8-like visual style and fixes other minor glitches.
We still continue working hard on DEVONthink To Go 2. With sharing and action extensions in iOS 8 Apple makes it for the first time possible to easily share data between apps. Of course we’ve already begun to write an extension for adding texts and documents from other apps to DEVONthink To Go.
hi, very excited about v2:-)
This version does not work with Yosemite, does it?
No, DEVONthink To Go v2 will not work with Yosemite, as it’ll be an iOS app, not a Mac app 🙂
This looks like Textmate 2, the never ending story
You almost need to call it something else as this is soooooo depressing. There is no excitement when it should have happened many moons ago.
And.. it broke my syncing.
I have Devonthink Pro and the mobile app. I just can’t get them to sync – ever!
What steps should I be taking to do this it just isn’t obvious and is very frustrating
@Steve: The update itself did not even touch syncing. But it changes the signature of the app and this could be maltreated by the OS and the router as some sort of malicious behavior. Does a restart of the iOS device, the router, and your Mac help?
@Jon: Could you please explain a bit further what exactly doesn’t work and where it stops? Blog comments are not really useful for in-depth support so please contact us directly.
You say you are still working on DevonThink To Go v2. When are we going to get an update on it?
Well syncing with the iPad still works for me , But the “open in” and “Clip to” functions on the iPad cause DTPTG to crash when it tries to open the database. Tried closing DTPTG, turning off the device, and a hard reset on the device but the only thing I found that corrects the issue is deleting DTPTG and reinstalling on the device. The app will then open and sync, but the crashing after “open in” and “Clip to” functions is repeatable.
Any ideas??
@ JB: It seems there’s a bug somewhere that we didn’t find before submitting the code to Apple. It does not crash on our devices but we’re already trying to find out where this happens. Sorry for the inconveniences.