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

Retired gear visible, added gear invisible.

From the mobile app I added a new pair of shoes, and retired another pair. The pair that I retired are still visible in the list, in italics, whereas my previously retired shoes are not. Somehow gear retired from the mobile app are not treated equally as gear retired from the web-version. This is pure discrimination!
In addition, and the biggest problem; the new pair of shoes that I added are NOT visible in the list, so I can't select it from the app.

As ASmugDill stated in this thread: https://forums.garmin.com/forum/into-sports/garmin-connect-mobile-application/garmin-connect-mobile-android/127913-retired-gear-still-appear-on-list Garmin Connect Online does things right and made it possible for me to select the right gear, and once again retire the retired pair. This makes it even clearer that the app is the problem, not the back-end.

But, adding and retiring gear from android app is useless.
  • I'm not seeing what you described.

    I created a dummy pair of shoes using Garmin Connect Mobile app v4.1.8 for Android (running on my tablet), and another using Garmin Connect Mobile app v3.11.1 for Android (running on my handset). Both are listed and available for selection.

    GCMv3 continues to err in listing all gear items, including those that should not be listed, whereas GCMv4 does the right thing.

    But, adding and retiring gear from android app is useless.


    Not true. I subsequently retired the dummy pair of shoes created in GCMv4, using the app itself, and it still does the right thing.

    The pair that I retired are still visible in the list, in italics, whereas my previously retired shoes are not.


    The retirement date is relevant to whether a gear item should be listed for selection against a given activity. Similarly, the first use date is relevant. Did you err in overlooking that detail?
  • Not true. I subsequently retired the dummy pair of shoes created in GCMv4, using the app itself, and it still does the right thing.

    So, are you saying I did get any use out of GCM when I wanted to add and remove gear? (Hint: I needed to visit GC from a computer to fix stuff)

    The retirement date is relevant to whether a gear item should be listed for selection against a given activity. Similarly, the first use date is relevant. Did you err in overlooking that detail?

    Well, if I did set a first use date where logically it would make sense not to show it at the time of creation, then possibly. But I do struggle to even think of a situation where it would be useful to hide a newly added piece of equipment.
    The logic was generally all over the place according to how it looked in my app. I'm now seeing all my retired gear, whereas I only say the latest one some months ago. Currently, things seem to have been corrected, either in the source or on my phone, so whatever my issue was - it's fixed.
  • But, adding and retiring gear from android app is useless.

    So, are you saying I did get any use out of GCM when I wanted to add and remove gear?


    Nice of you to come back and question that after four months.

    Your experience was what it was. My experience was what I described. If you make a general or unqualified statement (i.e. without restricting the scope to your own experience and circumstances) about a particular feature, in a discussion forum obviously for others to read and respond, then I should point out where your statement is not true. Whether you then choose to revise your statement so that it is true for the newly constrained scope is up to you.
  • Nice of you to come back and question that after four months.

    I just expected someone responsible to read about the issue, find the cause and fix it, since this is the only way I know how to report bugs and issues. I wasn't expecting someone telling me my experience was wrong based on their experience and circumstances. I'm sure I would have received a mail if someone important wanted more information about the issue.

    Your experience was what it was. My experience was what I described. If you make a general or unqualified statement (i.e. without restricting the scope to your own experience and circumstances) about a particular feature, in a discussion forum obviously for others to read and respond, then I should point out where your statement is not true. Whether you then choose to revise your statement so that it is true for the newly constrained scope is up to you.


    You've already proven that not everybody's experiences are the same, so of course the uselessness only applies to my experience and circumstances. For a bug report, that's so overwhelmingly obvious I never thought I'd ever have to point it out. And since I only expected people with extensive experience of bug reports to consider the contents of this post, I didn't.
  • If you know of better ways of reporting bugs and issues without having to deal with people questioning the validity of the experience, please let me know. Otherwise I hope we can close this thread.
  • since this is the only way I know how to report bugs and issues.
    But you weren't reporting it to Garmin per se, by creating a thread in this primarily user-to-user discussion forum (provided and hosted courtesy of Garmin); this is not a customer service channel, and while you are Garmin's customer, you are not the customer of 99% of the people who actually read and/or reply to posts here.

    I wasn't expecting someone telling me my experience was wrong based on their experience and circumstances.
    I don't think I'd tell anyone their experience is wrong, but especially in a discussion forum, I'd gladly tell my peers and equals (as fellow Garmin customers, product users, forum members, etc.) that their statements, claims or assertions are wrong – in scope, logic, factual information, whatever – as I see it, and do my best to give a reason why.

    If you know of better ways of reporting bugs and issues without having to deal with people questioning the validity of the experience, please let me know.
    Try a ">https://support.garmin.com/sv-SE/, since your forum user profile states you're from Sweden. Garmin provides official customer-to-business contact channels that do not put the content of communication in open view of other users or the general public.
    ">Google search for “Garmin product support”. Otherwise, I guess you could start at https://support.garmin.com/sv-SE/, since your forum user profile states you're from Sweden. Garmin provides official customer-to-business contact channels that do not put the content of communication in open view of other users or the general public.
  • But you weren't reporting it to Garmin per se, by creating a thread in this primarily user-to-user discussion forum (provided and hosted courtesy of Garmin); this is not a customer service channel, and while you are Garmin's customer, you are not the customer of 99% of the people who actually read and/or reply to posts here.

    I'm not sure they do have any customer service channels concerning GC and GCM. Only for their actual products. Please correct me if I'm wrong. I'd love instructions for how to report issues directly to garmin for exactly GC and GCM.

    I don't think I'd tell anyone their experience is wrong, but especially in a discussion forum, I'd gladly tell my peers and equals (as fellow Garmin customers, product users, forum members, etc.) that their statements, claims or assertions are wrong – in scope, logic, factual information, whatever – as I see it, and do my best to give a reason why.

    Thank you for clarifying. I did interpret your original comments as you were invalidating my experiences because of ignorance. Especially since you started your comment with "Not true". It sounds like I did interpret that to be more harsh than intended, because that IS a powerful rejection. I do appreciate you adding your experiences, especially if they differ from mine. But don't reject mine.

    Try a ">https://support.garmin.com/sv-SE/,
    Garmin Product Support, leads to product support, and as long as my issues are with a specific Product, like the 735xt, I do get support. But since Garmin don't seem to regard GC or GCM as products, perhaps because the warranty doesn't cover the web services, there's nothing there to find. There used to be a "Report Issues"-function at GC, but it was removed years ago, and my many reports of issues through that channel seem to have been sent directly to the incinerator.
    I've also tried to get my issues reported to Garmin SE and Garmin US by sending emails, using support forms and nothing ever happens. No answer, no fixes, nothing. This is the only remaining channel where they might listen, especially if others experience the same thing. That my help you understand my reporting issues here. If the bugs don't apply to you, then fine. Never mind.

    There's one more channel, but I'm not sure creating a bug report for the mobile app by calling their product support makes any sense. I'd hate it if someone reported technical bugs on the phone from when I've been in the position of QA-engineer in a SW-development project.

    ">Google search for “Garmin product support”. Otherwise, I guess you could start at https://support.garmin.com/sv-SE/,
    Garmin Product Support, leads to product support, and as long as my issues are with a specific Product, like the 735xt, I do get support. But since Garmin don't seem to regard GC or GCM as products, perhaps because the warranty doesn't cover the web services, there's nothing there to find. There used to be a "Report Issues"-function at GC, but it was removed years ago, and my many reports of issues through that channel seem to have been sent directly to the incinerator.
    I've also tried to get my issues reported to Garmin SE and Garmin US by sending emails, using support forms and nothing ever happens. No answer, no fixes, nothing. This is the only remaining channel where they might listen, especially if others experience the same thing. That my help you understand my reporting issues here. If the bugs don't apply to you, then fine. Never mind.

    There's one more channel, but I'm not sure creating a bug report for the mobile app by calling their product support makes any sense. I'd hate it if someone reported technical bugs on the phone from when I've been in the position of QA-engineer in a SW-development project.