java.io.IOException: write failed: EPIPE (Broken pipe)

I get the following error trying to share a file from the assets folder:

E/TransferOutThread: Exception transferring file
E/TransferOutThread: java.io.IOException: write failed: EPIPE (Broken pipe)
E/TransferOutThread:     at libcore.io.IoBridge.write(IoBridge.java:542)
E/TransferOutThread:     at java.io.FileOutputStream.write(FileOutputStream.java:186)
E/TransferOutThread:     at com.commonsware.cwac.provider.AbstractPipeStrategy$TransferOutThread.run(AbstractPipeStrategy.java:96)
E/TransferOutThread:  Caused by: android.system.ErrnoException: write failed: EPIPE (Broken pipe)
E/TransferOutThread:     at libcore.io.Posix.writeBytes(Native Method)
E/TransferOutThread:     at libcore.io.Posix.write(Posix.java:258)
E/TransferOutThread:     at libcore.io.BlockGuardOs.write(BlockGuardOs.java:313)
E/TransferOutThread:     at libcore.io.IoBridge.write(IoBridge.java:537)
E/TransferOutThread:     at java.io.FileOutputStream.write(FileOutputStream.java:186) 
E/TransferOutThread:     at com.commonsware.cwac.provider.AbstractPipeStrategy$TransferOutThread.run(AbstractPipeStrategy.java:96) 

The file exists, I’ve tried sending a non-existent file and the error was a FileNotFoundException. I think I’m creating the Intent and everything correctly, but I paste it here anyway:

Intent share = new Intent(Intent.ACTION_SEND);
share.setType("audio/*");
share.putExtra(Intent.EXTRA_STREAM, PROVIDER.buildUpon().appendPath(soundName + ".mp3").build());
share.addFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION);
startActivity(Intent.createChooser(share, "Share audio"));

I’m using the last version of cwac-provider, with Android sdkVersion 23

[jjoseba]

I’ve isolated the problem to the simplest code. It’s just an Activity that launches the sharing intent in its onStart() method. I’ve uploaded the complete project here: https://drive.google.com/file/d/0ByCtNqXoOZUEaTNDU3M0V3JRMmc/view?usp=sharing

[commonsguy]

With regards to Telegram, as I don’t use it, I don’t have a great way of testing it specifically. You might try a test with a file:/// with the same content; it’s possible that Telegram is fine with the Uri but just doesn’t like the content for some reason. If you come up with fresh evidence, or a way for me to test this that doesn’t involve me signing up for Telegram, file a fresh issue.

With respect to the docs, I just pushed a fix – thanks for pointing that out!