Microsoft-authentication-library-for-js: IE 11 not Working with Angular MSAL Library

[arunprasathv]

I still see this issue with MSAL Angular library while launching the application in IE11 and console has below Error:

SCRIPT1002: Syntax error
vendor.js (148561,1)

class AuthenticationResult { constructor(token, tokenType) { this._token = ""; this._tokenType = ""; this._token = token; if (tokenType) { this._tokenType = tokenType; } } get token() { return this._token; } set token(value) { this._token = value; } get tokenType() { return this._tokenType; } set tokenType(value) { this._tokenType = value; } }

isn't the classes supposed to be transpiled to es5?

[sgentile]

I'm getting the same error, works fine in Chrome, but IE11 broken (this is Azure and it's broken for IE ?)

see more here: https://stackoverflow.com/questions/53196989/fixing-syntax-error-in-internet-explorer-11-angular-6-project

[arunprasathv]

Yes, i know this and i made it to work by recompiling to target es5 and it works in IE11 but the login popup goes in loop.

Refer : https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/414

[DarylThayil]

@jasonnutter when you get a chance can you look at this and see if we are not compiling down to the right target for ie11?

[jasonnutter]

I was able to reproduce this with the MSAL Angular sample, and the cause looks to be that the main export for msal-angular isn't the CommonJS version of the library. Fix coming shortly.

[jasonnutter]

Fix merged, I'll post here when it has been published. Thanks!

[arunprasathv]

@jasonnutter Thanks. This is great!! #414 closed?

[jasonnutter]

Version 0.1.3 of @azure/msal-angular has been published to npm with a fix for incompatibility with IE11.

If you have other issues with IE11 that do not get fixed with this version, please file a new issue, thanks!

[dotnetcanuck]

@jasonnutter Version 0.1.3, according to the npm registry page, has been deprecated...

msal-angular 0.1.3 has been deprecated due to incompatibility with aot compiler. Please revert to 0.1.2.

Does 0.1.4-beta.1 include this fix? And is there a timeline on when that version might come out of beta?

[jasonnutter]

@dotnetcanuck Yes, 0.1.4-beta.1 has a fix for IE11 compatibility. Please try that version and let us know if it fixes issues you are seeing with IE11. We will promote it to 0.1.4 soon, just waiting to hear back from a few customers confirming that it fixes their issues and doesn't introduce any regressions.

[aleksandar-kandzhichki]

@jasonnutter The 0.1.4-beta.1 seems to fix the issues for me. However logging in with popup does not work. After authentication the popup does not close, the redirectURL is opened in the popup instead of the origin window.
On opening the popup, the origin throws some errors -

I suppose this has something to do with maybe polyfills, just unsure what exactly is the issue yet

[jasonnutter]

@aleksandar-kandzhichki Yeah that is a known issue we are looking into. For now, our guidance is to use the redirect flow for IE11, instead of popups.

[mronus]

@jasonnutter I upgraded the library to 0.1.4-beta.2 but it seems not working. I still have the syntax exception in my console and it prevents everything to be loaded in Angular.

The exception:

The code line where pointed out by the exception:

I've also tried different workarounds which are given in github issues related to that problem but no one of them worked.

Any help or hint is highly appreciated :)

[jasonnutter]

@mronus That looks to be from msgraph-sdk-javascript (which you may have via microsoft-graph-client). See this thread for more info: https://github.com/microsoftgraph/msgraph-sdk-javascript/issues/190