Proof

expo-share-intent

real upstream package — not intercepted. useShareIntent, ShareIntentProvider, useShareIntentContext and utils run from the bundle against the ExpoShareIntentModule native module (native-seams/expo-share-intent.ts, ported from the 4.1.2 Swift and Kotlin): sync hasShareIntent/clearShareIntent, async getShareIntent, and onChange/onError/onStateChange with upstream payloads, error strings and the single-file files-array quirk. apps with no share see exactly what upstream reports: no events, hasShareIntent false, and the no-plugin AppGroupIdentifier onError through reset

70%

API coverage

No visual proof cases have been published for this package yet. The registry summary below describes what the compat layer implements.

Working (9)

module presencegetShareIntent/hasShareIntent/clearShareIntent shape and sync/async contractiOS dataUrl store read per fragment with empty and invalid-type pathsno-plugin AppGroupIdentifier-nil onErrorAndroid singleton drain and OnNewIntent live path with text/file ACTION_SEND payloadstask-root launchreset lifecyclehook/provider/context initial stategetScheme/getShareExtensionKey/parseShareIntent utils

Missing (2)

no share extension or ACTION_SEND writer exists in Peachso no payload can arrive and onChange with a payload is implemented but unverified live; photo-library identifiers never resolve (entries drop as upstream drops unresolvable assets); content-resolver metadata errors are unreachable