DbMigrator also uses IConfiguration , see https://github.com/abpframework/abp/blob/dev/templates/app/aspnet-core/src/MyCompanyName.MyProjectName.DbMigrator/DbMigratorHostedService.cs#L15
But ConnectionString is a special config! DbMigrator designed to be worked in distributed environments. So if your tenants have its own database then it gets the ConnectionString from database.
See https://github.com/abpframework/abp/blob/dev/templates/app/aspnet-core/src/MyCompanyName.MyProjectName.Domain/Data/MyProjectNameDbMigrationService.cs#L66
Try to read another appsettings.json value
toastui-editor is a 3rd party tool and it's out of support. could you pls ask it on its own repo?
can you explain how did you solve tempkey.jwk problem? can you run the tests in Release mode? (this will filter down to some solution)
you can reopen if your issue continues...
the patch release 4.4.1 will be released next week. @maliming is this issue fixed in the 4.4 branch?
see my Gist https://gist.github.com/ebicoglu/543928d2dec68ce4fc0ddf25b8e39bac
this error looks like specific to you. did you change the this file manually
%UserProfile%\.abp\suite\appsettings.json
if yes, rename it to appsetting.backup.json and try to add your solution again.
closing this ticket. will be fixed in the next release if you encounter the same problem you can reopen this.
the hacky way is disabling IMultiTenant data filter to access data btw different tenants. see https://docs.abp.io/en/abp/4.4/Data-Filtering#imultitenant
but this is possible if all your tenants share the same DB.
if you change the tenant explained in the following doc, ABP Framework will set the TenantId https://docs.abp.io/en/abp/4.4/Multi-Tenancy#change-the-current-tenant
there's only 1 test in the saas application test project and it's a sample test without any test inside.
what's the exception?
