Closed izikl closed 1 year ago
@izikl Thanks for opening this issue. How many users are currently impacted by this error? Can you try to reproduce this error with the latest version of msal-browser?
Only 4 users were affected, but those 4 users were hitting it hundreds of times.
Can you try to reproduce this error with the latest version of msal-browser?
~I am blocked from upgrading due to this bug: https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/5340~
We will deploy 2.30.0 next Wednesday, so I will reply to your comment about the deployment a week after our deployment (to allow enough telemetry to be collected) on Nov 9th, 2022.
This issue requires attention from the MSAL.js team and has not seen activity in 5 days. @bmahall please follow up.
This issue requires attention from the MSAL.js team and has not seen activity in 5 days. @bmahall please follow up.
This isn't due to a long state value but rather localStorage or sessionStorage is already full when MSAL attempts to add a new value. You'll need to clear space in browser storage when this happens and probably do some investigation into why your app is reaching the storage quota
@izikl This issue has been automatically marked as stale because it is marked as requiring author feedback but has not had any activity for 5 days. If your issue has been resolved please let us know by closing the issue. If your issue has not been resolved please leave a comment to keep this open. It will be closed automatically in 7 days if it remains stale.
Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.19.0
Wrapper Library
Not Applicable
Wrapper Library Version
None
Public or Confidential Client?
Public
Description
We have got some users getting error:
This is the traces, we are seeing in the app:
So looks like sometime
setRequestState
is called with a state long enough that it exceeds the localStorage limits.Error Message
Error: Failed to execute 'setItem' on 'Storage': Setting the value of 'msal.f9818e52-50bd-463e-8932-a1650bd3fad2.request.state.ce0f222d-22f1-45ca-a3ad-bdef428e3abb' exceeded the quota. at e.setItem (https://dataexplorer.azure.com/static/js/main.deb8eff0.js:2:72074) at t.setTemporaryCache (https://dataexplorer.azure.com/static/js/main.deb8eff0.js:2:83609) at t.updateCacheEntries (https://dataexplorer.azure.com/static/js/main.deb8eff0.js:2:86836) at t.initializeAuthorizationRequest (https://dataexplorer.azure.com/static/js/main.deb8eff0.js:2:146724) at t. (https://dataexplorer.azure.com/static/js/main.deb8eff0.js:2:171676)
at https://dataexplorer.azure.com/static/js/main.deb8eff0.js:2:2804
at Object.next (https://dataexplorer.azure.com/static/js/main.deb8eff0.js:2:2909)
at https://dataexplorer.azure.com/static/js/main.deb8eff0.js:2:1845
at new Promise ()
at a (https://dataexplorer.azure.com/static/js/main.deb8eff0.js:2:1590)
Msal Logs
No response
MSAL Configuration
Relevant Code Snippets
Reproduction Steps
There are no clear repro steps since it happens in production to our users, and we can't repro it locally.
Expected Behavior
Don't throw. A long state value should not cause an exception.
Identity Provider
Azure AD / MSA
Browsers Affected (Select all that apply)
Chrome, Edge
Regression
No response
Source
Internal (Microsoft)