logoutRedirect() gives --> "Error - Attempted to clear all MSAL cache items and failed. Local cache unchanged."

Core Library

MSAL.js v2 (@azure/msal-browser)

Core Library Version

2.22.0

Wrapper Library

MSAL Angular (@azure/msal-angular)

Wrapper Library Version

2.1.1

Description

Everything seems to be working fine, but when you do msalService.logoutRedirect() you will get an error (in Chrome browser console + preserve logs): “Error - Attempted to clear all MSAL cache items and failed. Local cache unchanged.”.

After some research I managed to find out the there it at least a “not a function” exception in CryptoOps.ts when doing databaseStorage.deleteDatabase():

Error Message

1. Error - Attempted to clear all MSAL cache items and failed. Local cache unchanged.
2. databaseStorage.deleteDatabase is not a function

Msal Logs

No response

MSAL Configuration

auth: {
      clientId: <myappid>,
      authority: `https://login.microsoftonline.com/${<mytenantid>}`,
      redirectUri: '<myredirecturl>',
      postLogoutRedirectUri: '<mylogouturl>',
      navigateToLoginRequestUrl: false
    },
    cache: {
      cacheLocation: BrowserCacheLocation.LocalStorage,
      storeAuthStateInCookie: false,
    },
    system: {
      loggerOptions: {
          logLevel: LogLevel.Error,
          loggerCallback: (level, message) => {
              console.log(level, message);
          },
          piiLoggingEnabled: false
      }
    }

Relevant Code Snippets

msalService.logoutRedirect();

Reproduction Steps

1. Open Chrome developer tools
2. Open console
3. Toggle “preserve logs”
4. msalService.LoginRedirect();
5. msalService.logoutRedirect();
6. See the console output for error.

Expected Behavior

1. databaseStorage.deleteDatabase() should not cause “is not a function”
2. logoutRedirect() should not cause an error message

Identity Provider

Azure AD / MSA

Browsers Affected (Select all that apply)

Chrome

Regression

No response

Source

External (Customer)

[pkanher617]

@mettoware We were able to reproduce this and hope to have a PR up to fix this shortly - thanks for bringing this to our attention!

[msftbot[bot]]

🎉This issue was addressed in #4617, which has now been successfully released as @azure/msal-browser@v2.23.0.🎉

Handy links:

• Release Notes
• Official NPM Release