Identify and resolve client-side issues while debugging the application.
Check the log record on the device. Use the getLogRecords (SUPQQuery) or getLogRecords methods.
This is the log format
level,code,eisCode,message,component,entityKey,operation,requestId,timestamp
This log format generates output similar to:
level code eisCode message component entityKey operation requestId timestamp 5,500,'','java.lang.SecurityException:Authorization failed: Domain = default Package = end2end.rdb:1.0 mboName = simpleCustomer action = delete','simpleCustomer','100001','delete','100014','2010-05-11 14:45:59.710'
SUPConnectionProfile *cp = [SMP101SMP101DB getConnectionProfile]; // To enable trace of client database operations (SQL statements, etc.) [cp enableTrace:YES]; // To enable trace of client database operations with values also displayed [cp enableTrace:YES withPayload:YES]; // To disable trace of client database operations [cp enableTrace:NO]; // To enable trace of message headers sent to the server and received from the server // (this replaces the MBODebugLogger and MBODebugSettings used in earlier versions of SUP) [cp.syncProfile enableTrace:YES]; // To enable trace of both message headers and content, including credentials [cp.syncProfile enableTrace:YES withPayload:YES]; // To disable messaging trace [cp.syncProfile enableTrace:NO];