[android][contacts] Fixed back to back presentFormAsync attempt issue

[erenilufer]

Why

Closes #28951

How

After the first trigger of presentFormAsync, contactManipulationPromise doesn't get back to its initial state which is null. Managed it using startActivityForResult. Only occurs in Android.

Test Plan

It also can be observed and reproducible in apps/bare-expo. Tested in apps/bare-expo in Android 14.

Checklist

• Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
• Conforms with the Documentation Writing Style Guide
• This diff will work correctly for npx expo prebuild & EAS Build (eg: updated a module plugin).

[expo-bot]

Hi there! 👋 I'm a bot whose goal is to ensure your contributions meet our guidelines.

I've found some issues in your pull request that should be addressed (click on them for more details) 👇

⚠️ Suggestion: Missing changelog entries

Your changes should be noted in the changelog. Read Updating Changelogs guide and consider adding an appropriate entry to the following changelogs:

• packages/expo-contacts/CHANGELOG.md

---

Generated by ExpoBot 🤖 against e921b67

[jp1987]

I applied this as a patch, it fixes the issue (partly), but the behaviour is different from iOS. On Android, the presentFormAsync promise resolves immediately on opening of the screen, while on iOS the promise resolves once the screen closes.

[jp1987]

@erenilufer @EvanBacon I don't mean to be rude and hijack this PR, but this feature is pretty critical for our app, I believe this is the fix: jp1987#1

now presentFormAsync waits for the result like on iOS and no more unhandled rejections.

[erenilufer]

hello @jp1987 . Sorry for late reply, I didn't have a chance to look into it. Just tested your fix and it looks fine. Solves immediate promise resolve issue. You can go with a new pr or we can add your patch here it's up to you. It's completely okay. Thanks for the fix

[jp1987]

hello @jp1987 . Sorry for late reply, I didn't have a chance to look into it. Just tested your fix and it looks fine. Solves immediate promise resolve issue. You can go with a new pr or we can add your patch here it's up to you. It's completely okay. Thanks for the fix

Great, thanks for testing! Opened up a PR here: #29201