# Android: shared attachments use the full Content-Type header as intent type, so apps don't appear in the share sheet

**URL:** <https://forum.emclient.com/t/android-shared-attachments-use-the-full-content-type-header-as-intent-type-so-apps-dont-appear-in-the-share-sheet/120599>\
**Category:** Mobile apps\
**Created:** [November 12, 2026, 10:25am UTC](https://forum.emclient.com/t/android-shared-attachments-use-the-full-content-type-header-as-intent-type-so-apps-dont-appear-in-the-share-sheet/120599 "2026-11-12T10:25:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![hterhofte](https://forum.emclient.com/letter_avatar_proxy/v4/letter/h/b5e925/32.png) [@hterhofte](https://forum.emclient.com/u/hterhofte)\
**Post date:** [November 12, 2026, 10:25am UTC](https://forum.emclient.com/t/android-shared-attachments-use-the-full-content-type-header-as-intent-type-so-apps-dont-appear-in-the-share-sheet/120599/1 "2026-11-12T10:25:01Z")

</div>

When I share a PDF attachment from eM Client for Android (Share → another app), the intent type is set to the complete MIME header including parameters, for example:

type=application/pdf; name=invoice.pdf

instead of the bare MIME type application/pdf. Android matches intent types literally, so apps that register for application/pdf (PDF readers, invoice/payment apps, etc.) don’t show up in the share sheet. Sharing the same file from the Files app works fine, because that passes type=application/pdf.

Intent as captured with Intent Intercept:  
intent:#Intent;action=android.intent.action.SEND;type=application/pdf%3B%20name%3D.pdf;…;end

Expected: pass only the MIME type (without “; name=…”) as the intent type; the file name is already available through the content URI.

eM Client for Android version: 11.0.1393 (1256637)  
Android version: 16