Debug

Tracking Debug Messages

We can track clients' debug messages by aware_debug table on an AWARE database. This section describes tracking techniques of debug messages on the aware_debug table.

Trace AWARE iOS Events Using aware_debug Table

When an AWARE iOS client joins a study (after reading a QR code), the client creates an aware_debug table on the AWARE database. To the table, AWARE iOS stores debug messages such as the progress of data upload, software updates, and application crash reports.

The table structure is as follow:

Field	Type	Description
_id	int	unique id
timestamp	double	unixtimestamp
device_id	varchar	device_id
event	text	event description
type	int	type of event (0=unknown, 1=information, 2=error, 3=warning, 4=crash)
label	text	label of the event
network	text	network condition (e.g., wifi, mobile, no)
app_version	text	application version (e.g., 1.6.0)
device	text	device type (e.g., iPhone5s, iPhone6, and iPhone6s)
os	text	version of operationg system (e.g., 9.1)
battery	int	current battery level (schale=0-100%, unknown=-100)
battery_state	int	current battery state (0=unknown, 1=unplegged, 2=charging, 3=full)

Track the application error, warning and crash messages

Please search the type field with event types(0=unknown, 1=information, 2=error, 3=warning, 4=crash) on the aware_debug table.

select * from aware_debug where type=2;

Monitor speeds of data upload

Please search event table with %KB/s%.

select * from aware_debug where event like "%KB/s%";

Check progress of software update

Please search event field with %software%.

select * from aware_debug where event like "%sotware%";

Show progress of data upload

Please search event field with %[%]%/% or %[sensor_name]%/%;

select * from aware_debug where event like "%[%]%/%";