DBContext Issue with 3.3.3: System.ObjectDisposedException: Cannot access a disposed object.

Describe the bug

Each time my job fires, I get the error:

 ---> System.ObjectDisposedException: Cannot access a disposed object. A common cause of this error is disposing a context that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling Dispose() on the context, or wrapping the context in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances.
Object name: 'MyDbContext'.

Version used

3.3.3

To Reproduce

Here is my setup in my Startup.cs:

            services.AddQuartz(q =>
            {
                // Allows us to use dependency injection in all our job classes
                q.UseMicrosoftDependencyInjectionJobFactory();

                // Run a job every minute
                var myJobKey = new JobKey("MyJob");
                q.AddJob<MyJob>(opts => opts
                    .WithIdentity(myJobKey));
                q.AddTrigger(opts => opts
                    .ForJob(myJobKey)
                    .WithIdentity("MyJobTrigger")
                    .WithCronSchedule("0 0/1 * * * ?"));
            });

            services.AddQuartzServer(options =>
            {
                // when shutting down we want jobs to complete gracefully
                options.WaitForJobsToComplete = true;
            });

Expected behavior

According to the docs, using:

q.UseMicrosoftDependencyInjectionJobFactory();

should:

also injects scoped services (like EF DbContext) without problems

docs link: https://www.quartz-scheduler.net/documentation/quartz-3.x/packages/microsoft-di-integration.html#di-aware-job-factories

Additional context I should also mention I am using aspnetboilerplate, perhaps that is the culprit? Though I’m configuring everything with Quartz through Startup.cs, so actually aspnetboilerplate shouldn’t come into play at all here…

Not sure what I’m missing. Any pointers, ideas, or help would be much appreciated!

[princefishthrower]

Finally, to be clear, I’ve gone with my original solution, using Quartz in Startup.cs. I just needed to add [UnitofWork] to each job using repositories, as well as ensuring my job extended ITransientDependency, i.e. MyJob : IJob, ITransientDependency (IJob so Quartz is happy and ITransientDependency so ASP.NET boilerplate is happy) Everything seems to be running well (so far).

[princefishthrower]

Ahhh, this may also be relevant to whoever finds this: https://github.com/aspnetboilerplate/aspnetboilerplate/issues/3757

Need to add [UnitOfWork] to the class.