Error encountered resolving symbol values statically... #258

morphatic · 2016-12-22T04:44:34Z

I just upgraded angular-cli and angular and now I'm getting a compile error when running ng serve:

ERROR in Error encountered resolving symbol values statically. Only initialized variables and
constants can be referenced because the value of this variable is needed by the template compiler
(position 79:22 in the original .ts file), resolving symbol AUTH_PROVIDERS in
/path/to/my/project/node_modules/angular2-jwt/angular2-jwt.d.ts, resolving symbol AppModule in
/path/to/my/project/src/app/app.module.ts, resolving symbol AppModule in
/path/to/my/project/src/app/app.module.ts

BTW, line 79 in angular2-jwt.d.ts reads:

export declare const AUTH_PROVIDERS: Provider[];

I'm using auth0-lock and followed the quickstart tutorial to get up and running.

Workaround 1

It turns out that I don't have any services explicitly using the AuthHttp class, so I just commented out the import { AUTH_PROVIDERS } from 'angular2-jwt'; and providers: [ AUTH_PROVIDERS ] lines from app.module.ts and this seems to fix the issue. Of course, then I have to manually set the Bearer jwt_token value in my Authorization header, but at least it works...

Workaround 2

If I use the alternative configuration approach with provideAuth, I don't get any errors. Here are the relevant bits from my app.module.ts file:

import { NgModule } from '@angular/core';
import { HttpModule, Http, RequestOptions } from '@angular/http';
import { provideAuth, AuthHttp, AuthConfig } from 'angular2-jwt';
import { AppComponent          } from './app.component';
// ... other import statements ...

export function authHttpServiceFactory(http: Http, options: RequestOptions) {
  return new AuthHttp( new AuthConfig({}), http, options);
}

@NgModule({
  declarations: [ AppComponent ],
  imports: [ HttpModule ],
  providers: [
    {
      provide: AuthHttp,
      useFactory: authHttpServiceFactory,
      deps: [ Http, RequestOptions ]
    }
  ],
  bootstrap: [ AppComponent ]
})
export class AppModule {}

Other Info

Here is my current system info:

~$ ng -v
angular-cli: 1.0.0-beta.24
node: 7.0.0
os: darwin x64
@angular/common: 2.4.1
@angular/compiler: 2.4.1
@angular/core: 2.4.1
@angular/forms: 2.4.1
@angular/http: 2.4.1
@angular/platform-browser: 2.4.1
@angular/platform-browser-dynamic: 2.4.1
@angular/router: 3.4.1
@angular/compiler-cli: 2.4.1

I'm using auth0-lock: 10.7.3, angular2-jwt: 0.1.27, and typescript v2.2.0-dev.20161218. Thanks for such great tools!!!

The text was updated successfully, but these errors were encountered:

chenkie · 2016-12-22T15:30:53Z

Thanks for the info @morphatic, we're looking into that error now.

fiveone7 · 2016-12-30T08:42:07Z

I've got the same issue.

angular-cli: 1.0.0-beta.22-1
node: 6.9.2
os: win32 x64

@angular/common": "^2.2.3
@angular/compiler": "^2.2.3
@angular/core": "^2.2.3
@angular/forms": "^2.2.3
@angular/http": "^2.2.3
@angular/material": "^2.0.0-alpha.11-3
@angular/platform-browser": "^2.2.3
@angular/platform-browser-dynamic": "^2.2.3
@angular/router": "^3.2.3

angular2-jwt": "^0.1.26
auth0-lock": "^10.7.2

thehashrocket · 2016-12-31T01:22:56Z

I think this might be related to this issue.

nguyenminhtu · 2016-12-31T10:51:38Z

tks

the-ult · 2017-01-01T13:50:16Z

@chenkie any news on the update to rxjs 5.0x and compatibility with angular 2.4?

byteofsilicon · 2017-01-07T12:49:39Z

I am encountering this same issue.

bkarv · 2017-01-08T04:47:38Z

Upgraded to Angular CLI to latest today. I get the same error.

jonigl · 2017-01-12T13:51:31Z

Here I have the same error.

"version": "1.0.0-beta.24"
"angular2-jwt": "^0.1.25"

escardin · 2017-01-12T14:14:14Z

