Rc0: Failed to execute 'fetch' on 'Window'


after upgrading my app to ionic 2 rc0 from the latest beta version, chrome always halts during startup on an unfetched exception, when dev tools are opened. Error is:

“TypeError: Failed to execute ‘fetch’ on ‘Window’: 1 argument required, but only 0 present.
at TypeError (native)
at http://localhost:8100/build/polyfills.js:3:16551
at http://localhost:8100/build/polyfills.js:3:16749
at e (http://localhost:8100/build/polyfills.js:2:31200)
at http://localhost:8100/build/polyfills.js:2:31256
at n (http://localhost:8100/build/polyfills.js:1:65)
at t.MyBundle (http://localhost:8100/build/polyfills.js:2:31127)
at http://localhost:8100/build/polyfills.js:3:19992

This is the code where it stops:

 var D = t[n("Promise")] = t.Promise;
                if (t.Promise = A,
                D && (p(D),
                "undefined" != typeof t.fetch)) {
                    var N = void 0;
                    try {
                        N = t.fetch() // <<<<<<<<<< here it stops
                    } catch (n) {
                        N = t.fetch("about:blank")
                    N.then(function() {
                        return null
                    }, function() {
                        return null
                    N.constructor != D && p(N.constructor)

Any idea?


Have the same issue. Any ideas why? If you spit this error, in a few sec everything function as it should be.


@Rasioc @alexdruk Unchecking pause on exceptions in the sources tab of chrome dev tools - blue hexagonal stop sign with pause button in it - temporarily sorted the problem for me. I don’t know the actual cause of it, maybe related to this https://github.com/angular/zone.js/issues/446 or this https://github.com/angular/angular-cli/issues/2122


Thank you, but this is not a solution. Problem persist for RC2


No, obviously not a solution but makes it usable for the time being. Having to unpause the debugger every time is ridiculous.