-
Notifications
You must be signed in to change notification settings - Fork 27
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
MissingMethodException when running on mono with newer Newtonsoft.Json #118
Comments
Yay, breaking changes are fun! 😭 |
This is particularly weird as we're happily using 12.0.2 internally in our apps' tests. |
Though we're not using the overload that takes a |
Also, I've not tried it on windows with Full Framework, it might be a mono only quirk, not sure yet. |
Actually we are using that overload, it's just that it's an optional parameter: |
If this is a blocker it'll have to wait until .NET Core 3.0 ships in September, because then we can ship a 3.0.0 of this as a breaking change and remove the dependency on (And it would be tidier to ship a 3.0 to go with 3.0 😄) |
I ideally need a fix soonish, my workaround would be running this on core, but we want mono cause it's the closest thing to xamarin iOS/Android which is our target platform. That exception tells me it can't find |
Yeah, it's a weird one. Something about optional parameters and/or a change somewhere in 12.x with |
I'd be happy to look at doing a beta of a 3.0.0 with changes to decouple Newtonsoft.Json in the soon-ish future (within a week?) and pushing it to NuGet to unblock you though. |
That would be amazing, in the meantime if I figure out anything more I'll let you know 😃 |
I'll see if I can pick up the above this week. |
See #127 for a fix candidate. |
Pulled it down and can confirm this has fixed it 😄 Nice one |
This is quite an exotic setup I know, but this has my tests failing in CI, so I'll be looking into this too.
I have an example here:
a776327#diff-ad2944e2db1bf6a75b8602f406da7846R13
When running under mono, if I call
.WithJsonContent(...
then it pops with a runtime exception:In recreating this, I discovered that it's not an issue if you are referencing
Newtonsoft.Json
9.0.1, but if you reference a higher version such as 12.x then this issue pops up.The text was updated successfully, but these errors were encountered: