Client-Side Debugging

Identify and resolve client-side issues while debugging the application.

Problems on the device client side that may cause client application problems:

Unwired Server connection failed - use your device browser to check the connectivity of your device to the server.
Data does not appear on the client device - check if your synchronization and personalization parameters are set correctly. If you are using queries, check if your query conditions are correctly constructed and if the device data match your query conditions.
Physical device problems, such as low memory - implement ApplicationCallback.onDeviceConditionChanged to be notified if device storage gets too low, or recovers from an error.
Unwired Server connection failed. Use your device browser to check the connectivity of your device to the server.
Data does not appear on the client device. Check if your synchronization and personalization parameters are set correctly. If you are using queries, check if your query conditions are correctly constructed and that the device data matches your query conditions.
Physical device problems, such as low battery or low memory.

To find out more information on the device client side:

If you have implemented debugging in your generated or custom code (which Sybase recommends), turn on debugging and review the debugging information. See the API Reference information about using the Logger class to add logs to the client log record and synchronize them to the server (viewable in Sybase Control Center).
Check the log record on the device. Use the <PkgName>DB.getLogRecords (com.sybase.persistence.Query) or Entity.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'
            
```
- level – the log level currently set. Values include: 1 = TRACE, 2 = DEBUG, 3 = INFO, 4 = WARN, 5 = ERROR, 6 = FATAL, 7 = OFF.
- code – Unwired Server administration codes.
  - Synchronization codes:
    200 – success.
    
    500 – failure.
- eisCode – maps to HTTP error codes. If no mapping exists, defaults to error code 500 (an unexpected server failure).
- message – the message content.
- component – MBO name.
- entityKey – MBO surrogate key, used to identify and track MBO instances and data.
- operation – operation name.
- requestId – operation replay request ID or messaging-based synchronization message request ID.
- timestamp – message logged time, or operation execution time.
If you have implemented ApplicationCallback.onConnectionStatusChanged for synchronization in the CallbackHandler, the connection status between Unwired Server and the device is reported on the device. See the CallbackHandler API reference information. The device connection status, device connection type, and connection error message are reported on the device:
- 1 – current device connection status.
- 2 – current device connection type.
- 3 – connection error message.
For other issues, you can turn on SQLTrace trace on the device side to trace Client Object API activity. To enable SQLTrace using the ConnectionProfile's enableTrace API:
```
// To enable SQL trace with values also displayed
SUP101DB.getConnectionProfile().enableTrace(true, true);
```