Upgrade to latest msal/browser library breaks this sample

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Upgrade current sample to latest version of msal-browser npm install @azure/msal-browser @azure/msal-angular@latest

Click Login In Button and log in - F12 and look at console window - it has an error when trying to get the claims.

Any log messages given by the failure

core.js:6210 ERROR ClientAuthError: access_token_entity_null: Access token entity is null, please check logs and cache to ensure a valid access token is present. at ClientAuthError.AuthError [as constructor] (http://localhost:4200/vendor.js:130540:20) at new ClientAuthError (http://localhost:4200/vendor.js:130792:24) at Function.ClientAuthError.createAccessTokenEntityNullError (http://localhost:4200/vendor.js:131129:12) at Function.<anonymous> (http://localhost:4200/vendor.js:135387:35) at step (http://localhost:4200/vendor.js:130119:19) at Object.next (http://localhost:4200/vendor.js:130049:14) at http://localhost:4200/vendor.js:130021:67 at new ZoneAwarePromise (http://localhost:4200/polyfills.js:2387:23) at __awaiter$1 (http://localhost:4200/vendor.js:130000:10) at Function.ResponseHandler.generateAuthenticationResult (http://localhost:4200/vendor.js:135349:12)

Expected/desired behavior

Shows table with claims detail in the home.component.html file

Browser and version?

Google Chrome Version 90.0.4430.93

Versions

This is in the project - “ms-identity-javascript-angular-tutorial/1-Authentication/2-sign-in-b2c/”

Mention any other details that might be useful

---

Thanks! We’ll be in touch soon.

[profteck]

Thanks a mill. Your samples really do help me to understand the concepts.

[derisen]

@profteck thanks for catching this! Will get this fixed in PR asap.