-
Notifications
You must be signed in to change notification settings - Fork 22
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
JsonSerializationException when logging in (ApiContext.Create) #135
Comments
Having the same for the Java SDK. It's been almost 24 hours now. |
Have made a pull-request that solves the issue |
The same issue here (production), would be very nice if the PR got published asap ;)... |
Sorry for being harsh, but I believe as a bank, completely breaking your SDKs overnight and taking this much time to fix it is not acceptable. |
I cannot believe Bunq make a change to API model without updating Document or SDK Nuget , |
Hey, guys 👋We've resolved the issue. It must work now. |
Are we back to original? Can you please clarify? I patched SDK manually to accept Array of DirectoAlias Object and today it stopped working again today! |
Steps to reproduce:
Log in with ApiContext.Create()
What should happen:
Make use of api
What happens:
JsonSerializationException
Newtonsoft.Json.JsonSerializationException: "Cannot deserialize the current JSON array (e.g. [1,2,3]) into type 'Bunq.Sdk.Model.Generated.Object.LabelUser' because the type requires a JSON object (e.g. {"name":"value"}) to deserialize correctly.\nTo fix this error either change the JSON to a JSON object (e.g. {"name":"value"}) or change the deserialized type to an array or a type that implements a collection interface (e.g. ICollection, IList) like List that can be deserialized from a JSON array. JsonArrayAttribute can also be added to the type to force it to deserialize from a JSON array.\nPath '[2].UserCompany.director_alias', line 95, position 25."
Traceback
SDK version and environment
Response id
Extra info:
The text was updated successfully, but these errors were encountered: