Activities of "maliming"

Great : )

hi

Use Volo.Abp.Account.Pro.Public.XXX, and update the module name in depend on attributes.

<PackageReference Include="Volo.Abp.Account.Pro.Public.Application" Version="8.3.2" />
<PackageReference Include="Volo.Abp.Account.Pro.Public.HttpApi" Version="8.3.2" />

hi

The confusion here is how to handle or set the permissions from this post request at the mobile side. Do we need to return the token from the post request and use it every time or we need to simply call application-configuration method with userid/mobilenumber from the mobile app?

This is based on your authentication scheme.

Cookies or JWT token?

You should attach the cookie and jwt token in HTTP request headers.

hi

I need to reproduce your problem in some way to find the cause. From the information you shared, I don't have any ideas at the moment.

hi

They are now pro.

<PackageReference Include="Volo.Abp.Account.Application" Version="8.3.2" />
<PackageReference Include="Volo.Abp.Account.HttpApi" Version="8.3.2" />

hi

The logs related to WatchChanges

You can Override the BundleManager to remove the WatchChanges and check the logs again.

hi

You should use the integration services to communicate in microservices.

See https://abp.io/docs/8.2/guides/interservice-communication https://abp.io/docs/latest/framework/api-development/integration-services https://abp.io/docs/latest/tutorials/modular-crm/part-06

hi

Please replace all open-source Account modules with the commercial Account.Pro modules.

Check all csproj files of your solution to see the package reference.

Thanks.

hi

I have confirmed. You can use the tiered option in the next Studio version. I have also refunded your ticket.

Thanks.

hi

Can you share a minimal project to reproduce your problem?

liming.ma@volosoft.com

Thanks.