Closed iJungleboy closed 3 months ago
it appears the problem was different.
Apparently it was because IView
objects were being cached once created, but they kept a lazy-service which stopped working after the initial IServiceProvider was disposed after filling the cache.
I'm submitting a
[x] bug report => search github for a similar issue before submitting
...about
[x] Content Types or data management [x] internals
Current Behavior / Expected Behavior
In fairly random scenarios, errors appear in the style of
Cannot Access Disposed object
Object name:IServiceProvider
.After extensive research it appears that this is because of Ghost content types accessing metadata of their parent app, and some changes in the API around
AppState
resulted in using Dependency Injection much later, after the initial setup had been completed and it had been disposed.Should be fixed now.
Instructions to Reproduce the Problem
Your environment