Intent.ACTION_SEND targeting API Level 24+

Question

I get android.os.StrictMode.onFileUriExposed exception when trying to send a file with a Intent. It's my understanding that this is because I'm targeting 24> and file:// is not supported anymore, content:// should be used.

First I would like to say that I have seen similar questions like this, this and i'v also seen this blog post.

But the problem is, all of the post refer to URI when taking a picture, in my case the file is saved successfully using Uri and now I want to send the image using Intent like below:

shareBtn.setOnClickListener(new View.OnClickListener() {
        @Override
        public void onClick(View v) {
            Intent sharingIntent = new Intent(Intent.ACTION_SEND);
            Uri screenshotUri = Uri.parse("file://" + directoryToStore + "/" + filename);
            //the Uri above  - file:///storage/emulated/0/Android/data/myPackageName/files/SavedImages/test.jpeg
            sharingIntent.setType("image/jpeg");
            sharingIntent.putExtra(Intent.EXTRA_STREAM, screenshotUri);
            startActivity(Intent.createChooser(sharingIntent, "Share image using"));
        }
    });

By doing the above I only get a crash on some devices running 19>. Testing on my Samsung J7Pro (Android 7.0 API 24) I don't get a crash.

I have seen that some of that answers say that I can use:

StrictMode.VmPolicy.Builder builder = new StrictMode.VmPolicy.Builder();
StrictMode.setVmPolicy(builder.build());

But it's not the preferred way.

So, my question is. How should I handle sending files when targeting 24>. Should I do a if/else statement checking the version like if (Build.VERSION.SDK_INT >= 19) { and then use normal Uri for devices running <24 and how should I change file:// to content://? I also don't understand why the crash only happens on some devices.

---

EDIT 1:

I have done what the answer below suggested but the file is not passed with the intent, instead I get a Toast saying Unable to attach file when I try to email the image.

Answer 1

The proper way to share files from your app is a content provider, specifically FileProvider.

Add your FileProvider to AnroidManifest.xml:

<provider
    android:name="android.support.v4.content.FileProvider"
    android:authorities="${applicationId}.MyFileProvider"
    android:exported="false"
    android:grantUriPermissions="true" >
    <meta-data
        android:name="android.support.FILE_PROVIDER_PATHS"
        android:resource="@xml/shared_paths"/>
</provider>

Next, add the referenced resource, by adding an xml resource (Android Studio: right click on 'app' -> New -> Folder -> XML Resources fodler) Then, inside this new folder create an xml file named shared_paths.xml (should match value in AndroidManifest.xml). Contents for shared_paths.xml:

<?xml version="1.0" encoding="utf-8"?>
<paths xmlns:android="http://schemas.android.com/apk/res/android">
    <external-path name="SavedImages" path="SavedImages/"/>
</paths>

EDIT: changed element type from <files-path ../> to <external-path .. /> per documentation. IMPORTANT: Change the path attribute to fit your needs.

Lastly change you code like this:

shareBtn.setOnClickListener(new View.OnClickListener() {
        @Override
        public void onClick(View v) {
            Intent sharingIntent = new Intent(Intent.ACTION_SEND);
            Uri screenshotUri = FileProvider.getUriForFile(context, context.getPackageName() + ".MyFileProvider", new File(directoryToStore, filename))
            //the Uri above  - file:///storage/emulated/0/Android/data/myPackageName/files/SavedImages/test.jpeg
            sharingIntent.setType("image/jpeg");
            sharingIntent.putExtra(Intent.EXTRA_STREAM, screenshotUri);
            sharingIntent.addFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION);
            Intent chooserIntent = Intent.createChooser(sharingIntent, "Share image using");
            chooserIntent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
            startActivity(chooserIntent);
        }
    });

Answer 2

If you save your file in a public media folder in internal memory (i.e. for images /storage/emulated/0/DCIM/my.package.name/SavedImages/myImage.jpg) you can also share the file via it-s content-media uri (for image content://media/external/images/media/4711).

This way you do not need your own FileProvider but the file is available for all.

With a lcoal FileProvider in apps' private data directories the file is only available throug your app and will be deleted if you uninstall your app.

the purpose of a contentprovider is that you can read content from any uri as inputStream (i.e. form "uri= "https://stackoverflow.com/questions/...", "file:///storage/emulated/0/...", "ftp:....", "content:...") as long as there is a provider for this.

with api 25 Google enforces that "file:..." uri-s are not allowed any more