23.20 Breaks watchface layout

Artem 3 days ago

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

Top Replies

4024138 2 days ago +3
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 2 days ago in reply to 4024138 +3

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 2 days 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 1578985 2 days ago

I have the exact same issue with the same watchface on my Forerunner 255

0 4024138 2 days ago

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 means

Creates an issue that could cause graphical irregularities on some screens

I am hoping mine does not auto update!

0 Artem 2 days ago in reply to 4024138

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.

0 6125703 2 days ago in reply to 4024138

Maybe they fixed it so it causes irregularities on all screens instead of only some?

0 renton82 2 days ago

Reported some days ago: forums.garmin.com/.../incorrect-watchface-dafield-draw

0 Artem 2 days ago in reply to renton82

So Garmin was aware of the bug during beta, But still decided to roll out new version with the bug?

Wtf?

0 Julian 2 days ago in reply to Artem

I do not think Garmin has any testers they could fire.

0 nowster 2 days ago in reply to Artem

Artem said:
So Garmin was aware of the bug during beta, But still decided to roll out new version with the bug?

Probably due to rigidly fixed release schedules.

Anything reported less than two weeks before the release date is unlikely to be fixed in the release.

From past experience there will probably be a minor bugfix release in a couple of weeks time.

It could be worse: wrist-based cadence measurement was broken for about three months in 2022.

0 Artem 2 days ago in reply to nowster

that's literally contradicts the principal of open beta stage!.
if you're right, there no sense to rollout prerelease beta, if the reported bugs won't be fixed

0 Garmin-Maeve 2 days ago

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.