| 88 | | After that trying to create a minimal setup that reproduces the issue, usage of the swappable user model feature was removed and the m2m field was re-pointed to standard auth.User, and finally to a local Employee model. |
| | 88 | After that (and when trying to create a minimal setup that reproduces the issue): |
| | 89 | |
| | 90 | - First usage of the swappable user model feature was removed and the m2m field was re-pointed to standard auth.User |
| | 91 | - And finally to a local Employee model. |
| | 92 | |
| | 93 | In all cases, the same exception was generated. |