Fix contacts permission prompt timing

[j0ntz]

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

• Yes
• No

Dependencies

none

Requirements

If you have made any visual changes to the GUI. Make sure you have:

• Tested on iOS device
• Tested on Android device
• Tested on small-screen device (iPod Touch)
• Tested on large-screen device (tablet)

Description

Asana task

Remove contacts modal on first receive. The contacts permission prompt no longer appears from passive thumbnail lookup when a user receives funds. It now appears only when the user opens a transaction list with named transactions or explicitly edits the payee field from transaction details.

---

Note

Low Risk
Low risk: changes are isolated to UI permission-prompt timing and removes a side-effect from a thumbnail hook, with no sensitive data handling beyond existing permission requests.

Overview
Adjusts when the contacts permission modal is shown so it no longer triggers during passive contact thumbnail lookup (e.g. first receive).

Centralizes the “show modal + request OS permission” behavior into a new promptForContactsPermission thunk, calls it from ContactListModal, and adds a guard in TransactionListScene to only prompt when there are named transactions.

Simplifies useContactThumbnail to be a pure lookup over existing contacts state (no permission checks/modals), and updates the changelog entry to reflect the new prompt timing.

^{Written by Cursor Bugbot for commit 43bea65. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[samholmes]

I think this makes sense. But I think a short review-bar is all that's needed.

[samholmes]

I don't understand this commit much. Why were the type deprecated. I guess maybe a little sidebar?

[j0ntz]

RN navigation 7 will no longer allow NavigationBase and requires typed navigators only, that's why it was deprecated in the first place. We need to prepare for the transition eventually so we must do it incrementally.

On second thought, though, this commit might not be a valid workaround. We might just need to actually fix everything such that we lift navigator props out of all components using NavigationBase

[samholmes]

Approved if we drop first commit because it's not certain if it's useful