ClaimableBalanceCard silently discards claimBalance errors and never removes claimed rows

[k-deejah]

Problem

src/components/ClaimableBalanceCard.tsx BalanceRow.handleClaim handles the result of claimBalance with:

const { error } = await getClient().account.claimBalance(cb.id);
if (!error) setClaimed(true);

The else branch is entirely missing. When claimBalance returns an error string the button simply re-enables and nothing happens — users receive zero feedback. Additionally, if the API returns { data: null, error: null } (valid per the SorokitClient type), setClaimed(true) fires with no real ledger confirmation.

Two more related problems: (1) after a successful claim the row stays visible with a "Claimed" badge but is never removed from the list, leaving the count badge in the header stale; (2) there is no loading guard preventing a second Claim click while the first is in-flight.

Solution

Add a local claimError state to BalanceRow and display it inline on failure. Verify data is non-null before setting claimed. Lift a removal callback from the parent so the claimed row is removed after success. Disable the Claim button while claiming is true.

Acceptance Criteria

• A failed claimBalance call shows an inline error message below the Claim button
• claimed is only set to true when data is non-null
• Successfully claimed row is removed from the visible list
• The header count badge updates to reflect remaining claimable balances
• The Claim button is disabled while a claim is in-flight
• Claiming one row does not affect other rows in the list

---

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.

[OLAMIGHTY010]

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

I would like to work on this project

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

[kaizercodes]

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

Hi, I can fix this
kindly assign

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

[sadiquhammedabubakar-art]

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

Hi maintainer, I’d like to work on this issue and help implement a proper solution.

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

[chiemezie1]

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

I have reviewed this issue and understand the requirements.

I'd be happy to work on it. Please assign it to me.

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

[tesleem-28]

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

Hello, I reviewed the issue in detail and understand the scope and expected outcome. I have a practical implementation strategy and would be glad to take this issue from implementation to testing.

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

[emmxy]

@emmxy 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

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

[dollfins]

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

Hello maintainer, i would love to fix this issue kindly assign it to me Thanks

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

[anifast-123]

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

Hello maintainer, i would like to work on this issue

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

[Trovic1]

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

Please assign

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

[VeronicDev]

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

Hi, I can fix this pls assign

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

[payfoxX]

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

I love to fix this issue, kindly assign it to me. Thanks

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

[axeroofficialtournament-del]

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

Hello Maintainer, I have gone through this issue documentation and i am interesting and would love to be assigned this particular issue.

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