Activities of "Belen.molinaMA"

Thank you, everything is working correctly now.

One more question: Where can I find the backend logs generated by ABP? I would like to inspect runtime errors coming from the HttpApi.Host and the application layer.

Thank you — the checklist you provided resolved my issue for now. Running the DbMigrator first and aligning all connection strings fixed the inconsistent initialization and the missing admin/client records.

I have one additional question:

How should I properly regenerate the client-side proxies after creating a new application service?

In previous ABP versions I used commands like:

abp generate-proxy

or (for Angular)

abp generate-proxy -t ng

But I want to confirm the correct and recommended way in the current framework version, especially when using Angular + HttpApi.Host.

• Should I run the command from the Angular project folder or from the solution root?
• Are there any configuration steps required to make sure the new services appear in the proxy generator?
• How do I force regeneration if the proxy is not detecting new endpoints?

Thanks again for your help — your previous guidance was very useful.

Hello, I am working on an ABP project (version Pro - Team License). Yesterday everything worked perfectly: I created new entities, generated migrations, updated the database, ran the API, and both Swagger and the Angular UI loaded without issues. I could log in normally using the default admin user.

Today, after reopening the solution, the API behaves unexpectedly:

Swagger and the Angular logo no longer appear when running the API. It looks like the application is not initializing properly.

When I try to log in, I receive an error saying that the ClientId is missing, as if the default OpenIddict client was never seeded.

I tried dropping and recreating the database (using Update-Database):

Sometimes it works, sometimes it does not.

Most of the time, the default admin user is NOT created, which should happen during the DataSeeder execution.

I did not change anything related to authentication, database configuration, or appsettings between yesterday and today.

It seems like:

the DataSeeder is not being executed reliably,

or the project is not connecting to the database during startup,

or OpenIddict initialization is failing silently, causing the Client and admin user seeding to be skipped.

Could you help me understand why the initialization is inconsistent and why the default admin user and default clients are not being created when recreating the DB?

Thank you.