Hi ABP team,

I have a question regarding HangfirePeriodicBackgroundWorkerAdapter. I understand this is a worker which is asking as a bridge. What I don't find so nice about this approach is that it's flooding the hangfire dashboard, and if somebody wants to check jobs of the application it's difficult to find them.

If someone would use directly HangfireBackgroundWorkerBase , would HangfirePeriodicBackgroundWorkerAdapter actually be necessary? And if no, can it be disabled?

Hi,

I'm following up this ticket: https://abp.io/support/questions/8987/Upgrade-91---Issues-with-Google-External-login-Provider

Can you confirm that either 9.1.1 or 9.2 contains the bug fix for the above issues?

Thanks Alex

• Database System: EF Core / SQL Server , Running Angular UI

• Exception message and full stack trace: [10:02:58 INF] Error from RemoteAuthentication: OAuth token endpoint failure: invalid_client;Description=Unauthorized. [10:02:58 ERR] An unhandled exception has occurred while executing the request. Microsoft.AspNetCore.Authentication.AuthenticationFailureException: An error was encountered while handling the remote login. ---> Microsoft.AspNetCore.Authentication.AuthenticationFailureException: OAuth token endpoint failure: invalid_client;Description=Unauthorized --- End of inner exception stack trace --- at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler1.HandleRequestAsync() at Volo.Abp.Account.Public.Web.ExternalProviders.AbpAccountAuthenticationRequestHandler2.HandleRequestAsync() at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context) at Volo.Abp.AspNetCore.Security.AbpSecurityHeadersMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<<CreateMiddleware>b__0>d.MoveNext() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.RequestLocalization.AbpRequestLocalizationMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<<CreateMiddleware>b__0>d.MoveNext() --- End of stack trace from previous location ---

• Steps to reproduce the issue:

Hi, we upgraded an older project from 8.1 to 9.1, by doing step by step upgrades. After upgrading from 9.0.4 to 9.1, the google external login stopped working. Actually there are 2 issues:

• First of all, we had to delete the configurations in AbpSettings DB because the solution would not start, complaining that the settings are not in correct format
• After deleting the settings, and reconfigure the external google sign in, we get the above error

I tested this with a fresh 9.1 build, and the issue is also there. Basically configure google signin here:

And then try to login in with google.

• ABP Framework version: v9.0
• UI Type: Angular
• Database System: EF Core SQL Server
• Tiered (for MVC) or Auth Server Separated (for Angular): no

Hi ABP team,

I wanted to check a point, how is it enforced that users have unique username or email? Is this an application level check? If I check the database, I can see that all indexes are created as non unique so in theory it could be possible to create two users with same username or email if it happens in the same time.

I did a quick check and Microsoft is adding a unique index for the username at least: https://learn.microsoft.com/en-us/aspnet/core/security/authentication/customize-identity-model?view=aspnetcore-9.0#default-model-configuration

• ABP Framework version: v8.1.1
• UI Type: Angular
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Exception message and full stack trace:
• Steps to reproduce the issue:

HI ABP team,

When running tests on Azure Devops and very rarely on the developer machine, we get randomly failing unit tests. We can see the following exception:

Starting test execution, please wait... A total of 1 test files matched the specified pattern. [xUnit.net 00:00:18.48] Project.App.EntityFrameworkCore.Repositories.IdentityCustomerUserRepositoryTests.GetCustomerIdentityUsers_Will_Filter_By_Email_Or_UserName(email: null, userName: null, customerName: "CME", customerNumber: null, expectedCount: 1) [FAIL] Failed Project.App.EntityFrameworkCore.Repositories.IdentityCustomerUserRepositoryTests.GetCustomerIdentityUsers_Will_Filter_By_Email_Or_UserName(email: null, userName: null, customerName: "CME", customerNumber: null, expectedCount: 1) [1 ms] Error Message: Volo.Abp.AbpInitializationException : An error occurred during the initialize Volo.Abp.Modularity.OnApplicationInitializationModuleLifecycleContributor phase of the module Project.App.QQTestBaseModule, Project.App.TestBase, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null: Object reference not set to an instance of an object.. See the inner exception for details. ---- System.NullReferenceException : Object reference not set to an instance of an object. Stack Trace: at Volo.Abp.Modularity.ModuleManager.InitializeModules(ApplicationInitializationContext context) at Volo.Abp.AbpApplicationBase.InitializeModules() at Volo.Abp.AbpApplicationWithExternalServiceProvider.Initialize(IServiceProvider serviceProvider) at Volo.Abp.Testing.AbpIntegratedTest1..ctor() at Project.App.QQTestBase1..ctor() at Project.App.EntityFrameworkCore.QQEntityFrameworkCoreTestBase..ctor() at Project.App.EntityFrameworkCore.Repositories.IdentityCustomerUserRepositoryTests..ctor() in /home/vsts/work/1/s/test/Project.App.EntityFrameworkCore.Tests/EntityFrameworkCore/Repositories/IdentityCustomerUserRepositoryTests.cs:line 23 at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean wrapExceptions) ----- Inner Stack Trace ----- at Microsoft.Data.Sqlite.SqliteConnection.RemoveCommand(SqliteCommand command) at System.Data.Common.DbCommand.DisposeAsync() at Microsoft.EntityFrameworkCore.Storage.RelationalDataReader.DisposeAsync() at Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ToListAsync[TSource](IQueryable1 source, CancellationToken cancellationToken) at Volo.Abp.SettingManagement.EntityFrameworkCore.EfCoreSettingRepository.GetListAsync(String providerName, String providerKey, CancellationToken cancellationToken) at Castle.DynamicProxy.AsyncInterceptorBase.ProceedAsynchronous[TResult](IInvocation invocation, IInvocationProceedInfo proceedInfo) at Volo.Abp.Castle.DynamicProxy.CastleAbpMethodInvocationAdapterWithReturnValue1.ProceedAsync() at Volo.Abp.Uow.UnitOfWorkInterceptor.InterceptAsync(IAbpMethodInvocation invocation) at Volo.Abp.Castle.DynamicProxy.CastleAsyncAbpInterceptorAdapter1.InterceptAsync[TResult](IInvocation invocation, IInvocationProceedInfo proceedInfo, Func3 proceed) at Volo.Abp.SettingManagement.SettingManagementStore.SetCacheItemsAsync(String providerName, String providerKey, String currentName, SettingCacheItem currentCacheItem)

