It's extremely annoying that this type of bug has been around for at least 7 years (dating back to 935 and maybe earlier).
My observations (not exactly a recreation procedure since I'm sure this doesn't happen every time):
- I am using an FR955 with firmware 21.19
- I have two CIQ fields in my Run activity: Lap+ and AppBuilder 5.
- I want to change AppBuilder 5 to Stryd Zones
- Due to another extremely annoying bug (which happens consistently), it's not possible to directly change a data field from one CIQ field to another (which isn't already present in the activity), when the max number of CIQ fields have been added to the activity. In this case, the Connect IQ Fields list only displays the CIQ fields that are already present in the activity. This is apparently because the UI is trying to prevent the user from adding more than the max number. This is valid when you select a data field which does *not* have a CIQ field, but it's not valid when select a data field which *does* have a CIQ field. Clearly changing a field which already has a CIQ field to another CIQ field is not going to put you over the limit.
- Due to the above mentioned bug, I change Stryd Zones to the Timer field. This doesn't quite work, as the field crashes instead of immediately changing to Timer. After closing and reopening the activity, the Timer field is present.
- However, now I only have 1 CIQ field in the activity, but the watch thinks I have 2 (the max). I can tell because when I edit a data field and select Connect IQ Fields, it only shows me the 1 field that's already in the activity. It's the same bug as above, but made even worse because the watch doesn't even know how many CIQ fields are really installed
Power cycling the watch does not resolve this problem. I'm sure I could reset the activity to defaults, but I don't want to do that.
Finally I changed the remaining CIQ field (AppBuilder 5) to the Timer field. At this point I had 0 CIQ fields (the watch seemed to recognize this), and I was finally able to add the 2 CIQ fields I wanted in the first place.
Thankfully there was a workaround for this problem, but it took several minutes to perform a simple action which should have taken a few seconds: change an activity data field from 1 CIQ field to another CIQ field.
From what I've heard, this kind of problem also happens when you uninstall a CIQ data field from the device (remove the app completely), but it's still present in an activity. In this case, the activity will also think it has more CIQ fields than it actually does.
