• Replies 39 replies
  • Subscribers 28 subscribers
  • Views 6278 views
  • Users 0 members are here
Options
Related

Settings in Groups are not persisted

BobMiles
over 2 years ago

Hi, 

I made a watch face where I offer color settings to the user. I grouped all color settings in one group.

When I change the color settings in the group on the connectiq app it works fine and I can save it. But when I open the settings again, all the settings in the group are reset to their default value.

It does not happen with ungrouped settings. Is this a bug or is there a pitfall I don't know?

Thank you so much! 

Bob 

  • over 2 years ago in reply to flocsy🤠

    Thanks, I already did. I'll keep my hands off of the settings groups for now, although it would be a blessing to be able to group all those color selections... 

  • over 2 years ago

    I've the same problem in iOS.

  • over 2 years ago

    Strange, after 2 months I thought with latest SDK Garmin has it under control, so I reactivated grouping feature in resources of a watchface. It worked for me, but some user reported, that 'save' button is no longer availalbe in connect IQ. I deactivated groupings again .. and user reported everything ok. Strange after 2 month and much more time beta phase.

  • over 2 years ago in reply to forandy

    Bug still exist, any chance to fix?

  • over 2 years ago

    Want to urge this.If there are groups in preferences, many users reporting there is no save button in Garmin IQ app. Meanwhile I'm asking users to complain at Garmin helpdesk ... 2-3 users per day are complaining. Seems to be Garmin is not really urging this issue.

  • over 2 years ago in reply to forandy

    I don't think any more that it's worth trying to use any settings feature that is currently not working. I wasted 3 days refactoring my app to use array settings instead of N*Y separate settings but since this bug haven't been fixed in 3 months it's obviously never will, nor the array settings. The only thing we can hope that things that currently work won't be broken...

  • over 1 year ago

    fortunately, they set up a forum, it saves me from wasting hours trying to work something that does not work

  • over 1 year ago in reply to 5790664

    I would rise the question, why they did not fix within 1 year. Bad to hear, that it's still not working. Feature would be very interesting for more complex apps, but me personally I gave it up.

  • over 1 year ago in reply to forandy

    Because nobody uses it. Not even Garmin. Obviously. Why not? Because no developer will use something that doesn't work and probably will never work. On the other hand the main losers are the users because they would have better apps or the same app functionalities with better, more user friendly settings. If hundreds of users would open bug reports to Garmin about it then maybe they would consider fixing it...

  • over 1 year ago in reply to flocsy🤠
    flocsy🤠 said:
    Because nobody uses it. Not even Garmin. Obviously. Why not? Because no developer will use something that doesn't work and probably will never work. On the other hand the main losers are the users because they would have better apps or the same app functionalities with better, more user friendly settings. If hundreds of users would open bug reports to Garmin about it then maybe they would consider fixing it...

    This feature isn't used because it doesn't work and it doesn't work because it's not used.

    That's really CIQ in a nutshell