Skip to content

fix(EMBED-478): handle linked account lookup failures - #2539

Open
arch1995 wants to merge 1 commit into
masterfrom
fix/EMBED-478-handle-linked-account-fetch-failure
Open

fix(EMBED-478): handle linked account lookup failures#2539
arch1995 wants to merge 1 commit into
masterfrom
fix/EMBED-478-handle-linked-account-fetch-failure

Conversation

@arch1995

@arch1995 arch1995 commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Jira Link

EMBED-478

Description

getUserInfo loads the authentication profile and linked accounts together.
An error from the optional linked-account request currently rejects the full
user information request.

This change catches linked-account request errors, writes a warning, and
returns an empty linked-account list. The authentication profile remains
available to the caller.

Related backend change:
Web3Auth/citadel-server#91

How has this been tested?

  • Ran npm run lint.
  • Ran npm run build.
  • Ran the complete browser test suite with npm test.
  • Ran 261 no-modal tests in Chromium, Firefox, and WebKit.

Screenshots (if appropriate)

Not applicable.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

  • My code follows the code style of this project. (run lint)
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Note

Low Risk
Narrow error-handling change in an optional data path; worst case is silently empty linked accounts when Citadel is down, which matches the intended degradation.

Overview
getLinkedAccounts now wraps the Citadel /v1/user request in try/catch. On failure it logs a warning and returns [] instead of throwing.

Because getUserInfo loads the auth profile and linked accounts in parallel, this stops optional linked-account errors from rejecting the full user info call—the core auth profile still reaches callers, with no linked accounts until Citadel succeeds again.

Reviewed by Cursor Bugbot for commit 7eaf774. Bugbot is set up for automated code reviews on this repo. Configure here.

Co-authored-by: Cursor <cursoragent@cursor.com>
@arch1995
arch1995 requested a review from a team as a code owner September 4, 2026 09:26
@vercel

vercel Bot commented Sep 4, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
web3auth-web Ready Ready Preview Sep 4, 2026 9:32am UTC

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant