[Bug / Feature Request] Silent failure on reading stats sync & request for client-side sync log export #933

Device

X4 Pro

Affected Version

v2.0.0-RC

EPUB Optimization

Yes, using a different EPUB optimizer

Cache State

All of the above

Describe the Bug

1. Silent Sync Failure & False Success Indication:

   • Triggering Sync Books (under File Transfer > Sync Server) fails to update reading statistics to CrossPoint Sync service.
   • Executing a standalone Sync Stats operation also fails.
   • Triggering a manual sync from within the book menu reports a "Success" / completion toast on-device, but no updated metrics or sessions are actually committed or reflected on CrossPoint Sync.

2. Lack of Diagnostic Logging / Error Visibility:

   • When sync operations fail or silently dropped by the server, there is no error messaging, HTTP status code display, or accessible log file on device.
   • On hardware variants where serial output debugging is not accessible, users have no way to inspect failure logs or determine why data failed to sync.

Steps to Reproduce

1. Execute a full sync via File Transfer > Sync Server > Sync Books or perform a Sync Reading Stats operation.
2. Alternatively, trigger a manual sync directly from the in-book reading menu (observing the "Successful" notification on screen).
3. Open the CrossPoint Sync web dashboard and inspect reading statistics.
4. Observe that no reading stats, timestamps, or session progress updates have been recorded on the server.
5. Attempt to locate an error log or sync history within CrossInk settings (no log file or error viewer is available).

Expected Behavior

1. Accurate Sync Validation & Error Statuses:

   • If an API request fails, times out, or encounters payload errors, the UI should report an error state rather than showing a false "Success" toast.

2. On-Device / Exportable Sync Logs:

   • Implement a client-side error logging mechanism (e.g., generating a sync.log file on the SD card root/storage or adding a "View Sync Logs" panel in Settings).
   • Include standard diagnostic details in the log (timestamp, endpoint URL, HTTP response code, and error stack trace/message) to assist with troubleshooting without needing physical serial output access.

File Provided

Not Applicable

Relevant Log Output/Screenshots