-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File content stale with Dropbox on Android #63
Comments
#12 is specific to iOS. The last time I looked at Dropbox on Android it did not support the storage access framework (SAF), meaning you couldn't open files "from Orgro"; you could only go to Dropbox and then "open in Orgro". This is evidenced by e.g. this long-ignored request that Dropbox support SAF. However now that I look again with the latest version of Dropbox (274.2.2) I see that they seem to have added support. In other words Dropbox now does appear as a source in the file picking intent: I have not seen this before, so I can't speak to the quality of Dropbox's support for SAF. As I understand it, Dropbox is responsible for making sure that files are up to date before handing them off to the requesting application. So if you are finding files to be stale then I think it's Dropbox's fault and there's really nothing I can do about it. |
In version 274.2.2 (obtained 2022-4-10) Dropbox now appears to support storage access framework amake/orgro#63 (comment)
I have been using https://github.com/orgzly/orgzly-android previously, which uses the same file picker. It too won't automatically detect changes to a file, but has a "Sync" button within the app itself to request a file to be refreshed. |
Orgzly embeds the Dropbox SDK, which gives it that capability. I don't use the Dropbox SDK because I already support the universal file access APIs on iOS and Android, and I don't think Dropbox merits such special treatment. |
I cannot find a way to update a file from Dropbox that has been updated since it was first opened. Saw #12 but still not clear how this is supposed to work.
The text was updated successfully, but these errors were encountered: