Open Closed

Bugs & Issues v4.3.X #1126

User avatar
0
alper created
Support Team Director

To update your version to v4.3.x for both ABP CLI and ABP Suite run the following command

dotnet tool update -g Volo.Abp.Cli --version 4.3.0-rc.1
abp suite update --preview

or

Run this PowerShell script to update both the CLI and Suite to the latest including the preview versions.

v4.3 Preview ABP Framework Version Notes https://blog.abp.io/abp/ABP-Framework-4.3-RC-Has-Been-Published

v4.3 Preview ABP Commercial Version Notes https://blog.abp.io/abp/ABP-Commercial-4.3-RC-Has-Been-Published

From 4.x to 4.3 Migration Guide https://docs.abp.io/en/commercial/4.3/migration-guides/v4_3

Go to accepted answer
2 1
188 Answer(s)
  • User Avatar
    0
    talhazengin created

    Creating a new tenant does not creates an admin user for that tenant. chris.tune@gmail.com is right.

    ABP Framework version: v4.3.0 (new template) UI type: Angular DB provider: EF Core Identity Server Separated: yes Exception message and stack trace: No error.

    Steps: Create a tenant, you will see it won't add an admin user for that tenant.

    1
  • User Avatar
    0
    hakan.uskaner created

    I have an error with abp 4.3.0 and the Tiered MVC Version I think we got that error before, but could not find a issue here at that page.

    Steps to reproduce:

    1. Generate a new MVC/EF Version with Tiered Option enabled
    2. Generate a Item a property with Abp Suite
    3. Start Web Application and access that Item Page

    You receive that error:

    (Also an bug or feature : The AddItem Menu Entry in MenuContributor is in a different place at ConfigureUserMenuAsync instead ConfigureMainMenuAsync)

    I did check the index.js from that Item. There seams to be an error at the controller at line 3:

    var inventoryItemService = window.tierTest.controllers.inventoryItems.inventoryItems;

    instead of : var inventoryItemService = window.tierTest.controllers.inventoryItems.inventoryItem;

    I couldn't fix, because it seams that are more errors somewhere..

    It works well if i generate a new ap without the Tired Option.

    Do you got an workaround ?

  • User Avatar
    0
    AlderCove created

    Adding a new multi-tenanted entity through ABP Suite has AutoMapperConfigurationException

    ABP Framework version: v4.3.0 ( module template) UI type: MVC DB provider: EF Core Identity Server Separated: no

    When starting the Unified App from a Module template, after generating a multi-tenanted entity, adding migration and updating SQL database, the application has exception on startup:

    An unhandled exception occurred while processing the request.

    AutoMapperConfigurationException: Unmapped members were found. Review the types and members below. Add a custom mapping expression, ignore, add a custom resolver, or modify the source/destination type For no matching constructor, add a no-arg ctor, add optional arguments, or map all of the constructor parameters

    ResourceClassTypeCreateDto -> ResourceClassType (Destination member list) Acs.ResourceLibrary.ResourceClassTypes.ResourceClassTypeCreateDto -> Acs.ResourceLibrary.ResourceClassTypes.ResourceClassType (Destination member list)

    Unmapped properties:

    TenantId

    ResourceClassTypeUpdateDto -> ResourceClassType (Destination member list) Acs.ResourceLibrary.ResourceClassTypes.ResourceClassTypeUpdateDto -> Acs.ResourceLibrary.ResourceClassTypes.ResourceClassType (Destination member list)

    Unmapped properties: TenantId AutoMapper.ConfigurationValidator.AssertConfigurationIsValid(IEnumerable typeMaps)

    <br> DependencyResolutionException: An exception was thrown while activating λ:Microsoft.AspNetCore.Identity.ISecurityStampValidator -> Castle.Proxies.AbpSecurityStampValidatorProxy -> Volo.Abp.MultiTenancy.TenantConfigurationProvider -> Volo.Saas.Tenants.TenantStore -> Volo.Abp.ObjectMapping.DefaultObjectMapper1[[Volo.Saas.SaasDomainModule, Volo.Saas.Domain, Version=4.3.0.0, Culture=neutral, PublicKeyToken=null]] -> Volo.Abp.AutoMapper.AutoMapperAutoObjectMappingProvider1[[Volo.Saas.SaasDomainModule, Volo.Saas.Domain, Version=4.3.0.0, Culture=neutral, PublicKeyToken=null]] -> λ:Volo.Abp.AutoMapper.IMapperAccessor -> λ:Volo.Abp.AutoMapper.MapperAccessor. Autofac.Core.Resolving.Middleware.ActivatorErrorHandlingMiddleware.Execute(ResolveRequestContext context, Action next)

    <br> Was able to resolve the issue by adding .Ignore(x => x.TenantId) extension on the CreateMap in the src/Project.Application ProjectAutoMapperProfile class:

    Is that the correct approach?

  • User Avatar
    0
    Dicky.tech@gmail.com created

    4.3 file management module.

    file upload api works on local host after deploying to server it won't work. redirects to home page. all other apis works well.

    on the UI I can upload files well

    have you tested this ?

  • User Avatar
    0
    joe@tronactive.com created

    I updated ABP suite to 4.3.0 but didn't update my solution. I went to add a new property to one of my entities and got the below message.

    I had the same issue that a lot of people had right away when I tried upgrading to 4.3.0. "Cannot read the template Volo.Abp.Commercial.SuiteTemplates.Templates.Server.Entity.Partials.ConfigureEntityMultiTenantCondition.txt"

    I got past that issue once I updated the solution to 4.3.0 as others suggested. But then I noticed it partially added the new property but did not finish and now when i try to re-generate the entitiy with the new property that it already tried to generate it says the below error. I tried undoing everything it partially updated in the git changes but that didn't work either. Have any ideas?

  • User Avatar
    0
    alper created
    Support Team Director

    ABP Framework version: v4.3.0
    UI type: Angular
    DB provider: EF Core
    Tiered (MVC) or Identity Server Separated (Angular): Yes
    Steps to reproduce the issue:
    I just get source from ABP suite and build. It has this error

    @edelivery couldn't understand what you get? is that a module?

    Hi alper
    I just created new solution from abp suite
    Template type: application template

    so I understand this; you create a new Angular + EF Core + Separated Identity Server proejct.
    And it throws exception out of the box. Right?

    yes, that's right

    I created a new 4.3.0 project with the following CLI command

    abp new Angular.EfCoreSeperate05113159 -t app-pro -u angular -m none --separate-identity-server --database-provider ef -csf

    Migrated db with DBMigrator. Run IdentityServer project first, then HttpApi.Host project then, Angular ...

    And I don't see any console errors:

    Ensure that you are running the latest ABP CLI

  • User Avatar
    0
    alper created
    Support Team Director

    I've upgraded our solution from ABP 3.3.2 to 4.3.0.

    Everything was more or less smoothly, but now I discovered a problem: some new ABP tables are missing from migration scripts! How come? What am I supposed to do now?

    Please have a look at the migration classes autogenerated for 3.3.2 and 4.3.0. https://1drv.ms/u/s!AhWdpZddvifTtizt4xjre044i7B8?e=0xuBUs

    Here is the list of ABP-prefixed tables created from test solution (autogenerated in ABP Suite) using DbMigrator project in local MS SQL server DB - all the tables are at place:

    Here is the list of tables in our ORACLE DB created using standard update-database command and DbMigrator afterwards to seed data - make a note some tables are missing (for instance, AbpBlobContainers, AbpTextTemplateContents). How it's possible?? How to easily find out what is missing and add it?

    @Alexander there are missing tables because you might not have these modules: AbpBlobContainers, AbpTextTemplateContents If you create a new project these modules come by default that's why you see the difference in migration. You need to add these modules manually (if you require them)

  • User Avatar
    0
    alexander.nikonov created

    there are missing tables because you might not have these modules: AbpBlobContainers, AbpTextTemplateContents If you create a new project these modules come by default that's why you see the difference in migration. You need to add these modules manually (if you require them)

    @alper I did not expect to need this(these) module(s), but I got exception when trying to use "Forgot password" functionality - there was exception related to missing table - AbpTextTemplateContents. But even if this table is to be created when I add the corresponding module - it's gonna be empty? IMHO It should not require some email templates as "mustbe"? Or should be some default templates created automatically as I see it.

    Anyway, I am not sure it's quite obvious I need this table, because in the previous versions of ABP I didn't have this table and "Forgot password" worked as expected (i.e. email was sent)... So the question is: how to make "Forgot password" functionality work now? BTW, I need to fine-tune password update, because we use multi-tenant custom logic and I will need to update the password for all logins (usernames) with the same name at other tenants...

  • User Avatar
    0
    alper created
    Support Team Director

    ABP Framework version: v4.3.0 UI type: Angular DB provider: EF Core

    Problem : wrong generate localization

    @arifharsono that issue will be fixed in 4.3.1

  • User Avatar
    0
    joe@tronactive.com created

    @alper do you have any ideas on the one I posted 4 days ago? Can't populate enum localizations after upgrading to 4.3.0?

  • User Avatar
    0
    alper created
    Support Team Director

    I have an error with abp 4.3.0 and the Tiered MVC Version I think we got that error before, but could not find a issue here at that page.

    Steps to reproduce:

    1. Generate a new MVC/EF Version with Tiered Option enabled
    2. Generate a Item a property with Abp Suite
    3. Start Web Application and access that Item Page

    You receive that error:

    (Also an bug or feature : The AddItem Menu Entry in MenuContributor is in a different place at ConfigureUserMenuAsync instead ConfigureMainMenuAsync)

    I did check the index.js from that Item. There seams to be an error at the controller at line 3:

    var inventoryItemService = window.tierTest.controllers.inventoryItems.inventoryItems;

    instead of :
    var inventoryItemService = window.tierTest.controllers.inventoryItems.inventoryItem;

    I couldn't fix, because it seams that are more errors somewhere..

    It works well if i generate a new ap without the Tired Option.

    Do you got an workaround ?

    @hakan while we fix this issue there's a workaround. open the templates page in Suite. and find index.js.txt make the following change entity-name-plural-camelcase => entity-name-camelcase

  • User Avatar
    0
    hakan.uskaner created

    @alper: thanks for the workaround..

  • User Avatar
    0
    alper created
    Support Team Director

    Adding a new multi-tenanted entity through ABP Suite has AutoMapperConfigurationException

    ABP Framework version: v4.3.0 ( module template) UI type: MVC DB provider: EF Core Identity Server Separated: no

    When starting the Unified App from a Module template, after generating a multi-tenanted entity, adding migration and updating SQL database, the application has exception on startup:

    An unhandled exception occurred while processing the request.

    AutoMapperConfigurationException: Unmapped members were found. Review the types and members below. Add a custom mapping expression, ignore, add a custom resolver, or modify the source/destination type For no matching constructor, add a no-arg ctor, add optional arguments, or map all of the constructor parameters

    ResourceClassTypeCreateDto -> ResourceClassType (Destination member list) Acs.ResourceLibrary.ResourceClassTypes.ResourceClassTypeCreateDto -> Acs.ResourceLibrary.ResourceClassTypes.ResourceClassType (Destination member list)

    Unmapped properties:

    TenantId

    ResourceClassTypeUpdateDto -> ResourceClassType (Destination member list) Acs.ResourceLibrary.ResourceClassTypes.ResourceClassTypeUpdateDto -> Acs.ResourceLibrary.ResourceClassTypes.ResourceClassType (Destination member list)

    Unmapped properties: TenantId AutoMapper.ConfigurationValidator.AssertConfigurationIsValid(IEnumerable typeMaps)

    <br> DependencyResolutionException: An exception was thrown while activating λ:Microsoft.AspNetCore.Identity.ISecurityStampValidator -> Castle.Proxies.AbpSecurityStampValidatorProxy -> Volo.Abp.MultiTenancy.TenantConfigurationProvider -> Volo.Saas.Tenants.TenantStore -> Volo.Abp.ObjectMapping.DefaultObjectMapper1[[Volo.Saas.SaasDomainModule, Volo.Saas.Domain, Version=4.3.0.0, Culture=neutral, PublicKeyToken=null]] -> Volo.Abp.AutoMapper.AutoMapperAutoObjectMappingProvider1[[Volo.Saas.SaasDomainModule, Volo.Saas.Domain, Version=4.3.0.0, Culture=neutral, PublicKeyToken=null]] -> λ:Volo.Abp.AutoMapper.IMapperAccessor -> λ:Volo.Abp.AutoMapper.MapperAccessor. Autofac.Core.Resolving.Middleware.ActivatorErrorHandlingMiddleware.Execute(ResolveRequestContext context, Action next)

    <br> Was able to resolve the issue by adding .Ignore(x => x.TenantId) extension on the CreateMap in the src/Project.Application ProjectAutoMapperProfile class:

    Is that the correct approach?

    @AlderCove that's right.

    I created a new entity with the latest Suite (4.3.1 not published yet) and it also ignores TenantId

  • User Avatar
    0
    alper created
    Support Team Director

    4.3 file management module.

    file upload api works on local host after deploying to server it won't work. redirects to home page. all other apis works well.

    on the UI I can upload files well

    have you tested this ?

    there must be 2 identical enum value. you can remove the enum property and add again. or you can edit the entity.json file which is located in your .suite\entities folder.

  • User Avatar
    0
    cotur created

    4.3 file management module.

    file upload api works on local host after deploying to server it won't work. redirects to home page. all other apis works well.

    on the UI I can upload files well

    have you tested this ?

    Hi @dicky.tech

    Yes we have tested and got no problem after deployed to server. Can you share with me some logs?

  • User Avatar
    0
    Dicky.tech@gmail.com created

    4.3 file management module.

    file upload api works on local host after deploying to server it won't work. redirects to home page. all other apis works well.

    on the UI I can upload files well

    have you tested this ?

    Hi @dicky.tech

    Yes we have tested and got no problem after deployed to server. Can you share with me some logs?

    Hi, I will share logs tomorrow. meanwhile you can share the sample code you've used to upload images via API ?

  • User Avatar
    0
    cotur created

    Hi @dicky.tech,

    You can use IRemoteStreamContent for file uploading etc. See: https://docs.abp.io/en/abp/latest/Application-Services#working-with-streams

  • User Avatar
    0
    Dicky.tech@gmail.com created

    Hi @dicky.tech,

    You can use IRemoteStreamContent for file uploading etc. See: https://docs.abp.io/en/abp/latest/Application-Services#working-with-streams

    It worked.

    Thank you.

    Actually my issues was cookies in postman. Antiforgery. Was referencing to local cookie.

  • User Avatar
    0
    cotur created

    It seems like you have trouble with Anti Forgery System.

    See: https://docs.abp.io/en/abp/latest/CSRF-Anti-Forgery

    For MVC, we put antiForgeryToken to file upload posting request header.

    headers[abp.security.antiForgery.tokenHeaderName] = abp.security.antiForgery.getToken();

  • User Avatar
    0
    Dicky.tech@gmail.com created

    It seems like you have trouble with Anti Forgery System.

    See: https://docs.abp.io/en/abp/latest/CSRF-Anti-Forgery

    For MVC, we put antiForgeryToken to file upload posting request header.

    headers[abp.security.antiForgery.tokenHeaderName] = abp.security.antiForgery.getToken();

    sure. am okie

  • User Avatar
    0
    arifharsono created

    Create new tenant not creating admin user

    • ABP Framework version: v4.3.0 (Upgraded from 4.2.1)
    • UI type: Angular
    • DB provider: EF Core
    • Tiered (MVC) or Identity Server Separated (Angular): no
    • Exception message and stack trace: No error is thrown.
    • Steps to reproduce the issue:
    1. Goto SaaS-->Tenants-->New Tenant
    2. Create a new tenant with the admin user and pass entered.
    3. Save

    It looks like the tenant is created but the admin user is not added.
    In the database the tenant is added but there is no user.
    Potentially a problem in ObjectExtensions or TenantAppService?

    Chris

    I have the same problem here, ABP Framework version:* v4.3.0 from new Template.

    at Volo.Abp.Castle.DynamicProxy.CastleAsyncAbpInterceptorAdapter1.InterceptAsync[TResult](IInvocation invocation, IInvocationProceedInfo proceedInfo, Func3 proceed) at Volo.Saas.Tenants.TenantStore.GetCacheItemAsync(Nullable`1 id, String name) at Volo.Saas.Tenants.TenantStore.FindAsync(Guid id) <<<---- Error

  • User Avatar
    0
    scott7106 created

    reported by @chris.tune@gmail.com

    Create new tenant not creating admin user

    • ABP Framework version: v4.3.0 (Upgraded from 4.2.1)
    • UI type: Angular
    • DB provider: EF Core
    • Tiered (MVC) or Identity Server Separated (Angular): no
    • Exception message and stack trace: No error is thrown.
    • Steps to reproduce the issue:
    1. Goto SaaS-->Tenants-->New Tenant
    2. Create a new tenant with the admin user and pass entered.
    3. Save

    It looks like the tenant is created but the admin user is not added.
    In the database the tenant is added but there is no user.
    Potentially a problem in ObjectExtensions or TenantAppService?

    Chris

    The issue is more pervasive than Chris reported. None of the identity components are created for the new tenant. This includes the admin user, the default admin role and the initial permission grants needed for the new admin role.

    Is there a status available for this issue? Will it be addressed in the next patch?

  • User Avatar
    0
    camping89@gmail.com created

    ABP Framework version: v4.3.0 (15 May 2021) UI type: Blazer Web Server DB provider: MongoDB Tiered: yes Exception message and stack trace:

    The issue is ABP Suite will fail from second time of generation as above: Missing XXXWebAutoMapperProfile.cs

  • User Avatar
    1
    willignicolas@gmail.com created

    Hello,

    I think i'm the 4 person to report this :

    With UI MVC EF Core and no tiered when we create a new tenant the user is not deployed (We cannot login in tenant and use it) We can't on boarding new customer in production :(

    It's is ok with a new project. I have followed the migration steps for our project. (with compare method) but the problem is still there.

    Thanks for your help.

    erreur log is to long to post... timeout in : at Volo.Saas.Tenants.TenantStore.FindAsync(Guid id) at Jureez.Data.JureezTenantDatabaseMigrationHandler.MigrateAndSeedForTenantAsync(Guid tenantId, String adminEmail, String adminPassword) in C:\Personnel\Developpement\Jureez\aspnet-core\src\Jureez.Domain\Data\JureezTenantDatabaseMigrationHandler.cs:line 92

    2
  • User Avatar
    0
    Leaf created

    Blazor 4.3 preview

    unable to generate, is it backend template name is wrong spelling "o" and "e" ?

Assignee
User avatar alper
Labels
None yet
Made with ❤️ on ABP v9.1.0-preview. Updated on November 01, 2024, 05:35