Confirmation email is not sent when a user is created #10931

3 Answer(s)

• 

  0

  AI-Bot created 20 days ago

  Support Team ABP Agent

  • This happens because the distributed handler (AccountIdentityUserCreatedEventHandler) runs in the RabbitMQ consumer pipeline without an ambient ABP Unit of Work, but it calls Identity token generation (AbpSingleActiveTokenProvider.GenerateAsync(...)), which needs an EF Core DbContext. Without a UOW, ABP throws:

    A DbContext can only be created inside a unit of work!

  • Fix: ensure the handler method is executed inside a Unit of Work via interception:

    1. Add [UnitOfWork]
    2. Make the method virtual (required for ABP’s dynamic proxy interception)
    3. Add using Volo.Abp.Uow;

    Example:

  using System.Threading.Tasks;
    using Volo.Abp.Uow;
  
    public class AccountIdentityUserCreatedEventHandler
    {
        [UnitOfWork]
        public virtual async Task HandleEventAsync(IdentityUserCreatedEto eventData)
        {
            // existing handler code (no other changes needed)
        }
    }
  

  • Why the virtual matters: ABP applies [UnitOfWork] through dynamic proxy interceptors. If the method isn’t virtual, the interceptor won’t run, so no UOW is created, and token generation fails. This matches the behavior you observed and also the known pattern from ABP support Q&A.

  • Alternative (works but usually not necessary if interception works): manually begin a UOW inside the handler:

  using var uow = _unitOfWorkManager.Begin();
    // ...
    await uow.CompleteAsync();
  

  But the recommended approach is the attribute + virtual so the infrastructure manages it consistently.

  Links checked:

  • https://abp.io/docs/latest/framework/infrastructure/event-bus/distributed
  • https://abp.io/docs/latest/framework/architecture/domain-driven-design/unit-of-work
  • https://abp.io/support/questions/3201

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  VMPProgramador created 20 days ago

  Could a member of the support team please review this ticket?

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 19 days ago

  Support Team Fullstack Developer

  Hi,

  AccountIdentityUserCreatedEventHandler doesn't start a unit of work, so it fails when the event comes from RabbitMQ.

  You can use this workaround for now. Add this class to your Application project:

  using System.Threading.Tasks;
  using Volo.Abp.Account.Emailing;
  using Volo.Abp.EventBus.Distributed;
  using Volo.Abp.Identity;
  using Volo.Abp.Settings;
  using Volo.Abp.Uow;
  
  namespace YourProjectName.Account;
  
  public class MyAccountIdentityUserCreatedEventHandler :
      AccountIdentityUserCreatedEventHandler,
      IDistributedEventHandler<IdentityUserCreatedEto>
  {
      public MyAccountIdentityUserCreatedEventHandler(
          IdentityUserManager userManager,
          IAccountEmailer accountEmailer,
          ISettingProvider settingProvider)
          : base(userManager, accountEmailer, settingProvider)
      {
      }
  
      [UnitOfWork]
      public new virtual Task HandleEventAsync(IdentityUserCreatedEto eventData)
      {
          return base.HandleEventAsync(eventData);
      }
  }
  

  Then remove the original handler in the ConfigureServices method of your Application module, so the email isn't sent twice:

  using Volo.Abp.Account.Emailing;
  using Volo.Abp.EventBus.Distributed;
  
  Configure<AbpDistributedEventBusOptions>(options =>
  {
      options.Handlers.Remove<AccountIdentityUserCreatedEventHandler>();
  });
  

  The messages that RabbitMQ is still retrying will also be handled after this change.

  We'll fix this in the next patch release. Your ticket has been refunded.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel