fix(ios): prevent duplicate cancel callbacks in image picker

[kosmydel]

I don't have a repro; this is a bit of a guess at a fix for the Sentry issue

• Sentry issue: https://discord.sentry.io/issues/7518688525/events/829fb20ae3c74e97ba3284deee3bc8e5/?project=230973
• moves patch changes to the fork (introduced in https://github.com/discord/discord-archive-2024/pull/183085)
• upstream issue (not solved): [🐛] Callback arg cannot be called more than once > KLWR iOS Crash react-native-image-picker/react-native-image-picker#2390
• the solution taken from: [🐛] Callback arg cannot be called more than once > KLWR iOS Crash react-native-image-picker/react-native-image-picker#2390 (comment)

AI-driven repro scenario when it could happen:

The race requires the async photo load to still be in-flight when the dismiss fires — it won't happen on fast local photos.

1. Use an iCloud photo that is not downloaded locally (look for the cloud icon in Photos).
2. Enable New Architecture (NOBRIDGE mode).
3. Open the image picker, tap the iCloud photo to select it, then immediately swipe down before the download completes.
4. Without the patch: the dispatch_group_notify block fires after presentationControllerDidDismiss: has already consumed the callback → crash.
5. With the patch: presentationControllerDidDismiss: sets photoSelected = YES; the notify block early-returns → no crash.

[Copilot]

Pull request overview

This PR updates the iOS implementation of react-native-image-picker to prevent duplicate “cancel” callbacks (and the resulting crash) when the picker is dismissed while async photo loading is still in-flight.

Changes:

• Introduces a photoSelected flag to ensure the callback is only consumed once per picker session.
• Adds early-return guards in imagePickerControllerDidCancel: and presentationControllerDidDismiss: to avoid duplicate cancel emissions.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.