Skip to content

Bug: The Calculation of timeUntilAlarm is **Not** working as expected when comes to days #827

@Gaurav-Kushwaha-1225

Description

@Gaurav-Kushwaha-1225
Contributor

Description

When the timeUntilAlarm is calculated for displaying the Rings in XYZ, it doesn't include the days part like Rings in 2 days, but the implementation of timeUntilAlarm is made so that it should show these days, too.

So, the timeUntilAlarm has to be rechecked.

Steps to reproduce:

  1. Go to the add/update alarms page.
  2. Add an alarm and change its date to various options available.
  3. You will automatically see that the Rings in XYZ display on top isn't being calculated correctly.

Screenshots

E.g., I created a one-time alarm on various dates, and my current date and time is 19 April, 11:05 AM.

Date 19 Apr Date 20 Apr
Image Image
Date 22 Apr Date 21 Apr
Image Image

Activity

Gaurav-Kushwaha-1225

Gaurav-Kushwaha-1225 commented on Apr 19, 2025

@Gaurav-Kushwaha-1225
ContributorAuthor

I am working on it, it will be resolved soon.

Also, I came across this issue when I was working on #254, where my home widget was working fine and showing Rings in 1 day, but in UAC it was still showing Rings in x hours and y minutes something, for an alarm set for 21 April.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Bug: The Calculation of `timeUntilAlarm` is **Not** working as expected when comes to days · Issue #827 · CCExtractor/ultimate_alarm_clock