Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid: Sending multiple files as attachments in Email
    primarykey
    data
    text
    <blockquote> <p><strong>Possible Duplicate:</strong><br> <a href="https://stackoverflow.com/questions/2264622/android-multiple-email-attachments-using-intent">Android multiple email attachments using Intent</a> </p> </blockquote> <p>I already know there are may similar questions as I got my current code from one of the answer. But I am facing some problem and initially I think it is of gmail app but then I tried with other email client and same issue. <strong>Code:--</strong></p> <pre><code>ArrayList&lt;Uri&gt; uris = null; try { uris = logger.getSiteFilePaths(siteIndex); } catch (BaseLoggerException e) { // TODO Auto-generated catch block e.printStackTrace(); } Intent emailIntent = new Intent(android.content.Intent.ACTION_SEND_MULTIPLE); emailIntent.setType("application/octet-stream"); emailIntent.addFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION); emailIntent.putExtra(Intent.EXTRA_EMAIL,""); emailIntent.putExtra(Intent.EXTRA_SUBJECT, "Bl\u00fc-Test Log"); emailIntent.putExtra(Intent.EXTRA_TEXT, "Please find the attachments."); emailIntent.putParcelableArrayListExtra(Intent.EXTRA_STREAM, uris); startActivity(Intent.createChooser(emailIntent, "Email:")); </code></pre> <p>File paths are accurate </p> <pre><code>**e.g. --** file:///storage/sdcard0/BAPISandy_test1.csv </code></pre> <p>Issue:- In Gmail app files seems to be attached but when you send email it says "Couldn't show attachemnt" in notification bar. If tried with other email client it doesn't show files as attachment. <strong>System Info:--</strong> Samsung Galaxy Tab 2 (7 inch) Android 4.1.1</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload