[Bug] Countdown timers have been broken for a while now

[ayagikei]

[Bug] Countdown timers have been broken for a while now

[Ayagikei]

Thanks for your feedback, we will reconfirm the issue.

But it needs to be mentioned here that we have fixed a related issue in v1.90.

If it's convincing for you, you can also pay attention to whether the problem occurs again in v1.90.

[Ayagikei]

Thanks for the update :D!

[UsernamesAreNotMyThing]

I believe I have seen it happen again (1.90.2)

[Ayagikei]

I believe I have seen it happen again (1.90.2)

Thanks for the feedback again. We will check it.

[Ayagikei]

In v1.90.3, we made some improvements to this.
You can check to see if it has been fixed.

Before the v1.90.3 version, in the case of unexpected process termination, use multi countdown, etc., we may accumulate the timer to the next use (based on the estimated remaining time).
At the same time, due to an abnormal problem, these non-active accumulations will not be displayed in the countdown pop-up window.
But this may indeed not meet the user's expectations, we decided to remove this logic.

[UsernamesAreNotMyThing]

This is still occurring in 1.90.3, but now it's resetting the timer instead, to where it originally started

[Ayagikei]

This is still occurring in 1.90.3, but now it's resetting the timer instead, to where it originally started

Based on these phenomena, we currently suspect that the system kills the LifeUp process.
Please make sure you turn off the system and the manufacturer's battery optimization policy when running in the background to ensure that the countdown to LifeUp is calculated correctly.
You can refer to: https://docs.lifeupapp.fun/en/#/guide/background_running

The issue may be due to [START_REDELIVER_INTENT] of the Android Service.
After the LifeUp process restarts, the original intent is received, causing the timer to reset or accumulate.
We will try to improve it a bit in the next version. But you should be able to temporarily avoid the problem by doing the above.

[UsernamesAreNotMyThing]

Haven't seen this occur yet in 1.90.4, but I will re-open this if it happens again.

[UsernamesAreNotMyThing]

I just had a timer disappear unexpectedly, and the application has no record of it in the "Countdowns" menu

[Ayagikei]

I just had a timer disappear unexpectedly, and the application has no record of it in the "Countdowns" menu

As mentioned above, these are actually exceptions caused by the system unexpectedly stopping the LifeUp process.

Please check your battery optimization settings.

At present, there is no good solution on the application side. But we will try to investigate.

[UsernamesAreNotMyThing]

I already have battery optimization disabled for this application on my end.

[Ayagikei]

I already have battery optimization disabled for this application on my end.

Please check https://dontkillmyapp.com/.
In addition to Android's battery optimization options, you'll need to disable additional restrictions from various manufacturers.

[UsernamesAreNotMyThing]

My device doesn't fall into any of those brands, so I believe I have done everything I can.

[Ayagikei]

Get it. We will check what we can do on the application side. UsernamesAreNotMyThing ***@***.***> 于 2022年9月17日周六 11:33写道：

…

My device doesn't fall into any of those brands, so I believe I have done everything I can. — Reply to this email directly, view it on GitHub <#36 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG6LAEKODMURTJHRA2BWJKTV6U3YPANCNFSM565O7PMQ> . You are receiving this because you were assigned.Message ID: ***@***.***>

[UsernamesAreNotMyThing]

Still occurs in 1.90.7

[Ayagikei]

We may need to follow up on this issue in v1.91.x.

At present, this problem is due to the restart of the Service after the system is killed. In theory, it will only appear on some devices and the long countdown. The priority will be medium to low.

Sorry, we need to focus on other higher-priority work items first.