Unfortunately those are the only log entries that match the point in time.
I can see they are coming from here and occur directly after attempting to switch the language. I'd hoped the localization key "Abp.Authorization.Roles.RolePermissionSetting" might be a clue. Almost seems like it is trying to use localization entries (A permission name in this case) that do not exists.
Something I have not yet checked is the AbpAuditLogs table. I'll request access and provide more detail as soon as I can. If you have any other places you recommend I take a look I'd appreciate it.
I have just encounter this myself. Has any progress been made on this?
Cause
The problem seems to be caused by the service proxy being initialized before the API_BASE_URL has been set. This seems to cause a knockon effect on any other service proxy injected into a constructor. In practice this leads to all proxy calls going to undesireable domains and that is why nothing loads because the endpoints are invalid.
Source: service-proxies.ts:
export const API_BASE_URL = new InjectionToken<string>('API_BASE_URL');
Workaround I have found a workaround to this for now, but I don't know if this has severe side effects yet. On your ngRx Effect instead of injecting your service proxy in the constructor inject an Injector and for convenience use an accessor to keep your code the same.
I.e. Instead of
constructor(private actions$: Actions, private demoService: DemoServiceProxy) {}
use
get demoService(): DemoServiceProxy {
const { injector } = this;
return injector.get(DemoServiceProxy);
}
constructor(private actions$: Actions, private injector: Injector) {}
So it would seem that the latest version of aspnet-zero has a HomeController. This dictates the path which it will follow. One should keep in mind that Development, is subjective to the environment. Thus Development could also refer to a development server. Which in this cause, caused allot of issues, because it point to the wrong location (Ui/Login).
Got answered in PM