-
Notifications
You must be signed in to change notification settings - Fork 3.1k
fix: logout-inactivity route gets stuck on loading indicator when inactivity and isLoggedIn are true #14596
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
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
Contributor
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖
Largest pathsThese visualization shows top 20 largest paths in the bundle.Meta file: packages/next/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_shared.json, Out file: esbuild/exports/shared.js
Meta file: packages/richtext-lexical/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_shared.json, Out file: esbuild/exports/shared_optimized/index.js
DetailsNext to the size is how much the size has increased or decreased compared with the base branch of this PR.
|
GermanJablo
approved these changes
Nov 14, 2025
Contributor
|
🚀 This is included in version v3.65.0 |
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.
What?
Updates logic within the
logout-inactivityroute to handle scenarios wheninactivityandisLoggedInare true, which can occur when the app is open in multiple tabs.Why
A client found that the
/logout-inactivityroute can get stuck on the loading indicator when you are running Payload in multiple tabs.For example:
/logout-inactivitylogout-inactivityroute is still present and now receivesinactivity: trueandisLoggedIn: truebecause you logged in using the other tab/logout-inactivityhandler and does not get redirectedHow
On the
/logout-inactivitywe have auseEffectthat checks ifisLoggedIn: true, if yes it calls the logout handlers, if false it redirects to the login screen.In this above example, it calls the logout handler. The logout handler immediately checks
!inactivityand skips the logic.This change moves the
inactivitycheck out of the logout handler and into the useEffect condition alongsideisLoggedIn.Now, if the user is both logged in and inactive, we skip the logout call and instead redirect straight to the login page, allowing that page to handle the redirect logic properly.