[ Proof ]
expo-share-intent
real upstream package — not intercepted. on iOS Peach compiles the package own ExpoShareIntentModule.swift and a share arrives through `peach defaults write` plus `peach open <scheme>://dataUrl=<key>#<type>`; the Android seam below answers Android only. 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 reset70%
API coverageWorking (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 (3)
Android has no ACTION_SEND writer (Android native intake is paused)so an Android payload cannot arrive; iOS media shares need the share extension target Peach does not buildso file shares resolve only for paths the app container holds; photo-library identifiers never resolve (entries drop as upstream drops unresolvable assets); content-resolver metadata errors are unreachable