Abe-Froman

With 2 releases since this issue was last touched, including a major, I wonder if things have changed. @TomPallister can you comment which may address also #1328?

@gouttierre @ling1726 @ecraig12345 for visibility

@iclanton I have one member of our dev team who is hitting this exact same issue but the workaround @ipip2005 mentioned isn't working for us. ``` Rush Multi-Project Build Tool...

We actually got this resolved by deleting the package-lock.json that was in the root of the repo. Maybe this information will help someone else down the road.

We're having the same issue, let's call it on Application A, using 0.4.24. Another of our applications, Application B, is using 0.4.18 and does not have this issue. I haven't...

Neither downgrading to 0.4.18 nor upgrading to 0.5.0 resolved this issue for me. =(

I've solved it for our case. The solution was to provide a `redirectUri` value in adalConfig which points to the root of our application. For example: ``` export const adalConfig:...

Strangely I started hitting this tonight. Worked from the office today, everything was fine right up through my final commit/push. I came home, pulled, and hit this running under VS....

Likely same as #4581 We're seeing the same issue. Has anyone figured out a fix for this?