You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I set an alarm for today's New Moon as an Event, which fired off on time and as set. But, the auto repeat showed the Next New Moon to be August 4th, 2024 @ 12:13 hrs BST, which is 58d 22hrs ahead. This is incorrect. The next new moon is actually July 5th, 23:57 BST
To Reproduce
Steps to reproduce the behavior:
Day before the next New Moon, create a new alarm in Suntimes Alarm App
Choose "New Moon" from the Event drop down menu
Save alarm, and close Suntimes Alarm app
Let alarm go off the next day as scheduled and dismiss.
Open up Suntimes Alarm app and check the next scheduled New Moon Event Alarm. You will see the error, where it has skipped
Expected behavior
The next scheduled New Moon Event alarm should be at the date and time of the next New Moon as calculated on Suntimes app, which is approximately 29 days ahead
Screenshots
Screenshots attached
Version Info:
App Version: [ 0.15.15]
Android Version: [ 14]
Device Model: [Samsung Galaxy A13 model SM-A137F/DSN]
Additional context
Add any other information about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
I set an alarm for today's New Moon as an Event, which fired off on time and as set. But, the auto repeat showed the Next New Moon to be August 4th, 2024 @ 12:13 hrs BST, which is 58d 22hrs ahead. This is incorrect. The next new moon is actually July 5th, 23:57 BST
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The next scheduled New Moon Event alarm should be at the date and time of the next New Moon as calculated on Suntimes app, which is approximately 29 days ahead
Screenshots
Screenshots attached
Version Info:
Additional context
Add any other information about the problem here.
The text was updated successfully, but these errors were encountered: