Problem: Sometimes when assigning a personalization key that uses a binary datatype
to an operation argument or load argument with BIGBINARY type, the server throws exceptions
during synchronization.
[LNSupController+Finalize.m:61] Send data ExceptionSUPPersistenceException:
SUPPersistenceException from synchronize: – SUPSynchronizeException:
loginFail,Sync failed: -1497 (ERROR) %1:4 %2:4000
Explanation: This can happen if the data in the personalization key exceeds 35K.
Solution: None. When a binary personalization key is assigned to an operation
argument or a load argument, its size cannot exceed 35K. Additionally it is not
recommended to map a personalization key to big object types such as BIGSTRING or
BIGBINARY. For additional information, see these topics in
Mobile Data Models: Using Mobile Business
Objects:
- Datatype Support
- Creating Structure Types That are Compatible With Large Object Types
for Client Parameters and Personalization Keys