This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Pool workout interface problems

Hi all.

With Garmin Connect app for iOS 4.72.1.3 on iOS 17.0.1, pool swimming equipment is shown as “equipment_type_<something>” instead of the equipment name (e.g. equipment_type_fins for fins).

While trying to add a step with equipment, after workout save, the wrong equipment is set, usually the one before the right one in the list.



Furthermore, if Drill is selected for a step, during training the watch shows a normal step with distance instead of the drill clock.

Tried without luck the workaround to select the previous element (Butterfly), won’t work.

I am forlorn cause this has some direct impact on training.

Watch is a Fenix 6 Solar 26.00 enrolled in beta program, but I don’t think it’s relevant, because issues are generated by/in the app and pushed to the phone, which is passive in this workflow.

Bye.

  • Hi, I am having the same issues! Super frustrating especially the Drill function.

    I sadly don’t have a work around but desperately searching for one

  • Glad to hear that I am not alone in this.

    Additionally: snorkel equipment is not selectable due to the nature of the bug.

    If it is a pointer mismatch in the equipment list/array, there is no way to select snorkel, because selecting the first element (fins) does not point to the last (snorkel), cause the list is not circular and selecting fins results in no equipment selected, when getting back to the workout steps screen.

    I might add that during equipment selection, having the first element already selected does not help: user must select a different one first, then get back in the step and select the first one, only then the Connect app shows the right input.

  • I have found that if you create the workout on the Garmin Connect website (not through the app) it allows you to select drill and the correct equipment and sends through to the watch correctly.

    Bit of a workaround until they update the app

  • I confirm that creating/editing workouts throughout Connect web interface as workaround, fixes the iOS Connect app glitches.

    Garmin: weeks have gone by since this issue arose and is evidence of a poor QA: it is a big overlook on your side and a code with an issue this big should never be distributed. So much for software lifecycle, CI/CD, agile development and so forth… And the fact that a workaround has been found does not count as a solution.

  • With version 4.73.0.21 of Garmin Connect App for iOS equipment labels have been fixed.

    But the issues with workouts are still present:

    - to save the correct equipment, the element below must be selected (snorkel to get pull buoy, paddles to get kickboard)

    - drill not propagated to watch

    ”Funny” thing: if you save a workout with paddles to get kickboard and re-edit it, you get fins (because kickboard is selected).

  • Problem persists with 4.73.1.6 version of the app.

    In the equipment list, selecting a component, upon save, the workout sent to the watch contains previous equipment in the list.

    Drill stroke is ignored if selected in a workout step.

    Setting up the workout from web interface is used as workaround.

    Watch firmware went back and forth from 26.82 beta to 26.85 beta, then 26.00 official and reverting to 26.85 beta due to an altimeter issue.

    Bye.

  • Today the app has been updated to version 4.74.0.30.

    Equipment “shifting” after workout save is still present.

    Stroke even if selected is not propagated to the watch, specifically “Drill” stroke.

    Garmin Connect Web interface is still the workaround for this issue.

  • Drill stroke and equipment shifting issues still persist with version 4.72.2 of the app.

  • No changes in v4.74.3.

    I cannot think that there are only 2 users who are experiencing this problem. Even if that would be the case, the app has a feature which is not working properly: please fix it. 
    It is easily replicable, it is not device dependent, it would need less than a day to debug and fix.

    And there isn’t abother way to report an issue except posting here, so anyone would expect that a community manager/QA person would read it and report to devs.

    Please Do! Or give me a more direct/efficient/effective way to report this!

  • Did you try reporting it to Garmin's Support? It is uncertain they spot your post here, on the user forum