Error handling data: Argument cannot be null
Re: Error handling data: Argument cannot be null
No, that's not an issue. The only problem we see is when you are hammering the phone with too many packets per second. At that point you may end up with corrupt data. In your case the data is fine.
-
alienwoods
- Posts: 11
- Joined: 10 Mar 2014, 13:41
Re: Error handling data: Argument cannot be null
Bit of an update,
I crosschecked the ObjectMover's Unity C# with our existing Unity C# code and it seems the problem occured because we used ISFS object in the send function ( NetworkConnector/RequesTile() ). After i switched the variable type to simple SFSObject type from ISFSObject, the serialization error, and the Argument null not occurs anymore.
I crosschecked the ObjectMover's Unity C# with our existing Unity C# code and it seems the problem occured because we used ISFS object in the send function ( NetworkConnector/RequesTile() ). After i switched the variable type to simple SFSObject type from ISFSObject, the serialization error, and the Argument null not occurs anymore.
Re: Error handling data: Argument cannot be null
Oh really? 
Can you show me exactly how you changed the code? Both the "before" and the "after"?
ISFSObject is just an innocuous interface
I cannot think of a good reason why it should wreak havoc in iOS, but again... we have no idea about what Unity does during the export, so in theory anything is possible.
Can you show me exactly how you changed the code? Both the "before" and the "after"?
ISFSObject is just an innocuous interface
I cannot think of a good reason why it should wreak havoc in iOS, but again... we have no idea about what Unity does during the export, so in theory anything is possible.