-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
InvalidOperationException after upgrading to net core 3.0 #17090
Labels
Comments
@KeKl Can you try with the latest daily build. If it still fails, then please post the full stack trace. |
Also seeing this error with latest daily build + latest preview SDK.
|
@jsheetzati Have you tried the latest daily build? |
Duplicate of #15855 Second issue is altogether different issue. |
@ajcvickers Not seeing the same issue anymore with 3.0.0-preview9.19415.1. Thanks!! |
ajcvickers
added
the
closed-no-further-action
The issue is closed and no further action is planned.
label
Aug 16, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Already posted in the asp.net repo. Wasnt Cure if it´s an ef or identity issue.
Describe the bug
After upgrading to net core 3.0 and related ef core I get an exception
InvalidOperationException: Operation is not valid due to the current state of the object.
What I do is looking for activities for the user:
await _context.Activities.Where(x => x.Owner == user).ToListAsync();
If I check
await _context.Activities.Where(x => x.OwnerId == userId).ToListAsync();
everything is working as expected.
How can I debug this? Any hints what has changed in ef core 3?
This also happens with user set to null.
Smalles Project I can extract:
https://kevinklein.visualstudio.com/NewRepo
The text was updated successfully, but these errors were encountered: