Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Actor Proxy does not use same JsonSerializerOptions when deserializing in the non remoting API
See original GitHub issueExpected Behavior
When using ActorProxy Create(ActorId actorId, string actorType, ActorProxyOptions options = null); with custom ActorProxyOptions for the JsonSerializerOptions then ActorProxy.InvokeMethodAsync should use the same JsonSerializerOptions for Deserializaton.
should be changed to return await JsonSerializer.DeserializeAsync<TResponse>(response, JsonSerializerOptions);
Actual Behavior
Since there are discrepancies in the serialization and desalinization the call is successful in the actor but fails to deserialize on the client side.
Steps to Reproduce the Problem
Release Note
RELEASE NOTE:
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Fixed in master for 1.2. Reopening this until I cut a 1.1.2 patch release with this fix.
This was done in 1.1