Sunrise/Sunset complication will only show values for tomorrow

[ch00f]

Running Second Movement 866cbb1
on SensorWatch Pro with custom LCD
Steps to reproduce

• Set current timezone to UTC-7 (Seattle)
• Set Current Date/Time to 25-07-19 6:30pm
• Set Sunrise/Sunset location to 47.50N 122.23W
• Open Sunrise/Sunset face

Expected behavior
Sunset time is shown for July 19 since it is currently daylight outside. Watch displays "SET 19" with the correct sunset time. Pressing the alarm button shows "RIS 20" with tomorrow's sunrise time.

Observed Behavior
Watch displays sunrise time for tomorrow. Face displays "RIS 20." Pressing the alarm button shows the set time for the 20th. There is no way to see the set time for today.

---

I believe this bug has existed on the original SensorWatch since it always defaulted to set time for me during the day. It wan't until I got the custom LCD with the date in the corner that I realized it was showing me tomorrow's info.

[JohnQuincyAddingMachine]

I have noticed this as well (same time zone, though UTC-8 as of today). What I've noted is that in the morning, it properly shows the sunset time for today, but it rolls over to tomorrow's sunrise far too early. What I believe could be the case but haven't taken the time to confirm, is that the rollover might be happening on UTC time rather than the local time zone.

In other words, if UTC-8's sunset time is 17:07, it could be rolling over at 09:07 local time (17:07 UTC) rather than 17:07.

[mmahoney2025]

I did some testing on the simulator and the code appears to pass the current date in UTC to the sunrise/sunset calculation function. After midnight UTC it will pass the new date (tomorrow before today's sunset local time Pacific for example) to the sunrise/sunset calc and there's no checj to roll backwards a day.

Shows up more often in summer and timezones further behind UTC.

[voloved]

I'm worried this may impact the preset logic. I'll take a look after Thanksgiving to make sure it doesn't