Please support the open folder intent

[contrapunctus-1]

Applications like Syncthing require it to open folders.
See also syncthing/syncthing-android#838

[k3b]

goal:

• Intent to open filemanager and view content of a specified directory in the filemanager.
• This feature should not be a picker

my proposal: use this: https://stackoverflow.com/questions/17165972/android-how-to-open-a-specific-folder-via-intent-and-show-its-content-in-a-file
it already works with "EF File Explorer"

• action=android.intent.action.VIEW
• data=file:///path/to/directory/
• mime=resource/folder

---

[Update 2017-10-09] fixed typo in data. need data=file:///path/to/directory/ instead of data=file:/path/to/directory/

[tibbi]

picker and viewer are 2 different things, I will get there someday

[k3b]

thanks a lot

[k3b]

works great in k3b/APhotoManager#99 . thanks a lot

[iNPUTmice]

Can you also support getting the file path from org.openintents.extra.ABSOLUTE_PATH as described here: http://www.openintents.org/action/android-intent-action-view/file-directory. Modern Androids (API 24+) do not allow file uris to be transmitted in the data field of an intent. (FileUriExposedException). Should be a 2 line fix. I’m happy to contribute that fix myself if you don’t have any principle objections to handling it that way.

[tibbi]

sorry but no, that intent is a custom one belonging to a specific app, not a widely used one

[iNPUTmice]

Hi, I think we can agree that opening a file manager with a specific folder (to view the content of said folder) is a worthwhile goal and a good feature to have, right? That's why this issue was resolved in the first place. However that commit no longer works if the calling application targets API 24. An app targeting api 24 can not but file:// uris into the data of an intent. That why my proposal was to put the desired file path into an EXTRA field instead. If you prefer that I'm happy to call that field 'prg.simplemobiletool.filemanager.extra.path' or what ever. However openintents is not a vendor specific thing but an attempt to *standardized* those exact intent that are not covered by basic android.

[tibbi]

I will check someday how should it be handled, for now I dont want to add custom intent handling

[k3b]

@iNPUTmice

that intent is a custom one belonging to a specific app

I donot like app specific tags, too but at least it is documented which is much more than most other custom tags.

I will add it to my apps as last fallback-try if nothing else works.

---

Maybe we should create a simple android lib at github and publish at jcenter/mavencentrals for the task "open directory folder" with client-app and service-app code.

then @tibbi can add something linke this to Simple-File-Manager:

 String folderToBeopend = FileIntentApi.getOpenInDirectory(this.getIntent());
 if (folderToBeopend  != null) ... do open in directory code ..... 

[humpity]

ShareCompat (support.v4) uses setStream(uri) which is really an Intent.ACTION_SEND with a putExtra(Intent.EXTRA_STREAM, uri).