[@capacitor/share] Android: sharing several images with text to WhatsApp only sends the text (intent type forced to */*)
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 78/100
Direzione di ricerca
Start at the SharePlugin.shareFiles entry point and inspect how MIME types and ACTION_SEND_MULTIPLE intents are built. Reproduce the issue with several JPEG URIs and text, then verify that WhatsApp receives every image and the text while mixed or unknown types retain the documented fallback behavior.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Bug Report
Plugin(s)
@capacitor/share 8.0.2
Capacitor Version
Latest Dependencies:
@capacitor/cli: 8.5.2
@capacitor/core: 8.5.2
@capacitor/android: 8.5.2
@capacitor/ios: 8.5.2
Installed Dependencies:
@capacitor/ios: not installed
@capacitor/cli: 8.5.2
@capacitor/core: 8.5.2
@capacitor/android: 8.5.2
Platform(s)
Android
Current Behavior
Sharing several image files together with a text to WhatsApp only delivers the text: WhatsApp drops all the images. Sharing a single image with the same text works.
In SharePlugin.shareFiles, the intent type is forced to */* as soon as more than one file is shared, even when every file has a known MIME type:
String type = getMimeType(file);
if (type == null || filesList.size() > 1) {
type = "*/*";
}
intent.setType(type);
With three JPEG files, the ACTION_SEND_MULTIPLE intent is sent as */*, and WhatsApp treats it as a text-only share.
We confirmed it on a physical Android phone. Our logs showed the three files written to the cache and passed to Share.share, the plugin resolving with activityType: com.whatsapp, and still only the text reaching the conversation.
Expected Behavior
The intent should carry the common MIME type of the shared files, as Chrome's Web Share does: image/jpeg when all files are JPEG, image/* when they are mixed image types, and */* only when the types differ or are unknown. WhatsApp then receives all the images with the text.
Code Reproduction
import { Directory, Filesystem } from '@capacitor/filesystem'
import { Share } from '@capacitor/share'
// three small JPEGs written to the cache
const uris = []
for (const name of ['a.jpg', 'b.jpg', 'c.jpg']) {
const { uri } = await Filesystem.writeFile({ path: `share/${name}`, data: JPEG_BASE64, directory: Directory.Cache, recursive: true })
uris.push(uri)
}
await Share.share({ text: 'Three photos', files: uris })
// choose WhatsApp → only "Three photos" is sent
// with files: [uris[0]] → the photo and the text are sent
Other Technical Details
The following change fixes it for us. We apply it with patch-package, and three images plus the text now reach WhatsApp:
- String type = getMimeType(file);
- if (type == null || filesList.size() > 1) {
- type = "*/*";
- }
- intent.setType(type);
+ String type = getMimeType(file);
+ if (type == null) {
+ sharedType = "*/*";
+ } else if (sharedType == null) {
+ sharedType = type;
+ } else if (!sharedType.equals(type)) {
+ boolean bothImages = sharedType.startsWith("image/") && type.startsWith("image/");
+ sharedType = bothImages ? "image/*" : "*/*";
+ }
+ intent.setType(sharedType);
(sharedType is a String declared as null before the loop.)
We also set a ClipData covering every URI for ACTION_SEND_MULTIPLE, since the plugin currently only does it for a single file. That was not enough on its own: the MIME type was the deciding factor.
if (fileUris.size() > 1) {
ClipData clipData = ClipData.newRawUri("", fileUris.get(0));
for (int i = 1; i < fileUris.size(); i++) {
clipData.addItem(new ClipData.Item(fileUris.get(i)));
}
intent.setClipData(clipData);
intent.putParcelableArrayListExtra(Intent.EXTRA_STREAM, fileUris);
}
Related: #2474 (unknown extensions also fall back to */*, which WhatsApp likewise discards).
- Lingua principale
- Java
- Stelle
- 685
- Fork
- 691
- Merge medio
- 16h 33m
- PR unite (30g)
- 1
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di ionic-team/capacitor-plugins
-
triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
ionic-team/capacitor-plugins#2616 ·
-
[@capacitor/app] iOS: 'Expression implicitly coerced from String? to Any' warning in getAppLanguageApertatriage
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
ionic-team/capacitor-plugins#2604 ·
-
triage
Difficoltà 3/5 1-2 giorni Idoneità per principianti 66/100
ionic-team/capacitor-plugins#2615 ·
-
triage
Difficoltà 3/5 1-2 giorni Idoneità per principianti 58/100
ionic-team/capacitor-plugins#2614 ·
-
platform: android platform: ios
Difficoltà 4/5 3-5 giorni Idoneità per principianti 52/100
ionic-team/capacitor-plugins#2613 ·
Tutte le issue di ionic-team/capacitor-plugins
Issue simili
-
ToolCallbackProvider AutoConfiguration does not preserve tool orderForse già presa Una pull request collegata a questa issue è aperta o già unita. Apertastatus: waiting-for-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 79/100
spring-projects/spring-ai#7206 ·
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
eclipse-dirigible/dirigible#7958 ·
I maintainer di solito rispondono entro 1 giorno
-
bug ci sev-6
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
-
area/cli
Difficoltà 2/5 Mezza giornata Idoneità per principianti 78/100
quarkusio/quarkus#57623 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
jhipster/prettier-java#1113 ·
I maintainer di solito rispondono entro 2 giorni