Hello,
Thank you for providing detailed information. In order to minimize the surface of the problem, could you first try to unplug both of your modules from the Host application and try to reproduce the problem? If the problem does not persist, can you add the modules one by one and try again so that we can understand which module or host application is causing the problem.
Hello,
Can you update abp.resourcemapping.js in the MyApp.Web project as follows and try again?
module.exports = {
aliases: {
},
mappings: {
"@node_modules/datatables.net/js": "@libs/datatables.net/js/"
}
};
Thank you too :)
I am waiting to hear from you, you can write here at any time.
The document mentioned during the meeting: https://abp.io/docs/latest/framework/architecture/multi-tenancy#change-the-current-tenant
If you are available, we can talk right now through this link: https://us04web.zoom.us/j/73615342418?pwd=QIVbN3sQWP4lZ324DtruyDEZkfDvXA.1
Hello,
Thank you for the detailed information. Interesting problem. Can you create a Blazor Web App project from scratch and add these modules there? If the problem occurs again, we can make sure that the problem is not in the Host project, so we can plug and unplug the modules and try again.
Also, are there any places in your host application or modules where you interfere with the cookie?
Hello,
If it is appropriate, you can send your sample application to support@abp.io with a text like below:
Please forward my mail to Berkan Sasmaz regarding ticket #8789.
Thank you for the information. There doesn't seem to be a problem with the URL. After detailed examination of your problem, I started to think that the problem might be related to Angular or even angular-oauth2-oidc library. Here are some reasons:
So I'm assigning the problem to a friend from the Angular team, who will help you if there is a problem on our side, and even try to suggest a workaround solution if possible.