Share Screenshot is failing/hanging in Android Play Store production builds for some users

[Ashutosh-Tiwari]

Issue

Share Screenshot is failing/hanging in Android Play Store production builds for some users.

Observed Behavior

• On tapping Share, the Android share sheet does not open immediately.
• In affected cases, it opens after ~1 minute.
• Initially a blank/empty filename is shown, then later the correct filename appears.
• When selecting WhatsApp, it keeps loading and sometimes sends a blank message / blank attachment.
• On some devices, Android shows behavior similar to intent resolver not responding.
• • In debug / Firebase App Distribution builds, screenshot share works as expected.

Current Implementation

• React Native
• react-native-view-shot used for screenshot capture via captureRef
• react-native-share used for opening the Android share sheet
• Screenshot captured as PNG
• Filename generated using uuidv5

Current Flow

1. User taps Share
2. App captures screenshot using captureRef
3. Returned file path is passed to react-native-share
4. Android share sheet is opened

Why This Seems Production-Specific

• Works in debug builds
• Fails in Play Store production build
• Suggests stricter Android app-to-app file sharing behavior, release timing optimization, or resolver differences in prod

Impact

• Users are unable to share screenshot reliably
• Share CTA appears broken or delayed
• Poor UX in production for receipt/screenshot sharing

JS Changes Already Considered / Tried

• capture as PNG
• add delay before capture
• prevent double tap
• normalize file path
• pass MIME type image/png
• verify temp file exists before sharing

These JS-only fixes may reduce timing issues but may not fully solve the production Android resolver/share problem.

Can anyone help me on this issue?

[gre]

@Ashutosh-Tiwari
Hello,
First time I hear this issue but as the scope of this library is the screenshot part, and that your bug seems to be around "Android share sheet does not open immediately", I am not sure why it relates to react-native-view-shot.
Did you reported it to react-native-share too? Is there more crash log around the issue that you found to help seeing where it fails?