The reply from the AI-Bot cannot solve the issue.
Cli command:
abp new Acme.BookStore -t app-pro -u angular
Access login connect/token
Shell command:
curl --location --request POST 'http://localhost:44372/connect/token' \
--header 'Accept-Language: zh-Hans' \
--header '__tenant: demo' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--header 'Host: localhost:44372' \
--header 'Connection: keep-alive' \
--data-urlencode 'grant_type=password' \
--data-urlencode 'client_id=BookStore_App' \
--data-urlencode 'scope=BookStore' \
--data-urlencode 'username=admin' \
--data-urlencode 'password=1q2w3E*'
Exception reponse content:
<html lang="zh-Hans">
<head>
<meta charset="utf-8" />
<title>&#x672A;&#x627E;&#x5230;&#x79DF;&#x6237;&#xFF01;</title>
</head>
<body>
<h3>&#x672A;&#x627E;&#x5230;&#x79DF;&#x6237;&#xFF01;</h3>
<p>&#x6CA1;&#x6709;&#x79DF;&#x6237;&#x7684; ID
&#x6216;&#x540D;&#x79F0;&#x4E3A;&#xFF1A;demo&#x7684;&#x79DF;&#x6237;&#x3002;
<p />
</body>
</html>
It has been discovered that this issue only applies to 'Accept-Language: zh-Hans'
.
This is a normal response request.:
curl --location --request POST 'http://localhost:44372/connect/token' \
--header 'Accept-Language: en' \
--header '__tenant: demo' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--header 'Host: localhost:44372' \
--header 'Connection: keep-alive' \
--data-urlencode 'grant_type=password' \
--data-urlencode 'client_id=BookStore_App' \
--data-urlencode 'scope=BookStore' \
--data-urlencode 'username=admin' \
--data-urlencode 'password=1q2w3E*'
Reponse content:
<html lang="en">
<head>
<meta charset="utf-8" />
<title>Tenant not found!</title>
</head>
<body>
<h3>Tenant not found!</h3>
<p>There is no tenant with the tenant id or name: demo
<p />
</body>
</html>
The commercial and the community are different.
Community version response content:
{
"error": {
"code": "Volo.AbpIo.MultiTenancy:010001",
"message": "An internal error occurred during your request!",
"details": null,
"data": {},
"validationErrors": null
}
}
I think the response content of the community is correct.
How to temporarily fix the problem of character encoding errors in the commercial ? How can my response content be adjusted to be the same as that of the community?
Hi Angular team,
Cli command
abp new Acme.BookStore -u angular -t app-pro -theme lepton --old
Press F5 to refresh and then return to English
Also, this issue doesn't work even with the latest Volo.Abp.Studio.Cli
. I need to adjust app.module.ts
using cli command:
abp new Acme.BookStore -u angular -t app-pro -theme lepton
Has same issue. The InternetConnectionStatusComponent
is missing.
I created a new project and imported the "InternetConnectionStatusComponent" component. The entire process ran smoothly. However, the current problem lies in the template of the created project. It should not have been missing the import.
Including references like InternetConnectionStatusComponent ensures essential functionality—such as monitoring internet connectivity—is available out of the box. It promotes reusability and improves user experience, but can be removed if not needed.
What I mean is, why does the project you created automatically import the InternetConnectionStatusComponent, while mine doesn't have this import?
Why did you create the template with references?
import {
InternetConnectionStatusComponent,
} from '@abp/ng.theme.shared';
Node version: 22.17.0 Yarn version: 4.9.2 Npm version 10.9.2
I see that this import is missing for InternetConnectionStatusComponent, you will need to add this import to your app.module.ts
According to your method, I encountered a new problem.
./node_modules/@abp/ng.core/fesm2022/abp-ng.core-locale.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\@abp\ng.core\fesm2022'
./node_modules/@abp/ng.core/fesm2022/abp-ng.core.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\@abp\ng.core\fesm2022'
./node_modules/@abp/ng.oauth/fesm2022/abp-ng.oauth.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\@abp\ng.oauth\fesm2022'
./node_modules/@angular/common/fesm2022/common.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\@angular\common\fesm2022'
./node_modules/@angular/common/fesm2022/http.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\@angular\common\fesm2022'
./node_modules/@angular/core/fesm2022/core.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\@angular\core\fesm2022'
./node_modules/@floating-ui/core/dist/floating-ui.core.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\@floating-ui\core\dist'
./node_modules/@floating-ui/dom/dist/floating-ui.dom.browser.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\@floating-ui\dom\dist'
./node_modules/@volo/abp.ng.account/fesm2022/volo-abp.ng.account-admin-config.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\@volo\abp.ng.account\fesm2022'
./node_modules/@volo/abp.ng.account/fesm2022/volo-abp.ng.account-admin.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\@volo\abp.ng.account\fesm2022'
./node_modules/@volo/abp.ng.account/fesm2022/volo-abp.ng.account-public.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\@volo\abp.ng.account\fesm2022'
./node_modules/@volo/abp.ng.identity/fesm2022/volo-abp.ng.identity-config.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\@volo\abp.ng.identity\fesm2022'
./node_modules/@volo/abp.ng.identity/fesm2022/volo-abp.ng.identity.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\@volo\abp.ng.identity\fesm2022'
./node_modules/@volo/abp.ng.saas/fesm2022/volo-abp.ng.saas.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\@volo\abp.ng.saas\fesm2022'
./node_modules/@volo/ngx-lepton-x.core/fesm2022/volo-ngx-lepton-x.core.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\@volo\ngx-lepton-x.core\fesm2022'
./node_modules/@volosoft/ngx-lepton-x/fesm2022/volosoft-ngx-lepton-x.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\@volosoft\ngx-lepton-x\fesm2022'
./node_modules/angular-oauth2-oidc/fesm2022/angular-oauth2-oidc.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\angular-oauth2-oidc\fesm2022'
./node_modules/angularx-qrcode/fesm2022/angularx-qrcode.mjs:1:0-155 - Error: Module not found: Error: Can't resolve 'F:/abp-demo/angular/node_modules/@angular-devkit/build-angular/node_modules/@babel/runtime/helpers/esm/asyncToGenerator.js' in 'F:\abp-demo\angular\node_modules\angularx-qrcode\fesm2022'
** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
× Failed to compile.
I think you and I are not using the same template.
Cli:
abp new Acme.BookStore -u angular -t app-pro
Try this and you can reproduce it.