[Bug] useWallet's connect() has no catch, silently swallowing rejected wallet calls

[collinsezedike]

Description

useWallet's connect() has no catch, only a finally. If anything it awaits (connectWallet(), or the getAddress/getNetwork calls inside it) ever rejects rather than resolving to an error-state object, the rejection is unhandled: connecting resets, but the user gets no feedback at all, and the error only surfaces as a silent unhandled-promise-rejection in the console.

Steps to reproduce

1. Open the demo app with Freighter installed and unlocked.
2. Simulate a rejected promise somewhere in the connect() chain (e.g. temporarily throw inside resolveConnectedState() in src/lib/wallet.ts, or trigger a genuine Freighter extension messaging failure by disabling/reloading the extension mid-call).
3. Click "Connect wallet".

Expected behavior

The UI shows some indication that the connection attempt failed (a toast, an inline message, anything), matching the error-surfacing pattern already used elsewhere in the app (e.g. MilestoneRow.tsx's run() wrapper, which catches and surfaces contract-call errors).

Actual behavior

connecting flips back to false (via finally), but wallet state never updates and no error is shown. The failure is invisible to the user; only a console error (if any) hints at what happened.

Environment

• Network: testnet
• Contract: n/a (this is demo-app-only, demos/freelance-escrow)
• Commit or tag: main

Possible impact

No fund-safety or contract-state impact; this is a demo-app UX bug (silent failure on wallet connect), not a security issue.

[wadexybiodun]

Hi admin, could please kindly assign this task to me. Thank you.

[grantfox-oss]

🦊 GrantFox — @wadexybiodun has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #94)
2. Your PR will be reviewed by the drydocs maintainers

Good luck! Track your progress on GrantFox.

[collinsezedike]

Hey @wadexybiodun, checking in, no rush. Just want to make sure you have what you need on this one. Let me know if you're stuck or have questions.

[collinsezedike]

Hey @wadexybiodun, second check-in, still no rush. Just want to make sure nothing's blocking you. Let me know if you're stuck or have questions.

[collinsezedike]

Hey @wadexybiodun, this is a second check-in with still no update. If there's no progress or word back within the next few days, I'll have to unassign this one and open it up to someone else. Let me know where things stand.

[collinsezedike]

Unassigning @wadexybiodun due to no response after two check-ins. Opening this back up for anyone who'd like to take it.

[Santia2004]

Hi @collinszedike, I'd like to take this one! Please assign it to me.