Angular proxies error #9953

yazilim.ithinka created 13 hours ago

Template: microservice
Created ABP Studio Version: 1.3.2
Current ABP Studio Version: 1.3.2
Multi-Tenancy: Yes
UI Framework: angular
Theme: leptonx
Theme Style: system
Theme Menu Placement: side
Run Install Libs: Yes
Database Provider: ef
Database Management System: postgresql
Mobile Framework: react-native
Public Website: Yes
Social Login: Yes
Include Tests: Yes
Dynamic Localization: Yes
Kubernetes Configuration: Yes
Grafana Dashboard: Yes
Use Local References: No
Aspire: No
Optional Modules:
- GDPR
- FileManagement
- TextTemplateManagement
- AuditLogging
- OpenIddictAdmin
Selected Languages: English, Turkish
Default Language: English
Create Command: abp new AbpSolution1 -t microservice --ui-framework angular --mobile react-native --database-provider ef --database-management-system postgresql --theme leptonx --skip-migrator --public-website --without-cms-kit --dont-run-bundling -no-language-management -file-management

Hello

We are creating a new microservice project, then running it to ensure it works. Next, we add the ManagementService microservice to our project and build it to ensure it works. We then run our project to ensure it runs without errors. After that, we create the Products table in ManagementService via AbpSuite.
Here, we see that the Generating proxies section shows 0 ms. After checking, we see that files like entity appService have been created on the ManagementService backend side, but when we check the projects folder in Angular, we only see the abp -solution1 folder created during the project's initial stage. We did not see any folder or file related to management-service. Similarly, we did not see any files related to the products table we added via AbpSuite. Consequently, we have no access to any products table in the panel! I would like to mention that we also followed the steps in the readme files provided after creating the project, such as generate-proxy.

We did not encounter this issue in our samples a few updates ago. Could you please advise us on the areas we should check?

Thanks.

AI-Bot created 13 hours ago

Support Team ABP Agent

The issue where "Generating proxies" completes in 0 ms and no Angular proxy files are created for your new microservice (ManagementService) is typically caused by one of the following:

The Angular project is not properly configured to recognize the new microservice for proxy generation.
The ABP CLI is not targeting the correct Angular project or cannot resolve the backend API definition.
The required configuration in angular.json, environment.ts, or tsconfig.base.json is missing or incorrect for the new service.

Steps to Check and Resolve:

Verify Angular Project Configuration:
- Ensure your angular.json includes the correct projects and that the default project is set if you have multiple Angular projects.
- Make sure the projects folder in your Angular solution contains the expected structure for each microservice UI.
Check environment.ts:
- In your Angular app's src/environments/environment.ts, ensure the apis section includes an entry for your new microservice, e.g.:

apis: {
       default: {
         url: 'https://localhost:44300',
         rootNamespace: 'AbpSolution1'
       },
       managementService: {
         url: 'https://localhost:44301',
         rootNamespace: 'ManagementService'
       }
     }

The rootNamespace should match the backend namespace.

Update tsconfig.base.json:
- Add or update the proxy import paths:

"paths": {
       "@proxy": ["src/app/proxy/index.ts"],
       "@proxy/*": ["src/app/proxy/*"]
     }

Run Proxy Generation Manually:
- Open a terminal in your Angular project root and run:

abp generate-proxy -t ng

If you have multiple Angular projects, specify the project:

abp generate-proxy -t ng --project <your-angular-project-name>

If prompted for backend module or API name, use the correct values (e.g., managementService).

Check for Errors:
- If the command completes instantly or with errors, check for missing or misconfigured @abp/ng.schematics package, or missing backend API endpoints.
Restart Backend and Angular Apps:
- Ensure all backend services are running and accessible before generating proxies.
Review Documentation and Known Issues:
- See the official docs and support threads for troubleshooting:

If the above steps do not resolve the issue, double-check that your backend ManagementService exposes its API definition endpoint and that the Angular app can reach it.

Sources:

This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.