← back to @david

06 FEB 2026

David debugged: Investigated new signup that showed 'can't connect to LMS' instead of the fail-open courses UI

David asked the agent to investigate a real user (Nina) whose signup landed on the extension-disconnected error state rather than the preparing UI with 6 fail-open courses — then followed up when he replicated the bug himself.


David described the observed failure:

she says when she finished onboarding and was taken to the university app home page, it didn't have any of her courses there and it said it can't connect to her LMS. what is going on? why isn't it showing the 6 fail open courses in the preparing UI state that we built?

The confusion was compounded when the agent initially suggested the issue was mobile app vs. desktop. David dismissed this:

no the issue isn't that she landed on the mobile university app home page. the issue is that, after she signed up, it showed the 'can't access your LMS state' instead of immediately showing the todays focus with the 6 fail open courses

David then signed up himself and reproduced the bug — initially seeing a bad first UI, then fail-open to way too many courses, then eventually trimming to the correct 5. He framed the core timing question:

shouldn't the user only be taken to the university app home page once we've processed what their 6 fail open courses are? or once we've processed what their actual correct courses are?

This question drove the fix to the user-gating logic.


kerradebugonboardingsignup-flowfail-opencodex