Closed DickChesterwood closed 6 years ago
IE11: rebuilding with prod mode off, we can now see errors in the console:
"Error: SyntaxError at callWithDebugContext (http://192.168.99.100/vendor.bundle.js:60293:9) at debugCreateRootView (http://192.168.99.100/vendor.bundle.js:59566:5) at ComponentFactory_.prototype.create (http://192.168.99.100/vendor.bundle.js:56463:9) at ComponentFactoryBoundToModule.prototype.create (http://192.168.99.100/vendor.bundle.js:49215:9) at ApplicationRef.prototype.bootstrap (http://192.168.99.100/vendor.bundle.js:51050:9) at Anonymous function (http://192.168.99.100/vendor.bundle.js:50777:67) at PlatformRef.prototype._moduleDoBootstrap (http://192.168.99.100/vendor.bundle.js:50777:13) at Anonymous function (http://192.168.99.100/vendor.bundle.js:50698:21) at ZoneDelegate.prototype.invoke (http://192.168.99.100/polyfills.bundle.js:6159:13) at onInvoke (http://192.168.99.100/vendor.bundle.js:49945:17)"
Perhaps more useful:
SCRIPT5011: Can't execute code from a freed script polyfills.bundle.js
Going to try an upgrade to the latest Angular, it may be caused by out of date packages or something.
Total failure. Still the same problem. Think the freed script thing is a red herring....
HTML1300: Navigation occurred. 192.168.99.100 Wed May 23 2018 15:26:10 GMT+0100 (GMT Daylight Time) Opening Web Socket... [date] Wed May 23 2018 15:26:10 GMT+0100 (GMT Daylight Time) "Opening Web Socket..."
ERROR Error: SyntaxError "ERROR" {
__proto__: { },
description: "SyntaxError",
message: "SyntaxError",
name: "Error",
ngDebugContext: { },
stack: "Error: SyntaxError
at callWithDebugContext (http://192.168.99.100/vendor.js:44240:9) at debugCreateRootView (http://192.168.99.100/vendor.js:43717:5) at ComponentFactory_.prototype.create (http://192.168.99.100/vendor.js:41539:9) at ComponentFactoryBoundToModule.prototype.create (http://192.168.99.100/vendor.js:35515:9) at ApplicationRef.prototype.bootstrap (http://192.168.99.100/vendor.js:37061:9) at Anonymous function (http://192.168.99.100/vendor.js:36822:67) at PlatformRef.prototype._moduleDoBootstrap (http://192.168.99.100/vendor.js:36822:13) at Anonymous function (http://192.168.99.100/vendor.js:36759:21) at ZoneDelegate.prototype.invoke (http://192.168.99.100/polyfills.js:7154:13) at onInvoke (http://192.168.99.100/vendor.js:36088:17)", Symbol(rxSubscriber)_g.cpwagjsd1gf: undefined }
ERROR CONTEXT [object Object] "ERROR CONTEXT" {
__proto__: { },
component: null,
componentRenderElement: { },
context: null,
elDef: { },
elOrCompView: { },
elView: { },
injector: { },
nodeDef: { },
nodeIndex: 7,
providerTokens: [ ],
references: { },
renderNode: { },
Symbol(rxSubscriber)_g.cpwagjsd1gf: undefined,
view: { }
}
Error: SyntaxError {
__proto__: { },
description: "SyntaxError",
message: "SyntaxError",
name: "Error",
ngDebugContext: { },
stack: "Error: SyntaxError
at callWithDebugContext (http://192.168.99.100/vendor.js:44240:9) at debugCreateRootView (http://192.168.99.100/vendor.js:43717:5) at ComponentFactory_.prototype.create (http://192.168.99.100/vendor.js:41539:9) at ComponentFactoryBoundToModule.prototype.create (http://192.168.99.100/vendor.js:35515:9) at ApplicationRef.prototype.bootstrap (http://192.168.99.100/vendor.js:37061:9) at Anonymous function (http://192.168.99.100/vendor.js:36822:67) at PlatformRef.prototype._moduleDoBootstrap (http://192.168.99.100/vendor.js:36822:13) at Anonymous function (http://192.168.99.100/vendor.js:36759:21) at ZoneDelegate.prototype.invoke (http://192.168.99.100/polyfills.js:7154:13) at onInvoke (http://192.168.99.100/vendor.js:36088:17)", Symbol(rxSubscriber)_g.cpwagjsd1gf: undefined }
I really don't have time for this. I'm going to have to cut losses and declare no support for IE11.
The edge problem is very weird, it isn't resolving local network addresses.
Edge: seems that a security restriction prevents ip addresses being used. I don't know, anyway we won't support that browser for the course either.
Had enough of this. Begone!
hello @DickChesterwood i have the same error in my project, And I don't know how to fix it, did you find anything ?
Hi, sorry @duvangil I didn't ever get to the root of this - is it working for you in chrome or firefox?
I assumed I would get lots of complaints about this from the course, but I haven't heard anything about it so far.
Edge doesn't even "see" the ip address of docker-machine