Skip to content

fix: support 2026-09 userInfo.firebase API response format - #1

Open
klh wants to merge 1 commit into
ehmo:mainfrom
klh:fix/auth-user-id-parsing
Open

fix: support 2026-09 userInfo.firebase API response format#1
klh wants to merge 1 commit into
ehmo:mainfrom
klh:fix/auth-user-id-parsing

Conversation

@klh

@klh klh commented Sep 4, 2026

Copy link
Copy Markdown

The /api/firebase-login response changed from authUser.{id,profile.user_id} to userInfo.firebase.id. ParseAuthUser now parses both formats, resolving user ID, email, plan type, and abilities from whichever is present. Error messages include body previews for debugging.

Verified against a live Pro account response: userInfo.firebase.id contains the MJ UUID, userInfo.firebase.idpID contains the Firebase UID.

The /api/firebase-login response changed from authUser.{id,profile.user_id}
to userInfo.firebase.id. ParseAuthUser now parses BOTH formats side by side,
resolving the user ID, email, display name, plan type, and abilities from
whichever structure is present. Error messages include a body preview.

Verified against a live response: userInfo.firebase.id contains the MJ UUID,
userInfo.firebase.idpID contains the Firebase UID.

Co-Authored-By: Claude Code <noreply@anthropic.com>
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.

2 participants