Try with the newly released 0.1.28. It resolves issues with rxjs versions. I ran the cli and didn't get any compile errors on the project when I ran it, but I don't think I've resolved AOT issues yet. I'm working on getting my large angular project upgraded to latest so I can make sure issues are resolved.

jonigl · 2017-01-12T14:27:49Z

Thanks @escardin I tried the version that you mentioned (0.1.28) but unfortunately I continue with the same error.
I am using the latest version of rxjs.
Now Im using:

"version": "1.0.0-beta.24"
"angular2-jwt": "^0.1.28"
"rxjs": "^5.0.3"

This is my current system info:

angular-cli: 1.0.0-beta.24
node: 6.9.4
os: darwin x64
@angular/common: 2.4.3
@angular/compiler: 2.4.3
@angular/core: 2.4.3
@angular/forms: 2.4.3
@angular/http: 2.4.3
@angular/platform-browser: 2.4.3
@angular/platform-browser-dynamic: 2.4.3
@angular/router: 3.4.3
@angular/compiler-cli: 2.4.3

thehashrocket · 2017-01-12T16:57:17Z

Yep, 0.1.28 didn't fix the issue that lead to this error:

ERROR in Error encountered resolving symbol values statically. Only initialized variables and
constants can be referenced because the value of this variable is needed by the template compiler
(position 79:22 in the original .ts file), resolving symbol AUTH_PROVIDERS in
/path/to/my/project/node_modules/angular2-jwt/angular2-jwt.d.ts, resolving symbol AppModule in
/path/to/my/project/src/app/app.module.ts, resolving symbol AppModule in
/path/to/my/project/src/app/app.module.ts

escardin · 2017-01-12T17:10:31Z

Yeah you can't use AUTH_PROVIDERS with AOT afaik.

chenkie · 2017-01-12T17:14:00Z

The snippet above is the way to do it for now until the angular2-jwt @NgModule is ready.

export function authHttpServiceFactory(http: Http, options: RequestOptions) {
  return new AuthHttp( new AuthConfig({}), http, options);
}

@NgModule({
  declarations: [ AppComponent ],
  imports: [ HttpModule ],
  providers: [
    {
      provide: AuthHttp,
      useFactory: authHttpServiceFactory,
      deps: [ Http, RequestOptions ]
    }
  ],
  bootstrap: [ AppComponent ]
})
export class AppModule {}

memark · 2017-01-17T08:28:07Z

Just FWIW, the problem with AUTH_PROVIDERS is not related (only) to AOT. Even with AOT disabled, angular-cli still does some static analysis, which gives the same error.

@chenkie Any idea when the mentioned @NgModule might be ready?

escardin · 2017-01-17T14:18:25Z

It's there, you can try it. It's not documented because it's not tested. The additional output from running ngc isn't published either.

idl-shaohua · 2017-01-18T03:02:13Z

I ran into this issue too.

    "angular2-jwt": "^0.1.28"
    "angular-cli": "1.0.0-beta.25.5",

    "@angular/common": "^2.3.1",
    "@angular/compiler": "^2.3.1",
    "@angular/core": "^2.3.1",
    "@angular/forms": "^2.3.1",
    "@angular/http": "^2.3.1",
    "@angular/platform-browser": "^2.3.1",
    "@angular/platform-browser-dynamic": "^2.3.1",
    "@angular/router": "^3.3.1",

omarsallah00 · 2017-01-27T12:08:53Z

Thanks @chenkie you have saved my day

laterbreh · 2017-02-10T05:58:41Z

I wanted to also comment that I was getting this issue as well using the angular-cli:

"devDependencies": {
    "@angular/cli": "1.0.0-beta.30",
    "@angular/compiler-cli": "^2.3.1",
    "@types/jasmine": "2.5.38",
    "@types/node": "^6.0.42",
    "codelyzer": "~2.0.0-beta.1",
    "jasmine-core": "2.5.2",
    "jasmine-spec-reporter": "2.5.0",
    "karma": "1.2.0",
    "karma-chrome-launcher": "^2.0.0",
    "karma-cli": "^1.0.1",
    "karma-jasmine": "^1.0.2",
    "karma-remap-istanbul": "^0.2.1",
    "protractor": "~4.0.13",
    "ts-node": "1.2.1",
    "tslint": "^4.3.0",
    "typescript": "~2.0.3"
  }

and

"angular2-jwt": "^0.1.28"

