The reasons for doing that are detailed in this aspnetcore issue.
The user says he found a workaround by creating a UserManager/RoleManager
UserManager
RoleManager