Android ACTION_GET_CONTENT from Dropbox sources

I don't have an update on the Dropbox for Android app potentially returning content:// links for ACTION_GET_CONTENT in the future, but I'll be sure to pass this along as feedback.

Same issue. My app does NOT has READ_EXTERNAL_STORAGE permission. I'm using ACTION_GET_CONTENT intent to pick file from any app that can handle it. The Dropbox returns URI starting with 'file://' and my app can not read file since there is no permission. Other apps (including Google Drive) returns URI starting with 'content://' and my app can read it without any issue. As a result, users of my app can not use Dropbox to pick file. It forces them to use different app. I think you better fix it to stop loosing users. Why you still don't have any plans regarding the issue?

Thanks for the additional feedback Evgeny! I can't speak to why or why not particular changes are or aren't implemented, but we appreciate everyone taking the time to write, and I'm sending this along to the team.

Hello, Gregory. Thank you for your reply.
I have one more question.
When the Dropbox supports `content://` URI, can we get that notification?
e.g. a comment at here, your blog or a page such as the release-note.
(It seems that the update information in the Google Play page does not include the information about development.)

We need that notification because we will have to update our apps at that time.

I'll be happy to update this thread if/when I have any news on this.

Thank you! :D

Hi Gregory,

I imagine the team is already aware of this, but in Android Marshmallow the READ_EXTERNAL_STORAGE permission is classified as "dangerous" and requires for the developer to request, and the user to grant, permission at runtime. As you can imagine, the experience is rather strange for a user:

1. User opens Dropbox
2. User clicks file
3. User chooses my app
4. My app launches and asks to access the SD card

The context isn't there for a user as to why my app suddenly needs to get access to the SD card.

One thing I noticed, is that using the export functionality in the Dropbox app does not require the READ_EXTERNAL_STORAGE permission, so I assume this does share a content:// uri.

Thanks for the feedback Marius!

Hi Gregory,

Is there any update on this issue? Users of my app are unable to upload files from Dropbox at the moment, while other services like Google Drive working fine. The only way for me to fix this is to add a permission prompt to my app specifically for Dropbox.

One of the great benefits of using the file picker in Android Marshmallow is that you can share files safely between apps without having to grant permissions that would allow apps to have access to more files than are necessary. It would be great if Dropbox returned a URI using the content:// scheme so that users don't have to deal with unnecessary permission prompts.

Thanks!

Thanks for the feedback Josh. I don't have an update on this unfortunately, but I'll send along your feedback as well.