@cfc yes, totally understandable.
Yesterday I ran with the AW7 and AWU for comparison purposes, and since settings can be changed on the watch itself I did just that without worrying about having the iPhone app synchronization.
I suppose that it would still be nice to have WOD indicate the name of the Apple Watch it's operating on currently to avoid confusion, since this can change unexpectedly when Auto Switch is enabled.
There are plenty of features / fixes I'm hoping for first before further multi-watch support as well 😋
Especially the graph duration feature request I wrote a few days back.
Different issue report
Including a new issue report today, regarding the FIT file generated that doesn't pass Garmin FIT SDK's Activity File Validator (FitTestTool.jar)
Code:
Activity File Validator
Opening file: Marathon_distance_run_on_asphalt_gravel_and_single_track.fit
Decoding file...
File decoded
Message Count: 16140
FileId Message Exists - Level: REQUIRED Status: PASSED
FileId Message Is First - Level: REQUIRED Status: PASSED
FileId Message Type Is Activity - Level: REQUIRED Status: PASSED
FileId Message Manufacturer Id Exists - Level: REQUIRED Status: PASSED
FileId Message Time Created Exists - Level: REQUIRED Status: PASSED
Activity Message Exists - Level: REQUIRED Status: PASSED
Activity Message Timestamp Exists - Level: REQUIRED Status: PASSED
Activity Message Local Timestamp is Valid - Level: REQUIRED Status: PASSED
Activity Message total_timer_time is Equal to the Sum of Session Messages total_timer_time Values - Level: REQUIRED Status: PASSED
Activity Message Session Count Is Equal To Actual Session Count - Level: OPTIONAL Status: PASSED
Session Message Exists - Level: REQUIRED Status: PASSED
Session Message Timestamps are Valid - Level: REQUIRED Status: PASSED
Session Message Start Time Is Valid - Level: REQUIRED Status: PASSED
Session Message Total Timer Time and Total Elapsed Time are Valid - Level: REQUIRED Status: PASSED
Session Message First Lap Index and Num Laps are Valid - Level: REQUIRED Status: PASSED
Session Message total_timer_time is Equal to the Sum of Lap Messages total_timer_time Values - Level: REQUIRED Status: FAILED
Session message total_timer_time does not equal the sum of Lap messages total_timer_time values.
Session Message total_elapsed_time is Equal to the Sum of Lap Messages total_elapsed_time Values - Level: REQUIRED Status: FAILED
Session message total_elapsed_time does not equal the sum of Lap messages total_elapsed_time values.
Session Message Sport Exists - Level: REQUIRED Status: PASSED
Session Message Sub Sport Exists - Level: OPTIONAL Status: PASSED
Session Message Are Sequential and Abut - Level: REQUIRED Status: SKIPPED
Check requires two or more Session messages, found 1.
Session Message Valid Message Index - Level: REQUIRED Status: PASSED
Lap Message Exists - Level: REQUIRED Status: PASSED
Lap Message Valid Message Index - Level: REQUIRED Status: PASSED
Lap Message Start Time and Timestamp are Valid - Level: REQUIRED Status: FAILED
One or more Lap messages contain an incorrect Start Time and/or an incorrect 'End Time' relative to the Session message.
Lap Message Are Sequential and Abut - Level: REQUIRED Status: FAILED
Lap messages are not sequential, or do not abut.
Record Message Timestamps Fall Within Session Message Times - Level: REQUIRED Status: PASSED
Record Messages Are in Chronological Ascending Order - Level: REQUIRED Status: PASSED
Device Info Message Timestamps are Valid - Level: REQUIRED Status: PASSED
Device Info Message Device Index is Valid - Level: REQUIRED Status: PASSED
Device Info Message Manufacturer Id is Valid - Level: OPTIONAL Status: PASSED
Keeping only the FAILED tests:
Code:
Session Message total_timer_time is Equal to the Sum of Lap Messages total_timer_time Values - Level: REQUIRED Status: FAILED
Session Message total_elapsed_time is Equal to the Sum of Lap Messages total_elapsed_time Values - Level: REQUIRED Status: FAILED
Lap Message Start Time and Timestamp are Valid - Level: REQUIRED Status: FAILED
Lap Message Are Sequential and Abut - Level: REQUIRED Status: FAILED
Passing or not is not a big deal in itself as Strava or Intervals.icu parse the FIT file anyway.
FIT File Viewer, which is usually pretty strict has no objection either.
However
Quantified Self, an amazing free tool to compare or combine activities recorded with different devices using its merge functionality is unable to parse the FIT files generated by WOD.
If I take the WOD FIT file, put it in Fit File Tools's section remover, strip the end of the activity and download the result, the output works in Quantified Self, so that has been my workaround so far. That file still as some FAILED items but they don't trip Quantified Self.
I don't know if I mentioned it earlier but I'm working on my own fitness app at the moment (for walking treadmills, on Android) so I went deep on making 100% compliant and rich FIT files. I can help dig into this further.
The FIT file is attached, but they essentially all have the same problem loading in Quantified Self (and maybe some other platforms as well)