Incompatibility to cordova-ios 5.0.0?

Same, updated all my libs to their current status and face the exact same problem

Unfortunately don’t have time right now to dig, I just rollbacked

Note: maybe we should open an issue or separate post as it is not related to Cordova

[ng] ERROR in ./node_modules/@ionic/core/dist/esm/es5/ionic.core.js 6:2160
[ng] Module parse failed: Unexpected token (6:2160)
[ng] You may need an appropriate loader to handle this file type.
[ng] |  * Built with http://stenciljs.com
[ng] |  */
[ng] > function n(n,t){return"sc-"+n.t+(t&&t!==c?"-"+t:"")}function t(n,t){return n+(t?"-h":"-s")}function e(n,t){for(var e,r,i=null,o=!1,u=!1,f=arguments.length;f-- >2;)A.push(arguments[f]);for(;A.length>0;){var c=A.pop();if(c&&void 0!==c.pop)for(f=c.length;f--;)A.push(c[f]);else"boolean"==typeof c&&(c=null),(u="function"!=typeof n)&&(null==c?c="":"number"==typeof c?c=String(c):"string"!=typeof c&&(u=!1)),u&&o?i[i.length-1].vtext+=c:null===i?i=[u?{vtext:c}:c]:i.push(u?{vtext:c}:c),o=u}if(null!=t){if(t.className&&(t.class=t.className),"object"==typeof t.class){for(f in t.class)t.class[f]&&A.push(f);t.class=A.join(" "),A.length=0}null!=t.key&&(e=t.key),null!=t.name&&(r=t.name)}return"function"==typeof n?n(t,i||[],E):{vtag:n,vchildren:i,vtext:void 0,vattrs:t,vkey:e,vname:r,i:void 0,o:!1}}function r(n,t,e){void 0===e&&(e={});var r=Array.isArray(t)?t:[t],i=n.document,o=e.hydratedCssClass||"hydrated",u=e.exclude;u&&(r=r.filter(function(n){return-1===u.indexOf(n[0])}));var c=r.map(function(n){return n[0]});if(c.length>0){var a=i.createElement("style");a.innerHTML=c.join()+"{visibility:hidden}."+o+"{visibility:inherit}",a.setAttribute("data-styles",""),i.head.insertBefore(a,i.head.firstChild)}var s=e.namespace||"Ionic";return B||(B=!0,function l(n,t,e){(n["s-apps"]=n["s-apps"]||[]).push(t),e.componentOnReady||(e.componentOnReady=function t(){function e(t){if(r.nodeName.indexOf("-")>0){for(var e=n["s-apps"],i=0,o=0;o<e.length;o++)if(n[e[o]].componentOnReady){if(n[e[o]].componentOnReady(r,t))return;i++}if(i<e.length)return void(n["s-cr"]=n["s-cr"]||[]).push([r,t])}t(null)}var r=this;return n.Promise?new n.Promise(e):{then:e}})}(n,s,n.HTMLElement.prototype)),applyPolyfills(n).then(function(){function t(){r.forEach(function(t){var e;!function r(n){return/\{\s*\[native code\]\s*\}/.test(""+n)}(n.customElements.define)?(e=function(t){return n.HTMLElement.call(this,t)}).prototype=Object.create(n.HTMLElement.prototype,{constructor:{value:e,configurable:!0}}):e=new Function("w","return class extends w.HTMLElement{}")(n),U[s].u(function i(n){var t=C(n),e=t.s,r=d(n[0]);return t.s=function(n){var t=n.mode,i=n.scoped;return function o(n,t,e){return import(
[ng] | /* webpackInclude: /\.entry\.js$/ */
[ng] | /* webpackMode: "lazy" */

I have the same error when I upgrade cordova-android and my angular packages.

After reading this issue, I downgrade my package of @angular-devkit/architect and @angular-devkit/build-angular and it work again.

So we can say that is related with this two package version 0.13.x

1 Like

For me even by letting @angular-devkit/architect and @angular-devkit/build-angular to a previous it doesn’t work

As soon as I fetch all new libs (removing package-lock.json before fetching them) it fails

What if you rolled back cordova-ios to 4.5.5? Do you still get error relating to ionic.core.js?

Some people think this is a cordova or angular issue, but since the error message literally has error in file named Ionic.core.js, makes me think it’s clearly an ionic issue.

I won’t rollback Cordova as the new build system is mandatory to submit an app in the App Store as of March or something I think

Secondly I think it has nothing to do with Cordova as the problem happens when I “ionic serve” my app

2 Likes

I’m using version 5, no issues, just had to downgrade @angular-devkit/build-angular and @angular-devkit/architect to 0.12.x version

When I tried ng update -all:

                  Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=3.1.1 <3.3", would install "3.3.3333").
Incompatible peer dependencies found. See above.

Is this somehow related?

My package.json:

{
  ....
  "private": true,
  "dependencies": {
    "@angular/common": "^7.2.2",
    "@angular/core": "^7.2.2",
    "@angular/forms": "^7.2.2",
    "@angular/http": "^7.2.2",
    "@angular/platform-browser": "^7.2.2",
    "@angular/platform-browser-dynamic": "^7.2.2",
    "@angular/router": "^7.2.2",
    "@ionic-native/app-version": "^5.1.0",
    "@ionic-native/camera": "^5.1.0",
    "@ionic-native/core": "^5.1.0",
    "@ionic-native/file": "^5.1.0",
    "@ionic-native/file-path": "^5.1.0",
    "@ionic-native/file-transfer": "^5.1.0",
    "@ionic-native/geolocation": "^5.1.0",
    "@ionic-native/ionic-webview": "^5.1.0",
    "@ionic-native/photo-library": "^5.1.0",
    "@ionic-native/splash-screen": "^5.1.0",
    "@ionic-native/sqlite": "^5.1.0",
    "@ionic-native/status-bar": "^5.1.0",
    "@ionic/angular": "^4.0.2",
    "@ionic/storage": "^2.2.0",
    "class-transformer": "^0.2.0",
    "cordova-android": "7.1.4",
    "cordova-browser": "5.0.4",
    "cordova-ios": "5.0.0",
    "cordova-plugin-add-swift-support": "^1.6.0",
    "cordova-plugin-app-version": "^0.1.9",
    "cordova-plugin-camera": "^4.0.3",
    "cordova-plugin-device": "^2.0.2",
    "cordova-plugin-file": "^6.0.1",
    "cordova-plugin-file-transfer": "^1.7.1",
    "cordova-plugin-filepath": "^1.5.1",
    "cordova-plugin-geolocation": "^4.0.1",
    "cordova-plugin-ionic-keyboard": "^2.1.3",
    "cordova-plugin-ionic-webview": "^3.1.2",
    "cordova-plugin-photo-library": "^2.2.1",
    "cordova-plugin-splashscreen": "^5.0.2",
    "cordova-plugin-statusbar": "^2.4.2",
    "cordova-plugin-whitelist": "^1.3.3",
    "cordova-sqlite-storage": "^3.1.0",
    "core-js": "^2.5.4",
    "hammerjs": "^2.0.8",
    "jquery": "^3.3.1",
    "rxjs": "~6.4.0",
    "zone.js": "~0.8.29"
  },
  "devDependencies": {
    "@angular-devkit/architect": "~0.12.3",
    "@angular-devkit/build-angular": "~0.12.3",
    "@angular-devkit/core": "~7.2.3",
    "@angular-devkit/schematics": "~7.2.3",
    "@angular/cli": "~7.3.3",
    "@angular/compiler": "~7.2.2",
    "@angular/compiler-cli": "~7.2.2",
    "@angular/language-service": "~7.2.2",
    "@ionic/angular-toolkit": "~1.3.0",
    "@types/jasmine": "~2.8.8",
    "@types/jasminewd2": "~2.0.3",
    "@types/jquery": "^3.3.29",
    "@types/node": "~10.12.0",
    "codelyzer": "~4.5.0",
    "jasmine-core": "~2.99.1",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "~3.1.4",
    "karma-chrome-launcher": "~2.2.0",
    "karma-coverage-istanbul-reporter": "~2.0.1",
    "karma-jasmine": "~1.1.2",
    "karma-jasmine-html-reporter": "^0.2.2",
    "protractor": "~5.4.0",
    "ts-node": "~8.0.0",
    "tslint": "~5.12.0",
    "typescript": "~3.1.6"
  },
  "description": "Ankünder Instaboard",
  "cordova": {
    "plugins": {
      "cordova-plugin-whitelist": {},
      "cordova-plugin-statusbar": {},
      "cordova-plugin-device": {},
      "cordova-plugin-splashscreen": {},
      "cordova-plugin-ionic-keyboard": {},
      "cordova-plugin-file-transfer": {},
      "cordova-plugin-filepath": {},
      "cordova-plugin-file": {},
      "cordova-plugin-camera": {},
      "cordova-plugin-geolocation": {},
      "cordova-sqlite-storage": {},
      "cordova-plugin-app-version": {},
      "cordova-plugin-photo-library": {
        "PHOTO_LIBRARY_USAGE_DESCRIPTION": " "
      },
      "cordova-plugin-ionic-webview": {
        "ANDROID_SUPPORT_ANNOTATIONS_VERSION": "27.+"
      }
    },
    "platforms": [
      "android",
      "browser",
      "ios"
    ]
  }
}

This is NOT related.

Downgrading @angular-devkit doesn’t seem like a good solution either.

It is not, but ionic team does not think this is their issue!! they have to integrate with the new tool and fix this issue, somehow. the issue happens only when you upgrade @angular-devkit and it is not related to cordova-ios 5 either, I got the issue even with cordova-ios was 4.5.5.

what’s the reference for that assumption? you’ve got an issue to share?

This is the link: https://github.com/ionic-team/ionic/issues/17455

They simply opened this thread as an issue, locked it, and tagged with “ionitron: support”, look at the stupid bot comment regarding this.

thx for pointing that out

Hey folks! I’ve been testing cordova-ios 5 with the latest starter projects, but have not had this issue.

@almothafar_capella Sorry about the bot, it gets a little over aggressive when it checks issues.

If you have a project that is up on github, I can examine it a bit more. But we have not been able to reproduce this on our end.

I’ve been testing cordova-ios 5 with the latest starter projects, but have not had this issue.

Yes with starter, everything is fine, because the new version of devkit is not updated for starters:

"@angular-devkit/architect": "~0.12.3",
"@angular-devkit/build-angular": "~0.12.3",

but once you update these two:

"@angular-devkit/architect": "~0.13.3",
"@angular-devkit/build-angular": "~0.13.3",

And delete your package-lock.json, delete node_modules, to make sure you install the latest version of all dependencies before installing modules back with npm i, you will get the issue, maybe, because I got the issue when my docker was building project, I found that later when I was going to do the production build, so it is always installing the latest, this is why not many people got the issue for now, it is just early trigger for the issue.

1 Like

I can confirm the same issue in ours, which we fixed by rolling back @angular-devkit/architect and @angular-devkit/build-angular

I opened the new issue, hopefully you look into it without that aggressive bot :slight_smile:

Rolling back @angular-devkit packages doesn’t seem like a good fix.

What is odd to me, is that the build error is found in Ionic.core.js. I don’t understand how these packages and Ionic.core.js are related.

Alright, I look it over. Please hang tight.

1 Like

It is good fix “for now” as it is not Major changes, but for sure it is broken for future releases, IT IS an Ionic issue, so this need to fix this, just go forward now with that workaround until they fix it, I would be mad if that was cordova-ios 5 issue, since that major version fixes many major issues with Xcode and the new build system.