-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Critical crash bug "typeError: intl is not available" #15687
Comments
We have been experiencing this as well, same fix - editing the vendor.js and inserting a try/catch. Angular: 5.2.9 |
@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: |
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. |
…dows On some versions of Windows merely trying to access the `Intl` object can cause IE to throw an error, if the default `Map` object has been overwritten (e.g. when polyfilling). These changes add a `try/catch` around our usages so that users' apps don't crash completely on load. Fixes angular#15687.
…dows On some versions of Windows merely trying to access the `Intl` object can cause IE to throw an error, if the default `Map` object has been overwritten (e.g. when polyfilling). These changes add a `try/catch` around our usages so that users' apps don't crash completely on load. Fixes angular#15687.
We can now confirm that the issue (Angular App not being rendered) after kb4489881 installed on win8.1/winserver2012 + IE11. |
I've submitted a fix at #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 |
Sorry, what I meant is to check whether the changes from #15693 would fix the issue. |
…dows On some versions of Windows merely trying to access the `Intl` object can cause IE to throw an error, if the default `Map` object has been overwritten (e.g. when polyfilling). These changes add a `try/catch` around our usages so that users' apps don't crash completely on load. Fixes #15687.
…dows (#15693) On some versions of Windows merely trying to access the `Intl` object can cause IE to throw an error, if the default `Map` object has been overwritten (e.g. when polyfilling). These changes add a `try/catch` around our usages so that users' apps don't crash completely on load. Fixes #15687.
@mmalerba Thanks much! |
@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 |
…dows (#15693) On some versions of Windows merely trying to access the `Intl` object can cause IE to throw an error, if the default `Map` object has been overwritten (e.g. when polyfilling). These changes add a `try/catch` around our usages so that users' apps don't crash completely on load. Fixes #15687.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
What is the expected behavior?
Have a fallback for Intl while is not available
What is the current behavior?
Unexpectedly, all the app crashed and "typeError: intl is not available" error is presented at console.
Only IE-11
What are the steps to reproduce?
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.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular: 7.2.1
CDK: 7.2.1
TypeScript: 3.2.2
Browsers: IE 11
Is there anything else we should know?
Critical bug, should provide hotfix.
The text was updated successfully, but these errors were encountered: