Hello,
Thank you for yor kind interest and contribution. As you have also explained the server treats tenant timezone as DST‑aware. However, The Angular pipe is the only place that forces “standard offset only” for display when an IANA zone like US/Pacific is set intentionally.
So, changing the pipe to use DST‑aware formatting by default (e.g. by calling format() instead of formatDateWithStandardOffset()) would align with the server and with user expectations for IANA zones and would fix the “one hour behind after DST” issue.
You can also consider contributing a backward-compatible change (e.g. an optional parameter on abpUtcToLocal to use DST-aware formatting, or a dedicated DST-aware pipe). You can find details in this contribution guide.
You can let us know if you need further assistance. Thank you for your cooperation.
If you encounter an error similar to the following:
// root_effect_scheduler.mjs:3637
❌ ERROR ɵNotFound: NG0201: No provider found for `InjectionToken CORE_OPTIONS`. Find more at https://v20.angular.dev/errors/NG0201
as also mentioned here, you can resolve the issue by adding the following resolutions to your package.json:
"resolutions": {
"@ng-bootstrap/ng-bootstrap": "~19.0.0",
"@volo/abp.commercial.ng.ui": "~10.0.3",
"@volo/abp.ng.account": "~10.0.3"
}
https://gist.github.com/sumeyyeKurtulus/6111671cf4f1773c1b8c1f354631087a
I am getting such error after updating my version to 10.0.x.
// root_effect_scheduler.mjs:3637
❌ ERROR ɵNotFound: NG0201: No provider found for `InjectionToken CORE_OPTIONS`. Find more at https://v20.angular.dev/errors/NG0201
Hello again,
I apologize for overlooking the project in your original question. After reviewing the project you shared, I noticed that some paths in the tsconfig.json file redirect to node_modules. This approach is no longer supported. You can find more details here:
https://abp.io/community/articles/angular-library-linking-made-easy-paths-workspaces-and-5z2ate6e#how-path-references-worked-before-the-new-angular-application-builder
/* To learn more about this file see: https://angular.io/config/tsconfig. */
{
"compileOnSave": false,
"compilerOptions": {
// ...
"paths": {
"product-service": ["src/product-service/public-api.ts"]
// "@abp/*": ["node_modules/@abp/*"],
// "@volo/*": ["node_modules/@volo/*"]
},
"useDefineForClassFields": false
},
}
I also noticed that some package versions are not aligned. In particular, the Angular-related packages and the TypeScript version should match specific compatible versions. Unless you have a specific reason to use different versions, I recommend aligning them as follows:
{
"name": "angular-starter",
"private": true,
"engines": {
"node": "^22.0.0"
},
//...
"resolutions": {
"@ng-bootstrap/ng-bootstrap": "~19.0.0",
"@volo/abp.commercial.ng.ui": "~10.0.3",
"@volo/abp.ng.account": "~10.0.3"
},
"dependencies": {
"@abp/ng.components": "~10.0.3",
"@abp/ng.feature-management": "~10.0.3",
"@abp/ng.core": "~10.0.3",
"@abp/ng.oauth": "~10.0.3",
"@abp/ng.setting-management": "~10.0.3",
"@abp/ng.tenant-management": "~10.0.3",
"@abp/ng.theme.shared": "~10.0.3",
"@abp/ng.theme.lepton-x": "~5.0.3",
"@angular/animations": "~20.0.0",
"@angular/common": "~20.0.0",
"@angular/compiler": "~20.0.0",
"@angular/core": "~20.0.0",
"@angular/forms": "~20.0.0",
"@angular/localize": "~20.0.0",
"@angular/platform-browser": "~20.0.0",
"@angular/platform-browser-dynamic": "~20.0.0",
"@angular/router": "~20.0.0",
//...
"@volo/abp.commercial.ng.ui": "~10.0.3",
"@volo/abp.ng.account": "~10.0.3",
"@volo/abp.ng.audit-logging": "~10.0.3",
"@volo/abp.ng.chat": "~10.0.3",
"@volo/abp.ng.file-management": "~10.0.3",
"@volo/abp.ng.gdpr": "~10.0.3",
"@volo/abp.ng.identity": "~10.0.3",
"@volo/abp.ng.language-management": "~10.0.3",
"@volo/abp.ng.openiddictpro": "~10.0.3",
"@volo/abp.ng.saas": "~10.0.3",
"@volo/abp.ng.text-template-management": "~10.0.3",
"@volosoft/abp.ng.theme.lepton-x": "~5.0.3",
//...
},
"devDependencies": {
"@abp/ng.schematics": "~10.0.3",
"@angular/build": "~20.0.0",
"@angular-eslint/builder": "~20.0.0",
"@angular-eslint/eslint-plugin": "~20.0.0",
"@angular-eslint/eslint-plugin-template": "~20.0.0",
"@angular-eslint/schematics": "~20.0.0",
"@angular-eslint/template-parser": "~20.0.0",
"@angular/cli": "~20.0.0",
"@angular/compiler-cli": "~20.0.0",
"@angular/language-service": "~20.0.0",
"@types/file-saver": "^2.0.7",
"@types/jasmine": "~3.6.0",
"@types/jszip": "^3.4.0",
"@types/node": "^20.17.16",
"@typescript-eslint/eslint-plugin": "^8.50.0",
"@typescript-eslint/parser": "^8.50.0",
//...
"typescript": "~5.8.0"
}
}
Hello,
Thank you for explaining the issue in detail. It may be related to a misconfigured installation. Could you add the following resolutions to your package.json and try reinstalling?
"resolutions": {
"@ng-bootstrap/ng-bootstrap": "~19.0.0",
"@volo/abp.commercial.ng.ui": "~10.0.3",
"@volo/abp.ng.account": "~10.0.3"
},
You can let us know if you need further assistance. Thank you for your cooperation.
Hello,
Thank you for reaching out again. If you could provide an e-mail address and a target version, I can send the source code for this package.
Thank you for your cooperation.
Hello,
This behavior was implemented intentionally for the file property type. However, we’ve identified a minor bug that will be addressed in the next patch release. In the meantime, you can either update the templates or apply a manual fix to the generated code.
If you choose to modify the templates, please follow the steps below: https://abp.io/docs/latest/suite/editing-templates
// Frontend.Angular.__name@kebab__.component.html.template
name="{{ '<%= resourceName %>::<%= prop.formControl === 'file' ? removePostfix(prop.name, 'Id') : prop.name %>' | abpLocalization }}"
// Frontend.Angular.__name@kebab__-child.component.html.template
name="{{ '<%= resourceName %>::<%= prop.formControl === 'file' ? removePostfix(prop.name, 'Id') : prop.name %>' | abpLocalization }}"
I will also process a refund for this ticket. Thank you for your cooperation.
I understand the issue, and thank you for trying again. Could you please also try unchecking the “Run the initial tasks" option while creating the project and see if that helps?
Thank you again. I understand the problem and the inconvenience this situation is causing. Could you try creating an application with a different UI option to test whether a similar problem occurs? I also suggest following the creation process in an IDE or file explorer to see whether the files are created and then deleted.
Yes, I have just checked your solution and identified that there are more files missing as it seems.
The missing files are likely being silently deleted by Windows Defender's Controlled Folder Access. It blocks unauthorized apps from writing certain file types — which explains why hundreds of files are created fine but specific ones like angular.json, package.json, app.config.ts, and app.routes.ts are missing.
To confirm: Open Windows Security → Virus & threat protection → Protection history and check for blocked write actions around the time you ran the abp new command.
To fix:
The KubernetesProfileInfoLoader crash is a secondary issue — ABP Studio is failing to load because those JSON files are missing, corrupting the solution state.