Was resolved using @morphatic's solutions.

fiveone7 · 2017-02-20T15:59:32Z

Thank you. -_-

Kunepro · 2017-03-23T10:42:04Z

Add me to the list.
I got it to work removing AUTH_PROVIDERS like @morphatic suggested, but I would love to have this fixed.

  "devDependencies": {
    "@angular/cli": "^1.0.0-rc.2",
    "@angular/compiler-cli": "^2.3.1",
    "@types/jasmine": "2.5.38",
    "@types/node": "^6.0.42",
    "codelyzer": "~2.0.0-beta.1",
    "jasmine-core": "2.5.2",
    "jasmine-spec-reporter": "2.5.0",
    "karma": "1.2.0",
    "karma-chrome-launcher": "^2.0.0",
    "karma-cli": "^1.0.1",
    "karma-jasmine": "^1.0.2",
    "karma-remap-istanbul": "^0.2.1",
    "protractor": "~4.0.13",
    "ts-node": "1.2.1",
    "tslint": "^4.3.0",
    "typescript": "~2.0.3"
  }

vinicius · 2017-06-21T14:44:44Z

Thank you, @morphatic ! I was struggling with this issue for hours. I tried the Workaround 2 and it worked well.

robertsattler · 2017-09-26T06:25:46Z

Same issue. Thank you @morphatic, Workaround 2 works great.

  "dependencies": {
    "@angular/core": "^4.2.4",
    "angular2-jwt": "^0.2.3",
    // ...
  },
  "devDependencies": {
    "@angular/cli": "1.4.1",

stale · 2019-10-26T05:29:46Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you have not received a response for our team (apologies for the delay) and this is still a blocker, please reply with additional information or just a ping. Thank you for your contribution! 🙇‍♂️

chenkie mentioned this issue Dec 22, 2016

AuthHttp don't have token in the ahthorization header? #241

Closed

bytesfromali mentioned this issue Jan 3, 2017

ERROR in Error encountered resolving symbol values statically - Angular CLI dschnelldavis/angular2-json-schema-form#7

Closed

escardin added the question label Jan 3, 2017

Invis1ble mentioned this issue Jan 14, 2017

Fix jwt module compiling errors Invis1ble/assistant-client#50

Closed

jorgeriv mentioned this issue Jan 20, 2017

Can't resolve all parameters for AuthConfig #121

Closed

kuuurt13 mentioned this issue Feb 22, 2017

Issues with AOT Compiler in Angular CLI kuuurt13/ng-block-ui#1

Closed

stale bot added the closed:stale Issue or PR has not seen activity recently label Oct 26, 2019

stale bot closed this as completed Nov 2, 2019

Error encountered resolving symbol values statically... #258

Error encountered resolving symbol values statically... #258

Comments

morphatic commented Dec 22, 2016

Workaround 1

Workaround 2

Other Info

chenkie commented Dec 22, 2016

Uh oh!

fiveone7 commented Dec 30, 2016

Uh oh!

thehashrocket commented Dec 31, 2016

Uh oh!

nguyenminhtu commented Dec 31, 2016

Uh oh!

the-ult commented Jan 1, 2017

Uh oh!

byteofsilicon commented Jan 7, 2017

Uh oh!

bkarv commented Jan 8, 2017

Uh oh!

jonigl commented Jan 12, 2017

Uh oh!

escardin commented Jan 12, 2017

Uh oh!

jonigl commented Jan 12, 2017

Uh oh!

thehashrocket commented Jan 12, 2017

Uh oh!

escardin commented Jan 12, 2017

Uh oh!

chenkie commented Jan 12, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

memark commented Jan 17, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

escardin commented Jan 17, 2017

Uh oh!

idl-shaohua commented Jan 18, 2017

Uh oh!

omarsallah00 commented Jan 27, 2017

Uh oh!

laterbreh commented Feb 10, 2017

Uh oh!

fiveone7 commented Feb 20, 2017

Uh oh!

Kunepro commented Mar 23, 2017

Uh oh!

vinicius commented Jun 21, 2017

Uh oh!

robertsattler commented Sep 26, 2017

Uh oh!

stale bot commented Oct 26, 2019

Uh oh!

chenkie commented Jan 12, 2017 •

edited

Loading

memark commented Jan 17, 2017 •

edited

Loading