SorokitProvider error state clobbered in Promise.all and not cleared on reconnect or disconnect

[k-deejah]

Problem

src/context/SorokitProvider.tsx manages a single error state that is overwritten by multiple async operations. In the account-loading effect (lines 52–58), getAccount and getBalances run in Promise.all and both attempt to set the same error state:

if (accountRes.error) setError(accountRes.error);
if (balancesRes.error) setError(balancesRes.error);

If both fail, the second setError silently overwrites the first. Only one error is ever visible at a time.

A second problem: error is never cleared when address changes. If wallet A caused a balance-fetch error, that error string persists in the banner while wallet B's data is loading — the user sees a stale error that no longer applies.

A third problem: disconnectWallet (line 75) clears address, account, and balances but does not clear error or reset network. A stale error from a previous session remains visible after disconnect.

Solution

Reset error to null at the start of the address-change effect, before any fetches run. Collect both errors from the Promise.all and combine them:

useEffect(() => {
  setError(null); // clear stale error first
  if (!address) { setAccount(null); setBalances([]); return; }
  // ...
  .then(([a, b]) => {
    const combined = [a.error, b.error].filter(Boolean).join('; ');
    if (combined) setError(combined);
  });
}, [address, client]);

Also add setError(null) inside disconnectWallet.

Acceptance Criteria

• Connecting a new wallet clears any error from the previous session before fetching
• When both getAccount and getBalances fail, the message includes both error strings
• When only one fails, the correct single error is shown
• disconnectWallet clears the error state
• The error banner in TopBar.tsx does not show stale errors after wallet switch

---

Note for Contributors: If you're assigned to this issue, write a clear and detailed description for your pull request. Explain what was changed, why it was needed, how it was implemented, and include any relevant testing or screenshots where applicable.

[ChukwuebukaJohnDev]

@ChukwuebukaJohnDev has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I would love to work on this issue, Please assign it to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ChukwuebukaJohnDev to this issue.

[buki70]

@buki70 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer,
I’d really appreciate the opportunity to work on this issue. Having reviewed the acceptance criteria, I’m confident that I can submit a PR after being assigned.
Please kindly assign this issue to me.
Thank you!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @buki70 to this issue.

[flexocode442]

@flexocode442 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Maintainer, I'd like to work on this issue. I have experience with blockchain development and state management, and I can implement this. Please consider assigning it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @flexocode442 to this issue.

[Olamidepy]

@Olamidepy has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Kindly asssign me to this thanks

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Olamidepy to this issue.

[DevSolex]

@DevSolex has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer,

I’m a smart contract and full-stack developer and would love to contribute to this issue. I’m an experienced contributor with hands-on expertise in Rust, Soroban, Cairo, and TypeScript.

I’m passionate about building secure, scalable blockchain solutions, with a strong emphasis on writing clean and maintainable code. Based on the scope of this issue, I’m confident I can deliver a complete solution within 24 hours of assignment.

I’d greatly appreciate the opportunity to contribute and help move this forward.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DevSolex to this issue.

[drips-wave]

Congratulations, @Olamidepy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Olamidepy: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