It may be me, but - if I try to sync my FR230 (same behavior with 235) via Bluetooth to my iPhone, and I don't have a wireless network available for GC (i.e. either I'm on LTE with the app not enabled for data over the network, or WiFi + LTE turned off), the watch syncs to the phone, long progress, until the end - and then the transfer fails, 'no network available' or something similar. Turn data connection back on, sync, the whole sync starts all over again, obviously no data was cached on the iOS device, and then syncs successfully. So:
1. There is no data storage allowed on the iOS device at the end of the sync?
2. If network connectivity is thus a pre-requisite, and data will not be cached on the iOS device, would it not make sense to generate the error message at the *beginning* of the sync cycle rather than at the end? You know you're transfering data you won't be able to send to the Garmin server, save yourself some pain...
The simple fix to this would be to generate the error message up front. The more complicated (but much better user-wise) fix would be to allow the iOS device to hold on to activity data from the sync, until the next time network connectivity is available and then sync from the iOS device to the Garmin servers.
