Have a fallback for Intl while is not available
Unexpectedly, all the app crashed and "typeError: intl is not available" error is presented at console.
Only IE-11
I Don't know if we can repro this, but I'll give the background story as far as it can help.
While changing the localization -
App crashed on this line:
const hasV8BreakIterator = (typeof Intl !== 'undefined' && (Intl as any).v8BreakIterator);
from this file:
https://github.com/angular/material2/blob/master/src/cdk/platform/platform.ts
with this error: "typeError: intl is not available".
This crash won't let the app start, and there is no fallback.
We manage to fix it while editing the vendor.**.js file, and adding try-catch
block for this line.
Angular: 7.2.1
CDK: 7.2.1
TypeScript: 3.2.2
Browsers: IE 11
Critical bug, should provide hotfix.
We have been experiencing this as well, same fix - editing the vendor.js and inserting a try/catch.
Angular: 5.2.9
CDK: 5.2.5
TypeScript: 2.7.2
Browsers: IE 11
@HawkSoftDevTeam Do you know the root cause?
@almogyehuda Not all instances of IE11 display this problem. It has gotten worse in the last month or two however. We are currently trying to find a commonality between instances of the problem. We've observed the issue on a subset of Windows 2012, Windows 8.1 boxes.
Currently suspecting this KB, and testing:
https://support.microsoft.com/en-us/help/4483187/cumulative-security-update-for-internet-explorer-december-19-2018
Can confirm installing a language pack induces the error state on a previously working machine. Reinstalling the KB does not fix the error.
We see that issue started on our end after the following updates were installed, testing.
https://support.microsoft.com/en-us/help/4489881/windows-8-1-update-kb4489881
We can now confirm that the issue (Angular App not being rendered) after kb4489881 installed on win8.1/winserver2012 + IE11.
https://support.microsoft.com/en-us/help/4489881/windows-8-1-update-kb4489881
@almogyehuda @HawkSoftDevTeam @thealmogg @crisbeto
I've submitted a fix at https://github.com/angular/material2/pull/15693, but it would be nice to get it double-checked against the particular Windows version before it goes in.
Thanks much @crisbeto! We are double checking now
@crisbeto
We did double check install/uninstall and the update is the root cause for that problem
Sorry, what I meant is to check whether the changes from #15693 would fix the issue.
Sorry, what I meant is to check whether the changes from #15693 would fix the issue.
@crisbeto Yes,
We validated and that's the proper fix.
@mmalerba Thanks much!
Any idea when it will be tagged? We're currently not functioning in production envs effecting more than 20k users daily.
Sorry for the rush but we need it ASAP.
@crisbeto Any new with tag for this fix? We're depend on this commit right now...
this will go out with our next release on Monday
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
_This action has been performed automatically by a bot._
Most helpful comment
@almogyehuda Not all instances of IE11 display this problem. It has gotten worse in the last month or two however. We are currently trying to find a commonality between instances of the problem. We've observed the issue on a subset of Windows 2012, Windows 8.1 boxes.
Currently suspecting this KB, and testing:
https://support.microsoft.com/en-us/help/4483187/cumulative-security-update-for-internet-explorer-december-19-2018