[Bug] `responseBody` used before declaration in `tipService.ts` causes ReferenceError on API errors

[RUKAYAT-CODER]

Overview

In src/services/tipService.ts around line 29, responseBody is referenced in the error-path branch before it is ever assigned. The variable holding the parsed JSON is stored under a different name, so when the API returns a non-2xx status the service throws ReferenceError: responseBody is not defined instead of a meaningful error message.

Specifications

Features:

• Tip failures surface a meaningful error message to the caller rather than crashing

Tasks:

• Replace responseBody.error with the correctly named variable (e.g. response.error after awaiting res.json())
• Add a null-safe fallback: typeof errorBody?.error === 'string' ? errorBody.error : 'Unable to send tip.'
• Write a unit test that mocks a non-OK API response and asserts the error message is returned cleanly

Impacted Files:

• src/services/tipService.ts

Acceptance Criteria

• No ReferenceError is thrown when the tips API returns a non-2xx response
• The caller receives the server error string or the fallback message
• Existing tip success tests continue to pass

[quickweb-stack]

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

This issue aligns well with my experience. I can work on it and submit a polished PR for review.

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

[pharwasz]

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

Hi, I would like to work on this issue

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

[drips-wave]

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

🧑‍💻 @pharwasz: 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 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@pharwasz's PR #1244 was approved and merged by @RUKAYAT-CODER.

🏆 @pharwasz: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (48 total points). Track your full progress on GrantFox.

👏 Great work, @pharwasz! Keep contributing to rinafcode.

[drips-wave]

This issue has been completed by @pharwasz as part of the Stellar Wave Program's 8th Wave 🥳

😎 @pharwasz: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.