Saving EXISTING object gets FAULT = 'Server.Processing' exception during method invocation
Hi, I'm aware of several other threads relating to the server.processing exception during method invocation issue. Most of those issues were related to people not adding relations in the new way required in 4.x. I have a different issue in that I'm getting this fault when trying to save an existing object.
I shouldn't have to do a setrelation again on an existing object do I? I really hope not because that would seem extremely backwards to me.
Steps to reproduce:
1) Save object that has a 1:1 relation with BackendlessUser
2 ) Set the relation after saving the object
3) Save the existing object with the user relation set (just save with the object you get from a find)
4) BOOM fault
Currently, if I go and set the user field to nil right before I save the existing object again, it goes through and I have to do another setrelation again. This is definitely a dangerous workaround as now one step save has turned into 2 where if something happens to the network in between, I'll potentially have an orphaned object with no user relation.
Please advise. I'm on 4.0.10 iOS SDK.