RC3 Error encountered resolving symbol values statically
basvdijk opened this issue · 1 comments
basvdijk commented
Short description of the problem:
App is not building with ionic run android
after upgrading to RC3
What behavior are you expecting?
A building app.
Steps to reproduce:
When I add --dev
to the build line in the package.json like:
"scripts": {
"ionic:build": "ionic-app-scripts build --dev",
ionic run android
works fine
insert any relevant code between the above and below backticks
Which @ionic/app-scripts version are you using?
0.0.46
Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
> ionic-app-scripts build
[16:05:12] ionic-app-scripts 0.0.46
[16:05:12] build prod started ...
[16:05:12] clean started ...
[16:05:12] clean finished in 7 ms
[16:05:12] copy started ...
[16:05:12] ngc started ...
[16:05:12] copy: Error copying "ionic-app/node_modules/ionic-angular/fonts"
to "ionic-app/www/assets/fonts"
[16:05:12] copy finished in 192 ms
[16:05:17] Error: Error encountered resolving symbol values statically. Function calls are not supported. Consider
replacing the function or lambda with a reference to an exported function, resolving symbol AppModule in
ionic-app/.tmp/app/app.module.ts, resolving symbol AppModule in
ionic-app/.tmp/app/app.module.ts
[16:05:17] ngc failed
[16:05:17] ionic-app-script task: "build"
[16:05:17] Error: Error
npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "ionic:build" "--"
npm ERR! node v6.7.0
npm ERR! npm v3.10.3
npm ERR! code ELIFECYCLE
npm ERR! myApp@0.0.1 ionic:build: `ionic-app-scripts build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the myApp@0.0.1 ionic:build script 'ionic-app-scripts build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the myApp package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! ionic-app-scripts build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs myApp
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls myApp
npm ERR! There is likely additional logging output above.
basvdijk commented
Turned out the problem was angular2-google-maps installed as 0.15.0 instead of 0.16.0. Installed 0.16.0 fixed the problem.