Activities of "trendline"

I also encountered this issue, just comments out below dependents resolved it temporarily //typeof(CmsKitProPublicWebModule), //typeof(CmsKitProWebModule),

Thanks your helping, maliming

[maliming] said: hi

The UserFriendlyException not shown on the razor page client

What is your razor page code?

Thanks

Not any specified code, just a form submit, send a phonenumber and a verification code to API side.

ABP ver 9.3.5 with micro-services architecture, the UserFriendlyException not shown on the razor page client when backend API throw a UserFriendlyException, below is the code section: A BusinessException threw but it cannot shown on the client side in a application service like below: `
public virtual async Task

        if (!result)
        {
            throw new InvalidVerificationCodeException();
        }

        var identityUser = await _phoneNumberLoginNewUserCreator.CreateAsync(input.PhoneNumber, input.UserName, input.Password, input.EmailAddress);

        return ObjectMapper.Map<IdentityUser, IdentityUserDto>(identityUser);
    }
    `

the InvalidVerificationCodeException is a BusinessException

I added an UserFriendlyException in the Controller like below: `
[HttpPost] [Route("register/by-phone-number")] public virtual async Task

            return result;
        }
        catch (BusinessException ex)
        {

            throw new UserFriendlyException(ex.Code);
        }
    }
    `
    it got below logs in the backend:
    `
    2025-10-08 17:38:45.887 +08:00 [WRN] ---------- RemoteServiceErrorInfo ----------

{ "code": null, "message": "EasyAbp.Abp.PhoneNumberLogin:InvalidVerificationCode", "details": null, "data": {}, "validationErrors": null }

2025-10-08 17:38:45.887 +08:00 [WRN] EasyAbp.Abp.PhoneNumberLogin:InvalidVerificationCode Volo.Abp.UserFriendlyException: EasyAbp.Abp.PhoneNumberLogin:InvalidVerificationCode at EasyAbp.Abp.PhoneNumberLogin.Web.Controllers.PhoneNumberLogin.Account.LoginController.RegisterByPhoneNumberAsync(RegisterWithPhoneNumberInput input) at lambda_method3691(Closure, Object) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.AwaitableObjectResultExecutor.Execute(ActionContext actionContext, IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.

then the client get a 403 forbidden HTTP Status code with the errors like below, it doesn't use UI throw a message: { "error": { "code": null, "message": "EasyAbp.Abp.PhoneNumberLogin:InvalidVerificationCode", "details": null, "data": {}, "validationErrors": null } }

Resolved by added below code in ConfigureServices: `
Configure

        // This Cron expression only works if Hangfire or Quartz is used for background workers.
        // The Hangfire Cron expression is different from the Quartz Cron expression, Please refer to the following links:
        // https://www.quartz-scheduler.net/documentation/quartz-3.x/tutorial/crontriggers.html#cron-expressions
        // https://docs.hangfire.io/en/latest/background-methods/performing-recurrent-tasks.html
        options.CronExpression = "0 2 * * * ?"; // Quartz Cron expression is "0 23 * * * ?"
    });

` The default cron expression is for Hangfire, needs to add the correct format for Quartz if you are using Quartz as background worker.

This should add int the doc as a configuration section.

• Exception message and full stack trace:2025-09-28 05:01:50.206 +08:00 [FTL] Host terminated unexpectedly! Volo.Abp.AbpInitializationException: An error occurred during the initialize Volo.Abp.Modularity.OnApplicationInitializationModuleLifecycleContributor phase of the module Volo.Abp.AuditLogging.AbpAuditLoggingApplicationModule, Volo.Abp.AuditLogging.Application, Version=9.3.4.0, Culture=neutral, PublicKeyToken=null: Unexpected end of expression.. See the inner exception for details. ---> System.FormatException: Unexpected end of expression. at Quartz.CronExpression.BuildExpression(String expression) at Quartz.CronExpression..ctor(String cronExpression) at Quartz.CronExpression.ValidateExpression(String cronExpression) at Quartz.CronScheduleBuilder.CronSchedule(String cronExpression) at Quartz.CronScheduleTriggerBuilderExtensions.WithCronSchedule(TriggerBuilder triggerBuilder, String cronExpression) at Volo.Abp.BackgroundWorkers.Quartz.QuartzPeriodicBackgroundWorkerAdapter1.BuildWorker(IBackgroundWorker worker) at Volo.Abp.BackgroundWorkers.Quartz.QuartzBackgroundWorkerManager.ReScheduleJobAsync(IBackgroundWorker worker, CancellationToken cancellationToken) at Volo.Abp.BackgroundWorkers.Quartz.QuartzBackgroundWorkerManager.AddAsync(IBackgroundWorker worker, CancellationToken cancellationToken) at Volo.Abp.AuditLogging.AbpAuditLoggingApplicationModule.OnApplicationInitializationAsync(ApplicationInitializationContext context) at Volo.Abp.Modularity.OnApplicationInitializationModuleLifecycleContributor.InitializeAsync(ApplicationInitializationContext context, IAbpModule module) at Volo.Abp.Modularity.ModuleManager.InitializeModulesAsync(ApplicationInitializationContext context) --- End of inner exception stack trace --- at Volo.Abp.Modularity.ModuleManager.InitializeModulesAsync(ApplicationInitializationContext context) at Volo.Abp.AbpApplicationBase.InitializeModulesAsync() at Volo.Abp.AbpApplicationWithExternalServiceProvider.InitializeAsync(IServiceProvider serviceProvider) at Microsoft.AspNetCore.Builder.AbpApplicationBuilderExtensions.InitializeApplicationAsync(IApplicationBuilder app) at Viewtance.FM.Program.Main(String[] args) in D:\Source\Repos\apps\Viewtance.FM\src\Viewtance.FM.HttpApi.Host\Program.cs:line 58 `
• Steps to reproduce the issue: Debug Host project in a tired solution, host project failed to start.

The generate proxy issue resolved, it caused by a typo which the interface of the integration service not follow the conventional.

• Exception message and full stack trace: cannot generate the proxies for new added integration services in a microservice project
• Steps to reproduce the issue: follow the guides Integration Services add interface and implementation for the new integration service, when using abp studio or cli generate the proxy, not proxies generated, the integration service provider microservice is a project template service IdentityService

any miss configuration for integration service, or the generate proxy action is wrong?

Thanks for the help from Maliming, the auth server UI login is a cookie authentication, not the token scenario, added below code auth server module works fine

` context.Services.ConfigureApplicationCookie(options => { var previousOnSignedIn = options.Events.OnSignedIn; options.Events.OnSignedIn = async cookieSignedInContext => { await previousOnSignedIn(cookieSignedInContext);
};

var previousOnSigningOut = options.Events.OnSigningOut;
options.Events.OnSigningOut = async cookieSigningOutContext =>
{
    await previousOnSigningOut(cookieSigningOutContext);    
};

}); `

The simple inline handle is not triggered, the event itself may not be firing due to pipeline misconfiguration, could you give some suggestions which pipeline misconfiguration?