Invalid state. ''bad, state expected : null. in msal Angular

-
When you are using MSAL in angular app you encounter this error "Invalid state. ''bad, state expected : null" while calling "getCachedTokenInternal" method. 

Typescript shows pass string in intelligence and if you are now aware about state then you will pass blank string like "" but it gives above error. 

Solution

Pass the state as "null" as below.

var token = super.getCachedTokenInternal(scopes, this.getAccount(), null);

For more refer git error explanation - Invalid state Expected: null


Thanks



Comments

Post a Comment

Popular posts from this blog

The serve command requires to be run in an Angular project, but a project definition could not be found - Fixed

-
Error -  The serve command requires to be run in an Angular project, but a project definition could not be found Root Cause - When there is no project definition file in your project then you will see this error when you will run ng-serve or ng-build commands. Project definition file - In Angular project definition file is generated when you create new application or upgrade existing application. In Angular versions lesser than 6 this file name is .angulat-cli.json  and in Angular version 6 and above it's name is angular.json . Solution -   So while running the angular build or run commands make sure you have correct project definition file. If you are upgrading your application from Angular 5 or lesser versions to Angular 6 and greater versions then you need to run below command to generate new project definition and other related files. ng update @angular/cli   // run it twice, If it's not generating then again try to run below commands in same sequence....
Read more

Azure - Failed to deploy web package to App Service. Internal Server Error (CODE: 500)- Fixed

-
Image
Error:  Failed to deploy web package to App Service. Internal Server Error (CODE: 500) Explanation: I was getting this error when trying to deploy azure functions with release pipeline. I got this and there was no additional information logs with this. I wasted my one day on this issue. Find Error: You can see the actual error by changing  deploy method for  web deploy   by editing your pipeline. My Root Cause:  "Web Deploy detected insufficient space on disk." So this was the issue for me, it may be because of my subscription.  For different persons root cause might be vary but you can see actual error using this deploy method and can apply your fixes accordingly. Thanks!!!
Read more

Your global Angular CLI version (8.3.3) is greater than your local version (1.6.5). The local Angular CLI version is used.

-
Warning -  Your global Angular CLI version (8.3.3) is greater than your local version (1.6.5). The local Angular CLI version is used. Explanation - When you run an angular application and you have different versions of Angular CLI installed globally and in local project then you can see this warning or error. Solution - There are 3 things here. Either you can continue with this warning You can install matching version of angular CLI to global in local project by using below command.           npm install @angular/cli@version         3. Install Latest version of Angular CLI globally and in project as well.          To install latest angular CLI globally use below command.           npm install -g @angular/cli          To install latest angular CLI in project use below command.           npm install @angular/cli Thanks
Read more