[Bug]: First-time Google sign-up on Linux gets stuck on "Not Found" after successful authentication

[Lakshit-Gupta]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

1. Install the latest T3 Code AppImage on Linux.
2. Launch the application.
3. Click "Continue with Google".
4. Complete Google authentication in the browser.
5. Return to the desktop app.

Observed behavior:

• The application navigates to:

  t3code://app/CLERK-ROUTER/VIRTUAL/sign-up

• The UI renders a "Not Found" page.

• The application never redirects into the main app.

Additional observations:

• The Google OAuth flow succeeds.
• The Clerk user is created successfully.
• The application remains stuck on the virtual sign-up route.

Expected behavior

After a successful Google sign-up, the application should:

1. Complete the Clerk sign-up flow.
2. Redirect away from the Clerk virtual sign-up route.
3. Open the main T3 Code interface automatically.

Actual behavior

After Google authentication:

• The application navigates to:

  t3code://app/CLERK-ROUTER/VIRTUAL/sign-up

• The page displays "Not Found".

• The user cannot continue through the UI.

However, the user is actually authenticated.

Manually navigating to:

t3code://app/

immediately opens the application normally.

Impact

Blocks work completely

Version or commit

T3 Code AppImage 0.0.30

Environment

OS: POP OS UBUNTU BASED Linux Desktop: COSMIC Display Server: Wayland Browser: Brave Package: AppImage

Logs or stack traces

No application crash.

The application successfully authenticates with Clerk but remains on:

t3code://app/CLERK-ROUTER/VIRTUAL/sign-up

instead of redirecting to the main application.
During debugging I noticed that the Clerk sign-up object initially reported:

- status: missing_requirements
- missingFields: ["legal_accepted"]

After updating the sign-up with:


await window.Clerk.client.signUp.update({
  legalAccepted: true
})


the sign-up completed successfully and a session/user was created.

The remaining issue appears to be that the desktop app never redirects away from:

t3code://app/CLERK-ROUTER/VIRTUAL/sign-up

even though authentication has completed.

Screenshots, recordings, or supporting files

No response

Workaround

After completing Google sign-in, manually navigating to the application root allows the app to open normally.

Steps:

1. Open the browser and enter:

   t3code://app/

or, from the DevTools console:

window.location.href = "t3code://app/"

After manually navigating to the root route, the application loads and works normally.

[SebastienGllmt]

I get the same issue on Windows + WSL2 on 0.32-nightly.20260730.953 as well
Even using Github login instead of Google

If I try and login again after the first failure, I hit #4815 (even though the fix to the issue should be part of this release, so maybe it missed a case)

[maximilionai]

Same issue on Macos 26.5.1 and t3 code version 0.0.32-nightly.20260731.961

[VeiaG]

Same issue on windows
0.0.32

After sign up with github.

Before i was able to sign up , i was getting this issue #5239

[t3-code]

Closing as fixed by #5770: the Clerk sign-up redirect failure is fixed.