23.20 Breaks watchface layout

Artem 1 month ago

Garmin's testing methods are supreme!
How is it possible to get THIS into public release?!

Top Replies

4024138 1 month ago +4
Garmin's testing methods are truly special. Release notes for the new software 23.20
- Fix an issue that could cause graphical irregularities on some screens.
In Garmin language this actually mean…
Artem 1 month ago in reply to 4024138 +4

I work as software developer.
I just cant understand how such an obvious bug can go through unnoticed.
Not the first time!
Garmin should fire their testers. Or hire some, may be they have none.
Garmin-Maeve 1 month ago +3

We are aware working on a software fix for this. I will update this thread when there is a resolution. In the mean time I have added you to a ticket we have for this. Thank you for your patience.

All Replies

0 4955375 1 month ago in reply to Artem

we are the testers, buddy *sigh*

0 Artem 1 month ago in reply to 4955375

public betas are for public to test.
But I truly cant understand, why was the bug ignored and taken into public release!
This bug was reported almost a week before rollout, garmin could fix it or postpone the rollout. that's why there was a public beta prerelease!
why did they decided to ignore it? Considered minor?

0 Bitti 1 month ago in reply to Artem

Garmin definitely has its software quality problems, but in all fairness, with a large software like a smartwatch firmware, you cannot delay a public release until every single reported bug has been fixed. New bugs are found constantly, and often take time to track, fix, and go through some additional testing. If you waited for all of them to be fixed, you would never release a public version within reasonable time. Garmin seems to try to fix most verified "critical" bugs (watch crashes etc.) before release, but they also seem to have a quite fixed quarterly release schedule.

What I'm more concerned about is how so many bugs end up in firmwares in the first place.

0 Bitti 1 month ago in reply to Bitti

(To put things in perspective, I recently received a notification about a bug I had reported in a major programming language compiler. The notification said it will be fixed in the next major release. But the bug was reported and acknowledged ... 17 years ago!)

0 Artem 1 month ago in reply to Bitti

which software is that?
something from microsoft?
the thing with this particular bug, it was introduced with the latest beta. and it's on the nose!
and really, to align to circles in a single watchface a few pixels shoudn't be so difficult. and there's git, just look it up, how it was before.
Of course, I can't know how it really is. that's why I'm asking. why something like that happens. it's not the first time some obvious, newly introduced UI bugs go through beta, get reported and still land in the release

0 garmindret 28 days ago

Same issue here. Couldn't quite believe it was still there after powercycling the watch. It seems there some potential in Garmin's QA processes.

0 9851030 7 days ago in reply to Garmin-Maeve

Well it's been over a month now, and you still haven't fixed it.

0 Artem 7 days ago in reply to 9851030

Supposedly it's fixed in the new beta

0 Julian 7 days ago in reply to Artem

Yes the beta that was pulled back because of major issues.