By "selected" I mean it's used for the field that you're currently editing, as if the user had pressed START when the field was highlighted (and the full-screen prompt was not displayed). This is clearly not what the user intended!
If you dismiss the prompt with BACK, then the prompt will just reappear again, unless you quickly scroll to a different CIQ field which does not make an ANT+ connection.
(I'm not sure if this only applies to apps which try to connect to an HRM or other standard ANT+ device, as Stryd Zones doesn't trigger this problem)
This is just a horrible user experience, especially when combined with the other bug where it's very hard to select a different CIQ field once all your slots are used up (2 on most devices, 4 on Fenix 8). In this case, you have to change one of your CIQ fields to a non-CIQ field before you can change it to a CIQ field that's not already added to the activity.
This is yet another case of a generic prompt causing problems with CIQ apps because it's displayed in a context that was seemingly not anticipated by the implementer of the prompt.
The other recent case is the prompt that appears when an app tries to enable the onboard pulse ox sensor: it simply says something like "this will impact battery life". According to some reports, it's not even possible to dismiss this prompt in some cases.
Do the firmware and CIQ teams talk to each other? Does anyone test anything? There are so many bugs related to simply selecting a CIQ data field on the device.
flocsy🤠 this bug might interest you.
Examples of fields that should cause this problem:
- https://apps.garmin.com/apps/88ce4547-7d84-4289-b2c7-3e15ca00185f
- https://apps.garmin.com/apps/7c83d402-4b68-4f0a-b167-7139788a19b3
So here's my fun workflow for changing a data page field from one CIQ field to another CIQ field, when I'm at already at the 2 field max, even without this bug:
1) Open activity
2) Scroll to data page in question
3) Hold UP for activity menu
4) Press START for activity settings
5) Press START to select "data screens"
6) Press START to edit data page
7) Select Data Fields
8) Select the field I want to change
9) Change the field to Timer (because I'm at the limit, the other bug means that the Connect IQ list will only fields that are ALREADY in the activity, because somebody apparently doesn't realize you can change a field from one CIQ app to another CIQ app without going over the limit). I cannot emphasize how annoying this is
At this point, the change may not even "take" (instead, the CIQ field may remain, although it may also crash). Sometimes I have to press BACK several times to exit the activity, then reopen the activity, before the change takes
10) Go back to step 1 and do all that stuff again except I select the CIQ field I really want to use in step 9
With this bug, in step 10, if I scroll to/past a field that I don't want to select but which makes an ANT+ connection, the natural thing to do is press START to dismiss the full-screen prompt (note that there is no on-screen hint for dismissing it with BACK, and there's no "No" / red X option that would normally be triggered by pressing DOWN). When this happens, the field I didn't want is selected, and I have to do ALL of the steps all over again. What's worse is the prompt will still come up, except this time I know I have to dismiss it with BACK and very quickly scroll past the "bad" app. Either that, or scroll through the list in the opposite direction so I don't highlight the bad app.
If you didn't enjoy reading all of that, imagine what it's like to actually do all of it in real life. Yeah, using touch mitigates some of this stuff (although actually selecting a field via touch is very clunky), but the bugs remain.
Oh and as of this writing the activity I'm testing is stuck is a bad state where I only have 1 CIQ field selected but it thinks I have 2 selected, so it only shows the 1 field under the list of Connect IQ fields. I'll probably have to change that field back to the timer to fix this is as well. btw, real-time settings are also affected by this combo of bugs:
- when max number of CIQ fields is added to an activity, the list of available CIQ fields is limited to the existing fields in the activity, even when editing a field which ALREADY has a CIQ field
- sometimes the activity gets confused and thinks it has the max number CIQ fields even when it really doesn't
idk if anyone at Garmin actually cares whether devs or users enjoy using our watches, or whether it would be a surprise if we sometimes actively hate the user experience..
tbh it doesn't seem like it. All that matters is whether X% of suckers will pay for Connect+, like the guy in the forums with a $3000 MARQ who was salty because he can't pay to get rid of the Connect+ nag banners, despite the fact he has no interest in Connect+
