Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suntimes Event Alarm error is Moon Phase alarm repeat. #803

Closed
MyHeadHurtsNow opened this issue Jun 6, 2024 · 2 comments · Fixed by #807
Closed

Suntimes Event Alarm error is Moon Phase alarm repeat. #803

MyHeadHurtsNow opened this issue Jun 6, 2024 · 2 comments · Fixed by #807
Labels
Milestone

Comments

@MyHeadHurtsNow
Copy link

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:

  1. Day before the next New Moon, create a new alarm in Suntimes Alarm App
  2. Choose "New Moon" from the Event drop down menu
  3. Save alarm, and close Suntimes Alarm app
  4. Let alarm go off the next day as scheduled and dismiss.
  5. 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

  1. Screenshot_20240606_141847_Suntimes
  2. Screenshot_20240606_141746_Suntimes
  3. Screenshot_20240606_142239_Suntimes

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.

forrestguice added a commit that referenced this issue Jun 9, 2024
adds failing test that detects #803
@forrestguice
Copy link
Owner

Thanks for the detailed report. 👍
I was able to reproduce this bug, so likely it will be fixed soon.

@MyHeadHurtsNow
Copy link
Author

MyHeadHurtsNow commented Jun 9, 2024 via email

forrestguice added a commit that referenced this issue Jun 17, 2024
@forrestguice forrestguice added this to the v0.15.16 milestone Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants