Device Model: Garmin Venu 3S
Phone Hardware/OS: iPhone / iOS
Garmin Connect App Version: Latest iOS release
Garmin Connect App Version: Latest iOS release
Problem Summary:
A parsing conflict exists between the Garmin Connect app engine and the native iOS background event database. The calendar synchronization engine treats local time slots using absolute UTC values instead of evaluating local device time offsets. This creates a hard cutoff window for afternoon and evening events, completely erasing them from the Garmin Event Glance widget.
A parsing conflict exists between the Garmin Connect app engine and the native iOS background event database. The calendar synchronization engine treats local time slots using absolute UTC values instead of evaluating local device time offsets. This creates a hard cutoff window for afternoon and evening events, completely erasing them from the Garmin Event Glance widget.
Steps to Reproduce:
- Pair a Garmin Venu 3S to an iPhone with Garmin Connect background permissions set to "Always".
- Set the watch Sleep Window to standard night hours (e.g., 10:00 PM to 6:00 AM).
- Populate an active entry inside the Apple Calendar app for a specific local evening time slot (e.g., 7:00 PM).
- Run a manual cloud data synchronization cycle within the Garmin Connect app. [1]
Observed Result:
The 7:00 PM appointment is hidden from the wrist-based Event Glance widget. If the user is in a North American time zone (such as Mountain Time, UTC-6), the sync engine erroneously adds the offset hours to the event time stamp. A 4:00 PM local event registers within the Garmin app log as 10:00 PM UTC. Because 10:00 PM triggers the watch’s internal sleep/rest logic filtering threshold, all time-stamped events scheduled past 4:00 PM are suppressed from view.
The 7:00 PM appointment is hidden from the wrist-based Event Glance widget. If the user is in a North American time zone (such as Mountain Time, UTC-6), the sync engine erroneously adds the offset hours to the event time stamp. A 4:00 PM local event registers within the Garmin app log as 10:00 PM UTC. Because 10:00 PM triggers the watch’s internal sleep/rest logic filtering threshold, all time-stamped events scheduled past 4:00 PM are suppressed from view.
Verifying Workaround Factor:
This is confirmed to be an app processing calculation failure because designating the entry as an "All-Day Event" completely bypasses the logic loop and successfully forces the text block to appear on the watch face. Standard daily alerts and text notifications continue to push normally to the wrist hardware after 4:00 PM.
This is confirmed to be an app processing calculation failure because designating the entry as an "All-Day Event" completely bypasses the logic loop and successfully forces the text block to appear on the watch face. Standard daily alerts and text notifications continue to push normally to the wrist hardware after 4:00 PM.
Already executed a forced GPS time alignment and checked online user profile preferences to rule standard user setup configuration issues.