You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, even on the built-in checkout, if the user session becomes stale, and they come back to checkout, they are logged out on the site, but still appear "logged in" in checkout. This causes a problem as errors occur when trying to use saved payment methods and such, and just generic error occurs and displays to the user. We should have the ability to verify the session when loading checkout and clear it if it's stale and invalid. Ideally the Checkout SDK would just "lose" the signed in user when it loads checkout and determines it's stale.
The text was updated successfully, but these errors were encountered:
This is a known issue for us. At the moment we even allow finishing orders when the token expires. One of the engineers in Checkout team, @snaderiBC is currently working in verifying user session in order creation.
We will update this ticket when we have news around this issue.
Currently, even on the built-in checkout, if the user session becomes stale, and they come back to checkout, they are logged out on the site, but still appear "logged in" in checkout. This causes a problem as errors occur when trying to use saved payment methods and such, and just generic error occurs and displays to the user. We should have the ability to verify the session when loading checkout and clear it if it's stale and invalid. Ideally the Checkout SDK would just "lose" the signed in user when it loads checkout and determines it's stale.
The text was updated successfully, but these errors were encountered: