Release 2025.4.0 · OpenEMS/openems

Hi @stefan.feilmeier,

I’m experiencing a problem with the UI in the new 2025.4.0 release. When starting the app, I’m getting the following error:

NullInjectorError: R3InjectorError(AppModule)[ApplicationInitStatus -> InjectionToken Application Initializer -> [object Object] -> NavigationService -> NavigationService]:
  NullInjectorError: No provider for NavigationService!
    at NullInjector.get (core.mjs:1621:27)
    at R3Injector.get (core.mjs:2148:33)
    at R3Injector.get (core.mjs:2148:33)
    at injectInjectorOnly (core.mjs:1116:32)
    at ɵɵinject (core.mjs:1122:60)
    at injectArgs (core.mjs:1253:23)
    at Object.factory (core.mjs:2374:52)
    at core.mjs:2271:47
    at runInInjectorProfilerContext (core.mjs:877:9)
    at R3Injector.hydrate (core.mjs:2270:21)

It seems Angular’s dependency injection system isn’t finding a provider for NavigationService. This might be due to the new version not registering the service correctly (for example, via providedIn: 'root' or in the module’s providers array), which then causes the APP_INITIALIZER to fail during bootstrapping.

Could the recent changes have inadvertently removed or misconfigured the provider for NavigationService? Any insights on whether this is an oversight or if there’s a new pattern for handling this dependency would be greatly appreciated.

Thanks!