[CRITICAL ISSUE] Deep Linking Opens “Register Username” Modal in WebView (RC 7.10.0)
We are running a self-hosted Rocket.Chat Community Edition v7.10.0 and are integrating an external application using deep linking via resumeToken in an Android WebView.
We are facing a critical issue where the authenticated user is unable to access the chat room because they are repeatedly shown the “Register username” modal upon login, preventing them from seeing the deep-linked room.
Problem Details:
- User Creation Flow: We create the user programmatically using the
/api/v1/users.createendpoint.- The
usernamewe provide is simple (e.g.,guest1).
- The
- Login Flow: Immediately after user creation, we call
/api/v1/loginor/api/v1/users.createTokento generate a freshresumeToken. - Deep Link URL: We load the following URL in the WebView:
http://[server-address]/direct/[ROOM_ID]?layout=embedded&resumeToken=[TOKEN]
Observed Behavior (The Failure):
- The
resumeTokensuccessfully authenticates the user, confirming the token is active. - Instead of being directed to the DM room, the user is stuck on the “Register username” modal (as shown in the attached image).
- The modal suggests a variant username like
guest1-0.
Our Analysis:
It appears the user’s account is being created in a state that requires final username confirmation via the UI, even though a username was provided during the /api/v1/users.create call.
Questions for Support:
- What should be my actions to not get Register Username modal , as this is harmful for seamless user flow?
- What specific parameter must be included in the
/api/v1/users.createcall to fully provision a user and bypass the “Register username” modal when logging in viaresumeToken? (if needed) - Are there specific account settings (e.g., in Admin → Accounts) that need to be disabled to prevent this initial username confirmation step for API-created users in v7.10.0?
- Is this a known bug in v7.10.0 related to programmatic user creation?
Thank you for your assistance in resolving this integration blocker.

