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

[17.24 BUG] Calendar lists full day events on the wrong day

oBuTTuSo over 1 year ago

Events that cover the entire day gets listed one day too early! (I'm using an iPhone)

In this view it's OK (it says tomorrow for this event):

But inside it's listed under today (Monday)

And this apply for all my future full day events.

(old pictures because I posted this already under beta 17.22 as well, but issue remains...)

https://forums.garmin.com/beta-program/forerunner-965/forerunner-965---public-beta-bug-reports/i/public-beta-version-17-xx/calendar-lists-whole-day-events-on-the-wrong-day

Top Replies

Garmin-Sierra over 1 year ago in reply to Elbo +2 verified

Elbo

I asked because we are no longer reproducing this internally after making some changes.

If you are still experiencing this, please respond to the following:

1. May we, if necessary, reach out via…
Martin over 1 year ago +1

Same here!
Bitti over 1 year ago in reply to micro +1

Yes, the same happens for me too. There's already a bug report for it in the Beta forum, it might be a good idea to add a comment there too: https://forums.garmin.com/beta-program/forerunner-965/forerunner…

All Replies

0 Elbo over 1 year ago in reply to Garmin-Sierra

Garmin-Sierra can you at least tell if this bug is being worked on? And please share a list of bugs that are in the planning to be fixed. I guess garmin developers work in an agile way, and one principle of agile is being transparent, so sharing this with your customers would be a great way to show your customers garmin cares about software quality and working on fixing bugs.

0 Garmin-Sierra over 1 year ago in reply to Elbo

Yes, it is being worked on. I do not have a full list available, but if you have any concerns about specific bugs then I can let you know if they are under investigation, or if they have not been officially reported in our system yet. If anyone has an issue, we ask that they are brought directly to Product Support's attention so a report can be made, and is not solely discussed in forums.

0 Elbo over 1 year ago in reply to Garmin-Sierra

Garmin-Sierra

That is a long list, you’re asking. Some of the more urgent ones (for me)

https://forums.garmin.com/beta-program/forerunner-965/forerunner-965---public-beta-bug-reports/i/public-beta-version-16-xx/gesture-mode-slow-display-activation-with-deactivated-touch-screen

https://forums.garmin.com/beta-program/forerunner-965/forerunner-965---public-beta-bug-reports/i/public-beta-version-16-xx/no-gps-lock-after-continue-activity-and-nowhere-to-see-the-status

https://forums.garmin.com/beta-program/forerunner-965/forerunner-965---public-beta-bug-reports/i/public-beta-version-16-xx/lifetracking-keeps-complaining-after-stopping-an-activity-to-resume-later

0 Garmin-Sierra over 1 year ago in reply to Elbo

Elbo

The first thread you shared was reported in our system, and after reviewing the video showing it was only a one second difference we determined that this is by design. If your delay is taking longer than one second I would ask that you reach out to Product Support with a video example so they can see what you are experiencing.
An experience report was created regarding the GPS 'status' before resuming an activity. This is still under review with no promise of being changed. I ask that you make a new thread about this in the main Forum channel to gain additional impact, since there are no current beta software versions available to the public (all devices are on Public (non-beta) software).
LiveTrack creates a real-time view of your location during an activity, therefore, when 'Resume Later' is chosen and the activity is suspended, the activity is no longer running and neither will the LiveTrack session be running. The message that you see stating LiveTrack Cannot Connect is meant to notify the user that LiveTrack is currently NOT running. I can see how this would be undesirable. Please post in the main Forum channel to gain impact for this as well.

As for your Move Alerts "giving a beep", if you see the notification on the screen, we would expect that after some period of inactivity (usually after 1 hour per Using the Move Alert) So, if you have the activity paused/suspended and are inactive for around that period of time, we expect to see the Move Alert as you normally would. If you believe that you see the Move Alert prior to the 1-hour timeframe, we encourage you to post in the main Forum or reach out to Product Support directly.

0 Elbo over 1 year ago in reply to Garmin-Sierra

Garmin-Sierra 1 second extra delay makes the watch unusable for high intensity track training. This is unacceptable for a running watch.

The “cannot connect to live teacking” does not occur only once. It happens every few minutes, unit you resume the activity or end live tracking. This is not correct behavior.

The move alert suddenly beeps when you resume an activity, and my watch is configured to only beep during an activity, otherwise be silent. I’m not in an activity, because I said I resume later, so move alert such do the alert in the way the watch is configured outside activities. Again, undesired behavior.

0 oBuTTuSo over 1 year ago in reply to Garmin-Sierra

No news regarding this issue? It would be a shame if we'll have to wait until March (?) before getting it resolved...

0 oBuTTuSo over 1 year ago in reply to oBuTTuSo

...and the issue remains in 18.12 :-(

0 Garmin-Sierra over 1 year ago in reply to oBuTTuSo

oBuTTuSo

Can you give me your current Garmin Connect app version?

0 oBuTTuSo over 1 year ago in reply to Garmin-Sierra

4.74.0.30 (on iOS 17.2.1)

0 Garmin-Sierra over 1 year ago in reply to oBuTTuSo

Thank you. It looks like a fix has not been released yet with the Connect app unfortunately. We are working to release the fix as soon as we can!