Testing Party

🔧 Admin Controls

Party Status

Quick Actions

View Applications Manage Bugs

Auto-Approve Settings

Auto-approve tester applications

When enabled, testers can join immediately without admin approval

Auto-approve bug submissions

When enabled, bug reports are automatically approved

📊 Testing Completion Status

Loading completion stats...

TP017

Tickets auth login - Hidden uncaught error in dev console

Closed

Summary

sso works but still some uncaught error in dev console flow

Overview

Priority: Medium

Summary

Brief one-sentence description of the testing party

Overview

https://tickets.gfavip.com

Here's how to capture it:

Clear your console (click the 🚫 icon in DevTools)
Reload the page and trigger the login flow again
Look for messages starting with 🚨 UNHANDLED PROMISE REJECTION: or 🚨 GLOBAL ERROR:
Click the arrow to expand the error object - it will show:
The exact error message
Stack trace with file names and line numbers
Full error details
This will tell us exactly what's throwing the error. Can you try that and share what the 🚨 error messages say? Even a screenshot of the expanded error object would help!

In the meantime, let me also check if there might be other sources of errors:

Determined API error handling behavior (6 seconds)
Ah! I found a potential issue. The error might be coming from responses that aren't 401. Let me check what status code the gems API is actually returning:

Opened client/src/lib/queryClient.ts

Decided on error handling approach
I see the issue! The on401: "returnNull" only handles 401 errors, but if the API returns 403 (Forbidden) or any other error, it still throws. Let me make it handle ALL errors gracefully:

Diagnosed error logging mechanism
Good! I've added handling for 403 errors too. Now with the global error handlers in place, we should get full details when the error occurs.

Please try this:

Fully reload the page (Ctrl+Shift+R or Cmd+Shift+R to clear cache)
Open DevTools Console and clear it
Trigger the login flow
Look for any message starting with 🚨 - that will have the full error details
The error handlers I added will now capture:

Full error message
Stack trace with exact file/line numbers
All error properties
This will tell us exactly what's throwing the error. Can you try that and let me know what the 🚨 messages show (if any)?

Also, I've now configured the app to gracefully handle both:

✅ 401 Unauthorized - returns null instead of throwing
✅ 403 Forbidden - returns null instead of throwing
This should prevent most auth-related errors from crashing.

Detailed instructions and context for testers

Optional Details

Priority

Bug Board Link

Testing Deadline

Live Call Date/Time

Live Call Instructions

Clarifications & Questions

Ask questions or get clarifications about this testing party

Loading clarifications...

Applications

Loading applications...

Bug Reports

No bugs submitted

No bug reports have been submitted yet.

🔧 Admin Controls

Party Status

Quick Actions

Auto-Approve Settings

📊 Testing Completion Status

Tickets auth login - Hidden uncaught error in dev console

Party Details

Summary

Overview

Optional Details

Clarifications & Questions

Applications

Bug Reports

No bugs submitted

Leaderboard

Submit Bug Report

✓ Mark Testing Complete

✓ Testing Complete