Starting Timer After Deleting Running Timer Causes App to Crash

[noca2plus]

Steps to reproduce

1. Timer tab
2. Enter 2, 00, Start. Two-minute timer starts as intended.
3. Delete running timer started in Step 2 (press "X"). Remainder of two-minute timer is deleted as intended.
4. Enter 1, 00, Start. App crashes, returns to phone's home.

Expected behavior

Second timer (ie, 1:00) should start. App should continue to be visible.

Actual behavior

As soon as second timer (ie, 1:00) is started, app crashes and returns to phone's home. In some cases, the timer itself persists and can be seen in the notification bar. Left alone, an alarm will occur at the expected time (ie, after 1 minute). Curiously, entering the app again will show the running timer has 0:00 time remaining — inconsistent with time displayed in notification bar.

Clock You version

10.2 (22)

Android version

Android 13 (OxygenOS 13.0)

Other details

No response

Acknowledgements

• I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
• I have written a short but informative title.
• I will fill out all of the requested information in this form.

[Elektron123]

This is super weird since i fail to reproduce it on LineageOS android 16. might be android 13 specific? Im unsure still gotta do some testing

[Elektron123]

Failed to reproduce on stock android 13 too

[noca2plus]

Thanks for looking into this. I also failed to reproduce on Samsung Galaxy A20 running Android 10.

On the OxygenOS 13.0 phone (OnePlus Nord N300), I tried clearing app data and reinstalling from F-Droid. Original problem persisted (app still crashes). I've only got the one OnePlus, so can't test other models.

[Elektron123]

It seems like a OnePlus specific bug, sich kind of sucks since that makes it kind of impossible to debug, maybe its a common issue tho and i will find a fix somehow

[Sup-25498]

Some OEM kill apps..
"Don't Kill Me App" will fix it? I don't sure but maybe,
I don't have this problem but before I had something similar with the stopwatch and timer and I was able to fix it at this time from this website.
https://dontkillmyapp.com/oneplus (or just search "don't kill my app oneplus")
It will show you a guide to fix this bug if it's just related to OEM background process limits, hope it helps you

[Elektron123]

Oh i see, that might actually be the solution, im gonna have to look into if there is a leftover process from deleted timers and if there is patch that issue up. Thank you :)

[noca2plus]

FWIW, I changed what settings I could based on instructions from the Don't-kill-my-app! website. Didn't fix the issue. I installed the app as well, but it seemed to be more of a diagnostic tool than something to intervene on behalf of the Clock-You app.