ERROR in Error encountered resolving symbol values statically about angular

[kalyanram23]

i am having the same issue.

[Naren120]

I tried with all the latest release but no luck and I am not able to build my project with this.
is there a solution thats works well ?.

Is very important for me continue with the project, if the error continues i will have to migrate to another package.

[travist]

I will look into it, but need to figure out how to reproduce it. Are you using Angular CLI to build the project? I am working on this project over the weekend and may have resolution to this before the weekend is over. Thanks for your patience.

[Naren120]

@travist thanks for your response, yes I am using Angular CLI to build the project but I have resolved this issue by create new project and install this package first and then copy my all other functionality in new from existing project and build the project for now. And this is unbelievable that it is build successfully now I am not getting this error.
But still I don't know how this got fixed by this process. Is there any version clashing with other package or something else?
waiting for your response on this.
Thanks

Despite a lost weekend, we are still wrestling with this one. We are sticking as close to CLI as possible while incorporating several form.io approaches into our app. This following error was pervasive until we pruned our equivalent to the starter-app resource modules, after which we made considerable headway, only to have the problem resurface in auth.

ERROR in Error encountered resolving symbol values statically. Calling function 'FormioAuthRoutes', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol AuthModule in <snip>src/app/auth/auth.module.ts

Most of the chatter seems to be around AOT dependency on behalf of CLI, but haven't been able to wade through the finger pointing and tie it in. Problem is the same with ng build or ng serve.

Running out of alternatives for a workaround. Our use of angular-formio underlying services remains limited to documented approaches and starter-app implementations until we get stable.

current env:

		"@angular/common": "^4.4.0-RC.0",
		"@angular/compiler": "^4.4.0-RC.0",
		"@angular/core": "^4.4.0-RC.0",
		"@angular/forms": "^4.4.0-RC.0",
		"@angular/http": "^4.4.0-RC.0",
		"@angular/platform-browser": "^4.4.0-RC.0",
		"@angular/platform-browser-dynamic": "^4.4.0-RC.0",
		"@angular/router": "^4.4.0-RC.0",
		"angular-font-awesome": "^2.0.3",
		"angular-formio": "^1.0.1",
		"bootstrap-sass": "^3.3.7",
		"core-js": "^2.4.1",
		"firebase": "^4.3.0",
		"font-awesome": "^4.7.0",
		"formiojs": "^2.14.1",
		"jquery": "^3.2.1",
		"lodash": "^4.17.4",
		"rxjs": "^5.1.0",
		"tether": "^1.4.0",
		"zone.js": "^0.8.4"
	},
	"devDependencies": {
		"@angular/cli": "^1.3.2",
		"@angular/compiler-cli": "^4.4.0-RC.0",
		"@types/jasmine": "2.5.38",
		"@types/node": "~6.0.60",
		"angular2-load-children-loader": "^0.2.0",
		"codelyzer": "~2.0.0-beta.4",
		"es6-promise-loader": "^1.0.2",
		"formio-cli": "^0.5.4",
		"jasmine-core": "~2.5.2",
		"jasmine-spec-reporter": "~3.2.0",
		"karma": "~1.4.1",
		"karma-chrome-launcher": "~2.0.0",
		"karma-cli": "~1.0.1",
		"karma-coverage-istanbul-reporter": "^0.2.0",
		"karma-jasmine": "~1.1.0",
		"karma-jasmine-html-reporter": "^0.2.2",
		"protractor": "~5.1.0",
		"stylelint": "^8.1.1",
		"stylelint-config-sass-guidelines": "^3.1.0",
		"stylelint-scss": "^2.1.0",
		"ts-node": "~2.0.0",
		"tslint": "~4.4.2",
		"typescript": "^2.0.0"
	}

After digging around in angular-formio Demo dir a bit, I came across this little nugget. With AuthComponent being passed along in this way, all became well with FormioAuthRoutes.

export const authRoutes = FormioAuthRoutes({auth: AuthComponent});

[syed-asim]

@lookatmypinky can you please explain the workaround solution. really appreciate your help.

[roma-formio]

Closed due to no activity.