Ionic-app-scripts: ionic build --prod gets stuck after copying because of @firebase/app

[westphalen]

Short description of the problem:

There seems to have been some issues running ionic build --prod with certain version of @ionic/app-scripts and webpack back in late 2017, but I'm experiencing this issue with a new project on latest versions in 2018.

Specifically, the build process gets stuck right after copy finished. Eventually (about half an hour with default settings) it will exhaust memory and crash.

The reason this started happening for me was firebase init functions creating a functions directory in my project. This should be ok, but for some reason Webpack picks it up for my ionic build --prod and goes amok.

What behavior are you expecting?

functions directory is unrelated and thus ignored by app-scripts.

Steps to reproduce:

1. Start a new Ionic project.
2. firebase init functions
3. ionic build --prod

Which @ionic/app-scripts version are you using?
3.1.9

Other information:

Either webpack should not touch any files not related specifically to the Ionic project, or we should be able to configure the scope somehow.

[westphalen]

It seems the reported issue had nothing to do with firebase functions after all.

The real culprit was having the Ionic project depend on @firebase/app@^0.1.10.
Getting rid of that dependency immediately fixed the issue.

webpack finished in 67s

[Bengejd]

@westphalen how did you manage to get rid of the @firebase/app@^0.1.10 dependency without breaking everything?

[westphalen]

If you depend on it directly, I have no idea.

It was just in my project to support angularfire and firebase.

After upgrading everything, and then downgrading firebase to 4.12.1, I could build my app without @firebase/app@^0.1.10.

Reason for the downgrade: https://github.com/angular/angularfire2/issues/1576

[vincent-cm]

related to https://github.com/firebase/firebase-js-sdk/issues/904

[tahminabs23]

Unfortunately, I can not downgrade to firebase 4.12.1. Because I am depending on version 5. Has there any option to proceed to build without downgrading?

[westphalen]

@tahminabs23 Have you tried with angularfire2 5.0.0-rc-7.0?

[tahminabs23]

@westphalen yes, I tried with 5.0.0-rc.7 and firebase/app 0.1.10, but still gets stuck after copying when I use --prod

[tahminabs23]

Now I tried with "angularfire2": "^5.0.0-rc.7.0-next", "firebase": "^4.13.1", and it generates new issue https://github.com/angular/zone.js/issues/1081

[Usamaliaquat123]

@westphalen thank bro it works for me ...! [email protected] 💯 💯 💯 💯 💯 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 thanks dude ...

[germanriverahdez]

Yes, downgrade to [email protected].
This fix the problem for me.

Thank you @westphalen

[saryuvc]

Hello,

Please remove www folder,node modules,platforms, and npm install

please note : I have updated to ionic 4 and cordova 8.

this solved my issue.

[ghost]

After copy, webpack finished command is not displayed and freezes terminal.

I m using FCM push notification and I'm facing a similar issue. Any solutions?

I have tried these three solutions :

https://forum.ionicframework.com/t/ionic-build-prod-stuck-at-copy-finished-in/129732/11

https://stackoverflow.com/questions/26094420/fatal-error-call-and-retry-last-allocation-failed-process-out-of-memory

https://github.com/ionic-team/ionic-app-scripts/issues/1426

project property :

target=android-25
android.library.reference.1=CordovaLib
cordova.gradle.include.1=phonegap-plugin-push/coseionic2691015-push.gradle
cordova.system.library.1=com.android.support:support-v4:24.1.1+
cordova.system.library.2=com.android.support:support-v4:24.1.1+
cordova.system.library.3=com.android.support:support-v13:23+
cordova.system.library.4=com.google.android.gms:play-services-gcm:11+
cordova.system.library.5=me.leolin:ShortcutBadger:1.1.14@aar
cordova.system.library.6=com.android.support:support-v4:+

[r6047736]

If anyone using [email protected] and occurs the problem, downgrade to 5.4.1 works for me.

[kevinrodriguez-io]

Unfortunately,
If i downgrade to 4.12.1

i get the following error from angularfire2

[23:01:04]  typescript: ...darkn/projects/IONIC/airmedix/node_modules/angularfire2/firebase.app.module.d.ts, line: 2
            Module '"C:/Users/darkn/projects/IONIC/airmedix/node_modules/firebase/index"' has no exported member
            'functions'.

       L1:  import { InjectionToken } from '@angular/core';
