ionic-framework: Getting : Uncaught TypeError: t.resolve is not a function

@kensodemann HamzaLJ never got back to you, but I actually have the exact same issue with a project of mine. You can find a completely cut-down version of my project here. I’ve removed all of the typescript code except for the bare minimum initializations required to run into the error, in my own case.

I’m not sure if the error is in ionic (honestly, I don’t think so) but I’d personally appreciate it very much if somebody more experienced with this had a good idea of how to solve the issue properly.

After digging deep into it, I ended up looking at the es6.promise.js file module in core-js as that was part of the code that was transpiled into the polyfills.js file. Digging into it with the chrome debugger, I noticed that the .Resolve function of the Promise that Object.SetNativePromise was setting, (as the exception text correctly states) has .Resolve set to null. So I assume something goes wrong somewhere when doing polyfilling for Promise.

The way I ended up solving it temporarily for myself, was to comment out line 26 - 36 in es6.promise.js, the following lines:

var USE_NATIVE = !!function () {
  try {
    // correct subclassing with @@species support
    var promise = $Promise.resolve(1);
    var FakePromise = (promise.constructor = {})[require('./_wks')('species')] = function (exec) {
      exec(empty, empty);
    };
    // unhandled rejections tracking support, NodeJS Promise without it fails @@species test
    return (isNode || typeof PromiseRejectionEvent == 'function') && promise.then(empty) instanceof FakePromise;
  } catch (e) { /* empty */ }
}();

which is the function that attempts to check if the Promise object has already been polyfilled by another library and instead, just replaced it with var USE_NATIVE = true;.

This is in no way a viable solution, but I just needed to get it work so I could get on with the test project.

The problem I run into now is the fact that I can’t get this to run on ionic’s build servers, because obviously I run into the same error there, since the Ionic build system uses the default implementations of the npm modules, as it should, so I’m once again stuck with this error.

Any good ideas as to how to solve it in a proper fashion?

Same problem here with ciscospark Browser SDK anyone has solved the problem?

A solution could be to inject the bundle directly in index.html of the ionic project. The bundle is generated through browserify.

had the same problem with mongodb-stitch played a lot with various settings and workarounds (different versions of angular, typescript, zone.js, custom fixes in zone.js lib)

the result is that I think there is currently no way to use it via npm, the only way was to add the stitch.min.js script BEFORE polyfill.js in html, and after

        const clientPromise = stitch.StitchClientFactory.create(this.appId);
        this.stitchClient = await clientPromise;

with declare var stitch; at the top

I am having the same problem. The problem started when I added the mongodb-stitch into the standard super starter pack. I just import " import { StitchClientFactory } from ‘mongodb-stitch’; in a provider.ts and nothing in app module or appcomponent.ts.