Angular proxy generation error #9043

icoretchi created 7 days ago

Template: microservice
Created ABP Studio Version: 0.9.25
Current ABP Studio Version: 0.9.25
Multi-Tenancy: Yes
UI Framework: angular
Theme: leptonx
Theme Style: system
Run Install Libs: Yes
Database Provider: ef
Database Management System: sqlserver
Mobile Framework: none
Public Website: No
Include Tests: Yes
Dynamic Localization: Yes
Kubernetes Configuration: Yes
Grafana Dashboard: Yes
Use Local References: No
Optional Modules:
- GDPR
- FileManagement
- TextTemplateManagement
- AuditLogging
- Chat
- OpenIddictAdmin

Hi,

I have the following issue when trying to generate proxies for angular:

PS D:\repos\projects\abc\apps\angular> abp generate-proxy -t ng -url http://localhost:44308 -m employeeQuery --target employee-query-service
[10:18:53 INF] You are running the second generation of the ABP CLI. If you're interested in the legacy CLI, see https://abp.io/new-cli
[Invalid Module] Backend module "employeeQueryService" does not exist in API definition.

I've studied all similar supporting tickets, but the issue still persist. And the interesting thing is that I have another almost similar service and it's perfectly working for it.

Beside you can see the the api definition that have the employeeQueryService:

Any ideas?

Thanks

EngincanV created 7 days ago

Support Team .NET Developer

Hi, https://abp.io/support/questions/8763/Issue-Creating-Proxies-8665#answer-3a18255f-5677-e4bf-a992-db36d7ae7d9c can you check this answer to see if it fixes your problem?

icoretchi created 7 days ago

sumeyye.kurtulus created 7 days ago

Support Team Angular Expert

Hello, I cannot produce the same problem on my end. If you could provide the steps for creating these services or share a minimal reproducible example, I can assist you further on that.

icoretchi created 7 days ago

Hi,

I've generated a new solution with Abp studio. The problem persist. I can share with you. Just let know how.

Cheers,

sumeyye.kurtulus created 7 days ago

Support Team Angular Expert

Hi,

I've generated a new solution with Abp studio. The problem persist. I can share with you. Just let know how.

Cheers,

Can you share the project via this email please sumeyye.kurtulus@volosoft.com

icoretchi created 7 days ago

I've send it.

sumeyye.kurtulus created 7 days ago

Support Team Angular Expert

Thank you for sending the project over. After reviewing it, I noticed an issue with the generated-proxy.json files. Specifically, the module name being used is incorrect. The system expects the module name to be orderquery, but it currently reads as orderQueryService.

Could you also confirm whether you used Suite to generate the code for the Orders entity? If so, I have observed an inconsistency between the Suite and Schematics command that needs to be addressed.

This issue will be resolved in the next release, but in the meantime, I recommend the following steps to resolve the problem:

Delete the existing generated-proxy.json file.
Run the same following command to regenerate the proxy with the correct module name:

abp generate-proxy -t ng -m orderquery -u http://localhost:44305 --target order-query-service

Once completed, the issue should be resolved. Please feel free to reach out if you need any further assistance or clarification.

icoretchi created 7 days ago

Hi,

Thanks. The issue has been resolved. So, the problem was in the generated-proxy.json, that was actually generated by abp studio, then the solution first time was created. I've always thought that this file is deleted each time we generate proxies.

Cheers,
Yulian

sumeyye.kurtulus created 6 days ago

Support Team Angular Expert

I’m glad to hear your issue has been resolved. Typically, generated-proxy.json is read and overridden each time proxies are generated. However, in cases where it persists, it may be helpful to verify the generation process within ABP Suite to ensure expected behavior.