[23:01:04]  typescript: C:/Users/darkn/projects/IONIC/airmedix/node_modules/angularfire2/auth/auth.d.ts, line: 12
[23:01:04]  ionic-app-script task: "build"
[23:01:04]  Error: The Angular AoT build failed. See the issues above
Error: The Angular AoT build failed. See the issues above
    at C:\Users\darkn\projects\IONIC\airmedix\node_modules\@ionic\app-scripts\dist\aot\aot-compiler.js:232:55
    at step (C:\Users\darkn\projects\IONIC\airmedix\node_modules\@ionic\app-scripts\dist\aot\aot-compiler.js:32:23)
    at Object.next (C:\Users\darkn\projects\IONIC\airmedix\node_modules\@ionic\app-scripts\dist\aot\aot-compiler.js:13:53)
    at fulfilled (C:\Users\darkn\projects\IONIC\airmedix\node_modules\@ionic\app-scripts\dist\aot\aot-compiler.js:4:58)
       L2:  import { app, auth, database, firestore, functions, messaging, storage } from 'firebase';
       L3:  export declare type FirebaseOptions = {

            Namespace 'firebase.auth' has no exported member 'IdTokenResult'.

      L11:  readonly user: Observable<User | null>;
      L12:  readonly idTokenResult: Observable<auth.IdTokenResult | null>;
      L13:  constructor(options: FirebaseOptions, nameOrConfig: string | FirebaseAppConfig | undefined, platformId: Object, zone: NgZone);

I also downgraded to angularfire2 5.0.0-rc.7 and get "Zone already loaded" error which doesn't allow my app to run, i also had to change some calls for fireAuth.user...

[kevinrodriguez-io]

Update: See my latest comment, it works better than this solution.

Ok, thanks to @tahminabs23 i managed to find a solution.

This combination is working fine for me at the moment.

npm i --save [email protected]
npm i --save [email protected]

I had to change some code for the Auth validation:

From:

const userSubscription = angularFireAuth.user.subscribe(user => {
  // Some code here
  userSubscription.unsubscribe();
});

To

const unsubscribe = angularFireAuth.auth.onAuthStateChanged(user => {
  // Some code here
  unsubscribe();
});

[saumya04]

The combination of these 2 versions solved the issue for me:

firebase - 4.12.1
angularfire2 - 5.0.0-rc.4

npm i [email protected] [email protected] --save

[blasco]

@saumya04 Is that combination working? I get this warning:

npm WARN [email protected] requires a peer of firebase@^4.5.0 but none is installed

[saumya04]

@WooWapDaBug Yup the combination is working for me...

[blasco]

@saumya04 You are right, now it is working. I don't know what I was doing wrong

[kevinrodriguez-io]

I have to tell that this is not the best solution.

The best solution is to stop using the old angularfire2 namespace and switch to latest firebase, @angular/fire (this one instead of angularfire2) releases . At some point if you need offline usage you will have to try angularfire2-offline and that package is no longer mantained, so you will maybe want to try firestore, which is not supported in the [email protected], [email protected] combination.

My fix (which i think is the best for this specific scenario) was to update to latest @angular/fire and firebase and update all my imports... I also remember having some issues with the rxjs compat package but those are gone now.

My current working packages.json dependencies look like this:

{
    "@angular/common": "5.2.11", (other angular dependencies look like this)
    ... (Others)
    "@angular/fire": "^5.0.2",
    "firebase": "^5.5.4",
    "rxjs": "^6.2.2",
    "rxjs-compat": "^6.2.2",
    "zone.js": "0.8.26"
}

You have to uninstall angularfire2 and firebase and reinstall with
npm i @angular/fire firebase --save

That solution worked for me and now i enjoy the latest features and firestore support with offline usage.

[adamduren]

@kevinrodriguez-io FWIW I have this issue occur without any library other than "firebase": "^5.5.2".

[franzisk]

@westphalen thank bro it works for me ...! [email protected] 💯 💯 💯 💯 💯 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 🥇 thanks dude ...

Where did you change it to 4.12.1?

[courageDeveloper]

I have to tell that this is not the best solution.

The best solution is to stop using the old angularfire2 namespace and switch to latest firebase, @angular/fire (this one instead of angularfire2) releases . At some point if you need offline usage you will have to try angularfire2-offline and that package is no longer mantained, so you will maybe want to try firestore, which is not supported in the [email protected], [email protected] combination.

My fix (which i think is the best for this specific scenario) was to update to latest @angular/fire and firebase and update all my imports... I also remember having some issues with the rxjs compat package but those are gone now.

My current working packages.json dependencies look like this:

{
    "@angular/common": "5.2.11", (other angular dependencies look like this)
    ... (Others)
    "@angular/fire": "^5.0.2",
    "firebase": "^5.5.4",
    "rxjs": "^6.2.2",
    "rxjs-compat": "^6.2.2",
    "zone.js": "0.8.26"
}

You have to uninstall angularfire2 and firebase and reinstall with
npm i @angular/fire firebase --save

That solution worked for me and now i enjoy the latest features and firestore support with offline usage.

@kevinrodriguez-io when you did this, your project stopped hanging when you used the production flag?

[courageDeveloper]

@westphalen what version of angularfire2 are you using?

[courageDeveloper]

Finally it worked for me, i downgraded my @ionic/app-scripts to 3.1.11 and also added @firebase/[email protected]. These two links really helped me out:
https://github.com/ionic-team/ionic-app-scripts/issues/1426
https://github.com/firebase/firebase-js-sdk/issues/714#issuecomment-414211953

[mattdodge]

@courageDeveloper what did your package.json ultimately look like? I'm running into this issue now. Did you install @firebase/[email protected] and also @angular/fire? Or were you using the old angularfire2 library?

[mattdodge]

I was able to get it (like most people it seems...) after trying a bunch of different solutions. For me, the key seemed to be installing @angular-devkit/build-optimizer. I am not including angularfire2 or @firebase/database.

Here are the important parts of my package.json:

{
  "dependencies": {
    "@angular-devkit/build-optimizer": "0.6.8",
    "@angular/fire": "^5.1.1",
    "firebase": "^5.7.1",
    "rxjs": "^6.0",
    "rxjs-compat": "^6.3.3"
  },
  "devDependencies": {
    "@ionic/app-scripts": "3.1.11"
  }
}

[sriramv18]

i am not using firebase but copy finished after freeze

here this package.json any remove or update please reply as soon as...
{
"name": "Ionic3AngularMaterial",
"version": "0.0.1",
"author": "Ionic Framework",
"homepage": "http://ionicframework.com/",
"private": true,
"repository": {
"type": "git",
"url": "https://github.com/ionic-team/ionic-conference-app.git"
},
"scripts": {
"build": "ionic build",
"serve": "ionic build",
"start": "npm run serve"
},
"dependencies": {
"@angular/animations": "^5.1.1",
"@angular/cdk": "^5.0.1",
"@angular/common": "5.0.3",
"@angular/compiler": "5.0.3",
"@angular/compiler-cli": "5.0.3",
"@angular/core": "^5.0.3",
"@angular/forms": "5.0.3",
"@angular/http": "5.0.3",
"@angular/material": "^5.0.1",
"@angular/platform-browser": "5.0.3",
"@angular/platform-browser-dynamic": "5.0.3",
"@ionic-native/android-permissions": "^4.20.0",
"@ionic-native/camera": "^4.16.0",
"@ionic-native/core": "4.4.0",
"@ionic-native/fingerprint-aio": "^4.16.0",
"@ionic-native/geolocation": "^4.19.0",
"@ionic-native/launch-navigator": "^4.16.0",
"@ionic-native/location-accuracy": "^4.19.0",
"@ionic-native/splash-screen": "4.4.0",
"@ionic-native/sqlite": "^4.19.0",
"@ionic-native/status-bar": "^4.16.0",
"@ionic/storage": "2.1.3",
"@types/chart.js": "^2.7.40",
"amazon-cognito-identity-js": "^3.0.3",
"chart.js": "^2.7.3",
"cordova-android": "7.1.4",
"cordova-browser": "5.0.4",
"cordova-plugin-android-permissions": "1.0.0",
"cordova-plugin-camera": "~4.0.3",
"cordova-plugin-compat": "1.2.0",
"cordova-plugin-device": "2.0.2",
"cordova-plugin-fingerprint-aio": "~1.4.1",
"cordova-plugin-geolocation": "2.4.3",
"cordova-plugin-ionic-keyboard": "^2.0.5",
"cordova-plugin-ionic-webview": "^2.0.0",
"cordova-plugin-request-location-accuracy": "2.2.3",
"cordova-plugin-splashscreen": "5.0.2",
"cordova-plugin-statusbar": "2.4.2",
"cordova-plugin-whitelist": "1.3.3",
"cordova-sqlite-storage": "2.6.0",
"hammerjs": "^2.0.8",
"increase-memory-limit": "^1.0.6",
"ionic-angular": "3.9.2",
"ionic-img-viewer": "^2.9.0",
"ionicons": "3.0.0",
"rxjs": "^6.3.1",
"rxjs-compat": "^6.3.1",
"sw-toolbox": "3.6.0",
"uk.co.workingedge.phonegap.plugin.launchnavigator": "~4.2.2",
"zone.js": "0.8.18"
},
"devDependencies": {
"@ionic/app-scripts": "3.1.5",
"typescript": "2.4.2"
},
"description": "An Ionic project",
"config": {

"ionic_bundler": "webpack",
"ionic_generate_source_map": false,
"ionic_source_map_type": "source-map"

},
"cordova": {
"plugins": {
"cordova-plugin-fingerprint-aio": {},
"uk.co.workingedge.phonegap.plugin.launchnavigator": {
"OKHTTP_VERSION": "3.+"
},
"cordova-plugin-camera": {},
"cordova-plugin-whitelist": {},
"cordova-plugin-statusbar": {},
"cordova-plugin-device": {},
"cordova-plugin-splashscreen": {},
"cordova-plugin-ionic-webview": {},
"cordova-plugin-ionic-keyboard": {},
"cordova-plugin-geolocation": {
"GEOLOCATION_USAGE_DESCRIPTION": "To track your walks"
},
"cordova-plugin-request-location-accuracy": {},
"cordova-sqlite-storage": {},
"cordova-plugin-android-permissions": {}
},
"platforms": [
"browser",
"android"
]
}
}

[ColDrekken]

adding @angular-devkit/build-optimizer as @mattdodge mentioned solved this for me.

Thx.

[kevinrodriguez-io]

@angular-devkit/build-optimizer

I don't know what kind of black magic this does, but it fixed a couple of projects with the same problem but with no firebase 😄

[franzisk]

@angular-devkit/build-optimizer

I don't know what kind of black magic this does, but it fixed a couple of projects with the same problem but with no firebase 😄

Tons of errors came up after installing this plugin:

> ionic-app-scripts serve --address 0.0.0.0 --port 8100 --livereload-port 35729 --dev-logger-port 53703 --nobrowser
[app-scripts] [09:23:23]  ionic-app-scripts 3.2.2
[app-scripts] [09:23:23]  watch started ...
[app-scripts] [09:23:23]  build dev started ...
[app-scripts] [09:23:23]  clean started ...
[app-scripts] [09:23:23]  clean finished in 15 ms
[app-scripts] [09:23:23]  copy started ...
[app-scripts] [09:23:24]  deeplinks started ...
[app-scripts] [09:23:24]  deeplinks finished in 543 ms
[app-scripts] [09:23:24]  transpile started ...
[app-scripts] [09:23:33]  typescript: node_modules/@angular/common/http/src/response.d.ts, line: 253
[app-scripts]             Initializers are not allowed in ambient contexts.
[app-scripts]      L252:  readonly ok = false;
[app-scripts]      L253:  constructor(init: {
[app-scripts]      L254:      error?: any;
[app-scripts] [09:23:33]  typescript: node_modules/@angular/common/http/src/response.d.ts, line: 259
[app-scripts]             Initializers are not allowed in ambient contexts.
[app-scripts]      L258:          url?: string;
[app-scripts]      L259:      });
[app-scripts]             Cannot find name 'NonNullable'.
[app-scripts]      L121:      $implicit: any;
[app-scripts] [09:23:33]  typescript: node_modules/@angular/common/src/directives/ng_if.d.ts, line: 122
[app-scripts]      L122:      ngIf: any;
[app-scripts]             Initializers are not allowed in ambient contexts.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/application_init.d.ts, line: 26
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/ivy_switch/compiler/ivy_switch_on.d.ts, line: 12
[app-scripts]             A 'const' initializer in an ambient context must be a string or numeric literal.
[app-scripts]       L11:  export declare const R3_COMPILE_NGMODULE_DEFS: typeof compileNgModuleDefs;
[app-scripts]       L12:  export declare const R3_PATCH_COMPONENT_DEF_WTIH_SCOPE: typeof patchComponentDefWithScope;
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/ivy_switch/compiler/legacy.d.ts, line: 19
[app-scripts]             A 'const' initializer in an ambient context must be a string or numeric literal.
[app-scripts]       L18:  export declare let R3_COMPILE_NGMODULE_DEFS: DirectiveCompiler;
[app-scripts]       L19:  export declare let R3_PATCH_COMPONENT_DEF_WTIH_SCOPE: DirectiveCompiler;
[app-scripts]             Initializers are not allowed in ambient contexts.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/linker/query_list.d.ts, line: 36
[app-scripts]       L36:   * See
[app-scripts]       L37:   * [Array.map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/map)
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/container.d.ts, line: 37
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/container.d.ts, line: 45
[app-scripts]       L36:   * are no longer required.
[app-scripts]       L38:  [VIEWS]: LViewData[];
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L45:   * This allows us to jump from a container to a sibling container or component
[app-scripts]       L46:   * view with the same parent, so we can remove listeners efficiently.
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/container.d.ts, line: 50
[app-scripts]       L50:   * Queries active for this container - all the views inserted to / removed from
[app-scripts]       L51:   * this container are reported to queries referenced here.
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/container.d.ts, line: 55
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/container.d.ts, line: 60
[app-scripts]       L55:   * The host element of this LContainer.
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L60:  * It could also be a styling context if this is a node with a style/class
[app-scripts]       L61:  * binding.
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/container.d.ts, line: 70
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/container.d.ts, line: 72
[app-scripts]       L70:  * If `renderParent` is `null` it is headless. This means that it is contained
[app-scripts]       L71:  * in another view which in turn is contained in another container and
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L71:  * in another view which in turn is contained in another container and
[app-scripts]       L72:  * therefore it does not yet have its own parent.
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L74:  * When present all animation players will be passed into the flush method below.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/container.d.ts, line: 93
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/player.d.ts, line: 75
[app-scripts]       L75:  * This feature is designed to service application-wide animation testing, live
[app-scripts]       L76:  * debugging as well as custom animation choreographing tools.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/player.d.ts, line: 76
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L75:  * This feature is designed to service application-wide animation testing, live
[app-scripts]       L76:  * debugging as well as custom animation choreographing tools.
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/player.d.ts, line: 77
[app-scripts]       L76:   * debugging as well as custom animation choreographing tools.
[app-scripts]       L78:  export interface PlayerHandler {
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/player.d.ts, line: 78
[app-scripts]       L78:  export interface PlayerHandler {
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/player.d.ts, line: 79
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L78:  export interface PlayerHandler {
[app-scripts]       L80:       * Designed to kick off the player at the end of change detection
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/styling.d.ts, line: 123
[app-scripts]      L122:   * Location of initial data shared by all instances of this style.
[app-scripts]      L124:  [StylingIndex.InitialStylesPosition]: InitialStyles;
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/styling.d.ts, line: 127
[app-scripts]      L126:  * A numeric value representing the configuration status (whether the context is dirty or not)
[app-scripts]      L127:  * mixed together (using bit shifting) with a index value which tells the starting index value
[app-scripts]      L128:  * of where the multi style entries begin.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/styling.d.ts, line: 131
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]      L130:  [StylingIndex.MasterFlagPosition]: number;
[app-scripts]      L132:   * A numeric value representing the class index offset value. Whenever a single class is
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/styling.d.ts, line: 137
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/styling.d.ts, line: 143
[app-scripts]      L136:  [StylingIndex.ClassOffsetPosition]: number;
[app-scripts]      L138:   * Location of element that is used as a target for this context.
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]      L142:  * The last class value that was interpreted by elementStylingMap. This is cached
[app-scripts]      L143:  * So that the algorithm can exit early incase the value has not changed.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/styling.d.ts, line: 147
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]      L146:      [key: string]: any;
[app-scripts]      L147:  } | string | null;
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/styling.d.ts, line: 152
[app-scripts]      L152:  [StylingIndex.PreviousMultiStyleValue]: {
[app-scripts]      L153:      [key: string]: any;
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/styling.d.ts, line: 159
[app-scripts]      L158:  * the context during allocation. The 0th value must be null so that index values of `0` within
[app-scripts]      L159:  * the context flags can always point to a null value safely when nothing is set.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 56
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L55:  * views as it is recursively rendering templates.
[app-scripts]       L57:  * This is the "insertion" view for embedded views. This allows us to properly
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L57:  * This is the "insertion" view for embedded views. This allows us to properly
[app-scripts]       L58:  * destroy embedded views.
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 58
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 67
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 77
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 79
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 85
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 96
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 104
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 113
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 121
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 123
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 125
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 127
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 134
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 143
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 149
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/render3/interfaces/view.d.ts, line: 174
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/sanitization/bypass.d.ts, line: 23
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L66:  * container. Embedded views already have a node.next, but it is only set for
[app-scripts]       L67:  * views in the same container. We need a way to link component views and views
[app-scripts]       L68:  * across containers as well.
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L76:   * If this is an embedded view, HOST will be null.
[app-scripts]       L78:  [HOST]: RElement | StylingContext | null;
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L78:  [HOST]: RElement | StylingContext | null;
[app-scripts]       L80:   * Pointer to the `TViewNode` or `TElementNode` which represents the root of the view.
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L85:  * If `TElementNode`, this is the LView of a component.
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L95:   * a setter that creates an embedded view, like in ngIf).
[app-scripts]       L97:  [BINDING_INDEX]: number;
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]      L103:  * These change per LView instance, so they cannot be stored on TView. Instead,
[app-scripts]      L104:  * TView.cleanup saves an index to the necessary context in this array.
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]      L112:   * - For inline views, the context is null.
[app-scripts]      L114:  [CONTEXT]: {} | RootContext | null;
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]      L120:  [SANITIZER]: Sanitizer | null;
[app-scripts]      L122:   * The last LViewData or LContainer beneath this LViewData in the hierarchy.
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]      L122:  * The last LViewData or LContainer beneath this LViewData in the hierarchy.
[app-scripts]      L124:  * The tail allows us to quickly add a new state to the end of the view list
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]      L124:  * The tail allows us to quickly add a new state to the end of the view list
[app-scripts]      L125:  * without having to propagate starting from the first child.
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]      L127:  [TAIL]: LViewData | LContainer | null;
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]      L133:  * containers because their parent cannot be stored on the TViewNode (views may be inserted
[app-scripts]      L134:  * in multiple containers, so the parent cannot be shared between view instances).
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]      L142:  [CONTENT_QUERIES]: QueryList<any>[] | null;
[app-scripts]      L144:   * View where this view's template was declared.
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]      L148:  * The template for a dynamically created view may be declared in a different view than
[app-scripts]      L149:  * it is inserted. We already track the "insertion view" (view where the template was
[app-scripts]      L150:  * inserted) in LViewData[PARENT], but we also need access to the "declaration view"
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]      L174:  * This must be stored in the view rather than using `data` as a marker so that
[app-scripts]      L175:  * we can properly support embedded views. Otherwise, when exiting a child view
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L23:  export interface TrustedHtmlString extends TrustedString {
[app-scripts]       L24:      [BRAND]: BypassType.Html;
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L31:  export interface TrustedStyleString extends TrustedString {
[app-scripts]       L32:      [BRAND]: BypassType.Style;
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L39:  export interface TrustedScriptString extends TrustedString {
[app-scripts]       L40:      [BRAND]: BypassType.Script;
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L47:  export interface TrustedUrlString extends TrustedString {
[app-scripts]       L48:      [BRAND]: BypassType.Url;
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L55:  export interface TrustedResourceUrlString extends TrustedString {
[app-scripts]       L56:      [BRAND]: BypassType.ResourceUrl;
[app-scripts]             A computed property name in an interface must directly refer to a built-in symbol.
[app-scripts]       L62:  * This function wraps the trusted string in `String` and brands it in a way which makes it
[app-scripts]       L63:  * recognizable to {@link htmlSanitizer} to be trusted implicitly.
[app-scripts]             A computed property name in a type literal must directly refer to a built-in symbol.
[app-scripts]        L8:  export declare function isOnRunEffects(sourceInstance: {
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/sanitization/bypass.d.ts, line: 31
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/sanitization/bypass.d.ts, line: 39
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/sanitization/bypass.d.ts, line: 47
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/sanitization/bypass.d.ts, line: 55
[app-scripts] [09:23:33]  typescript: node_modules/@angular/core/src/sanitization/bypass.d.ts, line: 63
[app-scripts] [09:23:33]  typescript: node_modules/@ngrx/effects/src/on_run_effects.d.ts, line: 9
[app-scripts]        L9:      [onRunEffectsKey]?: onRunEffectsFn;
[app-scripts]       L10:  }): sourceInstance is OnRunEffects;

Ionic config:

Ionic:

   ionic (Ionic CLI)  : 4.11.0 (/Users/francisco/.npm-packages/lib/node_modules/ionic)
   Ionic Framework    : ionic-angular 3.9.2
   @ionic/app-scripts : 3.2.2

Cordova:

   cordova (Cordova CLI) : 7.1.0
   Cordova Platforms     : android 6.3.0, ios 4.5.5
   Cordova Plugins       : cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 2.2.0, (and 27 other plugins)

System:

   ios-deploy : 2.0.0
   ios-sim    : 6.0.0
   NodeJS     : v8.11.3 (/usr/local/bin/node)
   npm        : 5.6.0
   OS         : macOS Mojave
   Xcode      : Xcode 10.1 Build version 10B61

Plugins:

com.googlemaps.ios 2.7.0 "Google Maps SDK for iOS"
com.telerik.plugins.nativepagetransitions 0.6.5 "Native Page Transitions"
cordova-android-support-gradle-release 2.0.1 "cordova-android-support-gradle-release"
cordova-plugin-add-swift-support 1.7.2 "AddSwiftSupport"
cordova-plugin-android-permissions 1.0.0 "Permissions"
cordova-plugin-camera 4.0.3 "Camera"
cordova-plugin-compat 1.2.0 "Compat"
cordova-plugin-console 1.1.0 "Console"
cordova-plugin-contacts 3.0.1 "Contacts"
cordova-plugin-device 2.0.2 "Device"
cordova-plugin-email-composer 0.8.15 "EmailComposer"
cordova-plugin-facebook4 3.1.0 "Facebook Connect"
cordova-plugin-file 6.0.1 "File"
cordova-plugin-geolocation 4.0.1 "Geolocation"
cordova-plugin-globalization 1.11.0 "Globalization"
cordova-plugin-googleplus 5.3.2 "Google SignIn"
cordova-plugin-ionic-keyboard 2.1.3 "cordova-plugin-ionic-keyboard"
cordova-plugin-ionic-webview 2.2.0 "cordova-plugin-ionic-webview"
cordova-plugin-linkedin 1.2.1 "LinkedIn"
cordova-plugin-mauron85-background-geolocation 3.0.0-alpha.50 "CDVBackgroundGeolocation"
cordova-plugin-media 5.0.2 "Media"
cordova-plugin-nativeaudio 3.0.9 "Cordova Native Audio"
cordova-plugin-nativegeocoder 3.1.2 "NativeGeocoder"
cordova-plugin-network-information 2.0.1 "Network Information"
cordova-plugin-splashscreen 5.0.2 "Splashscreen"
cordova-plugin-statusbar 2.4.2 "StatusBar"
cordova-plugin-streaming-media 2.2.0 "StreamingMedia"
cordova-plugin-whitelist 1.3.3 "Whitelist"
cordova-plugin-x-socialsharing 5.4.1 "SocialSharing"
cordova-sqlite-storage 2.5.0 "Cordova sqlite storage plugin"
es6-promise-plugin 4.2.2 "Promise"
ionic-plugin-keyboard 2.2.1 "Keyboard"
phonegap-plugin-barcodescanner 8.0.0 "BarcodeScanner"
phonegap-plugin-push 2.1.2 "PushPlugin"
twitter-connect-plugin 0.6.0 "Twitter Connect"

[sriramv18]

This simple temporary solution Your Project folder open vs code find main.js.map and open delete content then save after run ionic prod build all issues are solved

[franzisk]

This simple temporary solution Your Project folder open vs code find main.js.map and open delete content then save after run ionic prod build all issues are solved

I can't find this file main.js.map, where is it located exactly?
Do you mean to leave this file empty?
Also, those errors appeared when I ran: ionic serve -b

[sriramv18]

ok no problem,

its place of the file here project_path/.source_maps/main.js.map