[Bug] OAuth error response rendered as raw JSON in UI — exposes internal API error codes to users

[RUKAYAT-CODER]

Overview

During login, src/hooks/useAuth.tsx passes the raw axios error response body to UI error state. For OAuth token exchange failures, the backend returns JSON like {"error":"invalid_grant","error_description":"Token expired"}. This raw JSON string is rendered directly in the UI label, exposing technical OAuth codes and internal API error descriptions to users.

Specifications

Features:

• Auth error messages mapped to user-friendly strings in src/utils/authErrorMessages.ts
• invalid_grant maps to message about expired session
• access_denied maps to credentials error message
• Raw error details logged to appLogger.error, never shown in UI

Tasks:

• Create src/utils/authErrorMessages.ts mapping OAuth error codes to user messages
• In useAuth.tsx error handler, parse error.response?.data?.error and look up user message
• Fall back to generic message for unknown codes
• Log raw response to appLogger.error
• Add unit tests for each mapped error code

Impacted Files:

• src/hooks/useAuth.tsx
• src/utils/authErrorMessages.ts (create)

Acceptance Criteria

• User never sees raw JSON or OAuth error codes in UI
• Common OAuth error codes mapped to friendly messages
• Unknown codes produce generic fallback message
• Full error details still appear in appLogger.error for debugging

[Hollujay]

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

I would like to apply for this issue because I can get it done.

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

[temisan0x]

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

Hey team, I'd like to take on this issue. I've gone through the requirements and understand the changes needed. I can start working on it right away if that's okay.

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

[drips-wave]

Congratulations, @temisan0x! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

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