fix(login): Resolve dashboard connection delay with robust loading state - #246
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Root Cause Analysis
Users have frequently experienced a 1 to 2 minute UI 'freeze' when clicking the Continue to Dashboard button on the Login page if an active session is detected. This happens because the backend API (/api/users/me) can experience Serverless cold starts or network latency, taking up to 2 minutes to respond on free tiers. The frontend \handleContinue\ function lacked any visual feedback during this asynchronous wait, leading to a degraded UX where the app appeared unresponsive.
Proposed Changes
This PR systematically addresses the lack of UI feedback by breaking down the solution into three distinct commits:
Verification
Note: The underlying cold-start issue itself is being mitigated at the infrastructure level via UptimeRobot pings to the backend API base URL.