fix(cross-chain-accounts): add error handling for blob fetching in AccountBlobs

[Baophan00]

Summary

The AccountBlobs component had no error handling for the getAccountBlobs API call. If the API failed, the promise rejection was unhandled and the user saw no feedback — just an empty state. This adds proper try/catch, loading state, and cleanup on unmount.

Closes shelby/feedback#45

Problem

In apps/cross-chain-accounts/components/AccountBlobs.tsx:

• The useEffect had an async function that returned a value but was called with .then() — if the API rejected, it became an unhandled promise rejection.
• No loading state — user didn't know if data was loading or empty.
• No error state — API failures silently showed "No blobs found".
• No cleanup on unmount — potential state update after component unmounts.

Solution

• Convert the inner async function to use try/catch and set error state explicitly.
• Add isLoading state for UI feedback during fetch.
• Add cleanup function (cancelled flag) to prevent state updates after unmount.
• Update render to show loading and error states with appropriate messages.

Files changed

• apps/cross-chain-accounts/components/AccountBlobs.tsx — 39 additions, 10 deletions

Test plan

• Simulate API failure (e.g., invalid API key) → error message shown
• Successful fetch → blobs displayed normally
• Switch account while fetching → old fetch doesn't set state
• Normal loading → "Loading blobs..." shown

🤖 Generated with Hermes Agent (Nous Research)

---

Note

Low Risk
Localized UI and async lifecycle changes in one component; no auth, payments, or shared API contract changes.

Overview
AccountBlobs now handles blob list fetches with explicit loading, error, and empty UI instead of treating failures like “no blobs.”

The useEffect fetch uses try/catch/finally, sets isLoading/error, clears error when the wallet disconnects, and uses a cancelled cleanup so in-flight requests don’t update state after unmount or account/refreshTrigger changes. Successful loads still populate the existing blob grid unchanged.

^{Reviewed by Cursor Bugbot for commit 6399d11. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

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

^{Reviewed by Cursor Bugbot for commit 6399d11. Configure here.}

[cursor]

Empty state flashes before loading

Low Severity

isLoading starts as false and is left unchanged when account is missing, so the first paint after a wallet connect has no loading flag, no error, and empty blobs. The empty-state copy is shown until useEffect later sets isLoading. With autoConnect this flicker happens on page load and again on every reconnect.

Additional Locations (1)

• apps/cross-chain-accounts/components/AccountBlobs.tsx#L80-L86

 

^{Reviewed by Cursor Bugbot for commit 6399d11. Configure here.}