Android ACTION_GET_CONTENT from Dropbox sources

Hi, thanks for useful Dropbox.

I have same problem.
So, does the future version of Dropbox support `content://` URI?
I hope that Dropbox returns `content://` URI that works fine without `READ_EXTERNAL_STORAGE` permission such as sharing files by `FileProvider`. I really hope so.
I don't want that the my apps require more permission that make users feel uneasy.
And then, I think that more users use Dropbox as the place to save files of more apps. Because since Kitkat many apps use `FileProvider` and they don't read/write the file  by oneself.

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?

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.

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 report! I'm sending this along to the right people.

Any update on this? I've run into the same issue.

Apologies, no update right now. I'll check in with the right people again.

Has this been fixed recently? I did not run in to permission issues using the following code to initiate download...

Intent intent = new Intent(Intent.ACTION_GET_CONTENT);

intent.setType("*/*");

startActivityForResult(intent, PICKFILE_RESULT_CODE );    

The uri returned in onActivityResult was this:

file:///storage/emulated/0/Android/data/com.dropbox.android/files/scratch/Kanji%20Sketch%20Pad/KanjiKnowledge.ks

Processing the data in onActivityResult required a bit of a workaround for Dropbox, which I'll mention in a separate thread, but my app read the file okay. Does the issue only appear under certain circumstances?

I should add, I am using Android 5.0.2, device is HTCOne,

Still no news on potentially using content:// instead yet, but I'll ask engineering if something changed about the existing behavior/any guidance.