As mentioned, each time it's a different test. The only common thing is the exception root: Volo.Abp.AbpInitializationException : An error occurred during the initialize Volo.Abp.Modularity.OnApplicationInitializationModuleLifecycleContributor phase of the module Project.App.QQTestBaseModule, Project.App.TestBase, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null: Object reference not set to an instance of an object.. See the inner exception for details. ---- System.NullReferenceException : Object reference not set to an instance of an object. Stack Trace: at Volo.Abp.Modularity.ModuleManager.InitializeModules(ApplicationInitializationContext context)

We would gladly work together with you to discover the root cause, but I don't what we can change in the setup to get more details.

Database provider: EntityFrameworkCore UI framework: Angular ABP Version: 8.0.5 Generated through ABP Suite

Hi ABP team,

I'm posting here a couple of points related to abp suite. Could you assist us with them?

Frontend angular:

Design:

Is it possible for me to design and implement new templates that can be utilized during the generation process?

CSS

Where should I write CSS for my specific component? Is it necessary to place all of my CSS classes within the global styles.css file, or is there an alternative approach? Regarding advanced filters, is there an option to disable them entirely? Alternatively, is it possible to select which filters are included?

Database provider: EntityFrameworkCore UI framework: Angular ABP Version: 8.0.5 Generated through ABP Suite

Hi ABP team,

I'm posting here a couple of points related to abp suite. Could you assist us with them?

Will value objects be supported? And any time soon?

From the ABP provided documentation, it’s clear that value object type is not supported, but this can’t be achieved through custom code either.

As noticed from the figure, the custom code part indeed can be modified and changes won’t be lost. Or

After applying changes in DbContext class to register the properties from value object SupplierDetails, a new build done through APB suite will delete the custom changes. From the above figure it can be noticed that the value object mapping is lost, regardless of the registration approach.

This cand simply be reproduced by creating a new entity (master or child) and adding even just one property.

Why are empty “if” statements added in DbContext?

Another noticed thing that occurs with every build done from ABP Suite also at DbContext class level is that suite is adding the same empty if statement every time.

This cand simply be reproduced by creating/updating an entity and hitting the “Save and generate” button from ABP Suite.

Will child entities be handled through its master entity?

ABP Suite’s documentation specifies that for child type entities DomainService and AppService classes are created apart from master’s DomainService and AppService classes, meaning that child entities won’t be handled through master’s DomainService and AppService. Couldn’t child entities be handled along with master entity? When creating/updating/deleting master entities, child entities should be created/updated/deleted through master and not through child DomainService or child AppService.

Will there be checks added for create/update DTOs in order to specify which properties to add to each DTO?

While creating or editing an entity, base DTOs are automatically created/updated, but some properties that are not intended for create or update actions are landing in create/update base DTOs that are clearly not modifiable. This option should fall in the user's control.

ABP recommendations not respected in Domain Service

In the generated domain service, repository methods are used to insert / update entities. Based on documentation from ABP, this should happen in the appservice

Frontend angular:

Design:

Is it possible for me to design and implement new templates that can be utilized during the generation process?

CSS

Where should I write CSS for my specific component? Is it necessary to place all of my CSS classes within the global styles.css file, or is there an alternative approach? Regarding advanced filters, is there an option to disable them entirely? Alternatively, is it possible to select which filters are included?

Excel

For exporting to Excel, does the export include all fields from the entity? Can I choose which fields to be included?

General:

If we modify a template how do we maintain it when ABP ships out changes / bug fixing in the templates?