I did the above steps. when i run it on expo it just shows a loading screen
Could you share some screenshots?
Hi,
It's better if you share project with me, I can check it in depth.
Hi,
Will this fix also work if we are still using abp 8.3.X but need to update our Swashbuckle.AspNetCore to 6.8.1?
Nope.
The problem will fixed in the 9.0.x version.
It looks like we're missing the forLazy() call from our module import, but it seems that's something we need to manually create on our modules and just looking at your link, I don't understand how to create this (in explanation, I don't understand what's happening in the forChild() call).
Not related to this, forlazy
is used to configure some services.
Could you please share a test project with me? i will check it. thanks shiwei.liang@volosoft.com
Hi,
You can consider using the appsettings
{
"Hangfire": {
"Provider" : "in-memory"
}
}
{
"Hangfire": {
"Provider" : "postgreSql"
}
}
private void ConfigureHangfire(ServiceConfigurationContext context)
{
var configuration = context.Services.GetConfiguration();
context.Services.AddHangfire(config =>
{
if(configuration["Hangfire:Provider"] == "in-memory")
{
....
}
....
});
Configure(options =>
{
options.ServerOptions = new BackgroundJobServerOptions() { WorkerCount = 3 };
});
}
If I change the endpoint on the external system side to [AllowAnonymous] , the current User is empty, but the tenant is identified.
if you need current user info, don't use [AllowAnonymous]
Could you share the full logs? thanks.