wiki/racecommittee-app-administrator.md
... ...
@@ -77,4 +77,34 @@ In the **Regatta** tab of the AdminConsole click the **Edit** action of the rega
77 77
78 78
## On-Device Configuration
79 79
80
-As stated above it is possible to (re-)configure these preferences in the app. Changes on the device will not be synchronized with the server.
... ...
\ No newline at end of file
0
+As stated above it is possible to (re-)configure these preferences in the app. Changes on the device will not be synchronized with the server.
1
+
2
+## Troubleshooting
3
+
4
+Let's have a look at the most common problems.
5
+
6
+### Connectivity
7
+
8
+In the top right corner three dots indicate the connectivity status. If there is a problem with sending or receiving data to/from the server the dots will turn red. The device will re-try to send data every minute.
9
+
10
+![Connectivity ok](wiki/images/rcapp/app_conn_ok.jpg) ![Connectivity bad](wiki/images/rcapp/app_conn_bad.jpg)
11
+
12
+If your device users are experience persistent connectivity issues advice them to click on the three red dots. This will display further information including the last successful sent time. Recheck that the device has an overall network connectivity and check if your server is not accepting the data sent by the device. This might be the case when the RaceCommittee App is trying to send data for already deleted/renamed regattas.
13
+
14
+![Expert view](wiki/images/rcapp/app_expert.jpg)
15
+
16
+Selecting the "Expert information" option you'll have access to the expert information screen. This screen gives you the chance to have a look at all the data which could not be sent. Additionally you stop the device from trying to send this data by clicking on "Clear Events".
17
+
18
+### Failure to load data
19
+
20
+When trying to logon onto a course area the RaceCommittee App opens an error dialog showing an error similar to "Failure to load data: 'null'" or something more expressive. Most of the times this happens when the current version of the app is not compatible with the server. Redo the synchronization step or even force an update via the app's preference screen.
21
+
22
+### Runtime- and Crash-Logs
23
+
24
+For further fault localization the app maintains runtime-logs. They are stored on the (emulated) SD-Storage partition under
25
+
26
+ /sd/racecommittee/DATE.log
27
+
28
+In the case of a crash due to a unchecked exception to app writes to a crash log located in
29
+
30
+ /sd/racecommittee/DATE_crash.log
... ...
\ No newline at end of file