Golf Widget Bug after Update

There is a bug in the golf widget after updating the firmware. If you click within the golf widget, the watch crashes and reboots.

I think this bug first appeared in 9.97. It was claimed to have been fixed in 9.98, but has reappeared in both 10.75 and 10.77.

The only workaround is to save a round of golf after the firmware update, before clicking in the golf widget.

0 Gr4z over 5 years ago

Works fine for me, never seen that on any previous firmware either. I am now on 10.77

0 Pasoderb over 5 years ago

Works fine for me too (haven't playd a round after update to 10.77).

0 Niterider4 over 5 years ago

Interesting. When it was reported back in 9.97 I didn't see it. But with 10.75 I did, until I saved a new round.

The golf activity works fine. And the golf widget works fine, if I just look at it. But if I click for more details within the golf widget, that crashes the watch. This is only right after I update the firmware.

In any event, the golf widget is kind of useless because it doesn't show you a hole-by-hole score. It treats golf like any other activity, and shows you steps, distance, duration - not stuff a golfer is terribly interested in.

I did notice improvements to the golf widget in 10.75/77. Now it shows you your handicap and net score, but a hole-by-hole score would be a big improvement.

0 Gr4z over 5 years ago in reply to Niterider4

I like the new widget. It shows you for your last round: no of pars, birdies etc ,fairways hit, GIR, No of putts, steps/distance/time. Not much else I would want to look at on such a small screen.

0 TigerGPS over 5 years ago

I saw the same thing. Appeared to combine the last two rounds in the widget after update and crashed the watch. After recording a new round the widget problem has gone away.

0 SevenEleven711 over 5 years ago

Same here, but in version 11.10. Reproducable every time. Seems to have combined two different scorecards (not even the latest ones) and crashes the watch every time once accessing the details of the round.

0 Niterider4 over 5 years ago in reply to SevenEleven711

Same here. The bug goes away once you play and save a new round.