Kartal Kaan Bozdoğan

@davimacedo The PR now uses the latest SDK release, which includes the INVALID_VALUE error code

[These lines](https://github.com/parse-community/Parse-SDK-JS/blob/ffc523f9cd0fa2dd3fcc9754d5f15c3c1c78314f/src/ObjectStateMutations.js#L119-L121) should probably be doing a deep-copy. Feels like we should also remove line 138 and the spread at line 139.

Whoops. Fixed.

Makes sense. I haven't been able to dig deeper into the code, but thought it was interesting that there was an (albeit harmless) overflow. My colleagues and I are working...

I have verified that the SDK sends a malformed request to the server, so this is an SDK issue.

I am afraid not, @mtrezza . Feel free to transfer the issue. We ended up working around it.

@dplewis Strange that you cannot replicate it. I tested it with #1451 and the issue was still there. Did you follow the steps in #1452?

@dplewis Added the test with small modifications

Fixed after #1451