5

I've been trying to switch my app over to AoT compilation and have been getting this error in the production environment when the app is loading (it works fine locally).

Error: Can't resolve all parameters for IconService: (?, ?)

it seems like the error is coming from on the modules that is providing the IconService. The icons services constructor looks like

constructor(private http:Http, private iconConfiguror:IconConfiguror) {

So my question is what does this error mean and why would it happen in the prod environment only (I've tried enabling prod mode locally)?

It seems like it means that the http and icon configuration parameters aren't provided, but the icon config is provided at the app module level and the HttpModule is imported in the IconModule where the IconService is provided.

@NgModule({ imports: [ CommonModule, HttpModule, ], declarations: [ IconComponent, ], exports: [ IconComponent, ], providers: [ IconService, __platform_browser_private__.BROWSER_SANITIZATION_PROVIDERS, ], })

And the barrel for our icon component.

export * from "./components/icon/icon.configuror"; export * from "./components/icon/icon.service.provider"; export * from "./components/icon/icon.service"; export * from "./components/icon/icon.component"; export * from "./components/icon/icon.module";
Improve this question
8
  • constructor(private http:Http, private iconConfiguror:IconConfiguror) Commented Feb 23, 2017 at 20:06
  • 1
    @AJT_82 forgot to update that, I did try that as well. Commented Feb 23, 2017 at 20:08
  • The __decorate is correct, they should not be injected there. How are you providing the IconConfiguror service? Commented Feb 23, 2017 at 20:15
  • @altschuler In the app.module {provide: IconConfiguror, useClass: IconConfigurorImpl},. And the IconConfigurorImpl itself @Injectable() export class IconConfigurorImpl extends IconConfiguror { Commented Feb 23, 2017 at 20:22
  • Are you using barrels? Commented Feb 23, 2017 at 22:48

6 Answers 6

Reset to default
6

Fixed this by providing the IconService in a different way.

 { provide: IconService, useFactory: iconServiceFactory, deps: [Http, IconConfiguror], },

and the factory itself

export function iconServiceFactory(http: Http, iconConfiguror: IconConfiguror) { return new IconService(http, iconConfiguror); }

I guess for some reason the Http wasn't being provided (even though HttpModule was imported) so I had to declare it as a dependency.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

5

One possible cause of this error is if you are not decorating your IconService class with @Injectable(). If that is the cause, adding that decoration above the class declaration will fix the error.

Improve this answer

Comments

2

I have encountered similar problem. I solved it by changing export order in the barrel.

Basic service files:

// dependency.service.ts @Injectable() export class DependencyService { } // dependant.service.ts import { DependencyService } from '.'; @Injectable() export class DependantService { constructor(private dependency: DependencyService) { } }

Following barrel causes the error:

// index.ts export * from './dependant.service'; export * from './dependency.service';

While following one works:

// index.ts export * from './dependency.service'; export * from './dependant.service';
Improve this answer

2 Comments

I just have experienced this issue, and I wonder if you know why it happens ?
@JacquesCornat I haven't investigated on it. At least I find logical that dependency order must be correct. However, I suspect how decorators are process.
1

Sometimes is single way to fix it - manually describe parameters.

static get parameters() { return [Http, IconConfiguror] } constructor(private http:Http, private iconConfiguror:IconConfiguror) {
Improve this answer

Comments

0

Worked for me when I used following while importing the Service in app.module.ts

{provide: AuthService, depends: HttpClientModule}
Improve this answer

Comments

0

My issue was that I was inheriting from a base class, and I had decorated that base class with @Injectable. The inheriting class was the class that should have the @Injectable attribute, not the base class. It seems that when the compiler sees the @Injectable attibute, it checks to make sure all the properties in the constructor can be injected. If not, it's an error. I solved it by removing the @Injectable attibute from that class.

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.