They don't work for me either. It's a shame, since I always forget to tick my boxes in the morning.

Yea, sorry, I can't currently find the time to work on Tickmate 😞

Just to add that it used to work for me on Android 6 but on current versions (9 and now 10) it doesn't work.

Please re-open this issue if the problem persists in v1.4.13. Thanks @cipo7741

re-open this issue if the problem persists in v1.4.13

Persists for me, using v1.4.13 ☹.

Worked reliably on Android 9, but not on Android 10.

Strange indeed. Re-opening this but unfortunately I currently do not have the time to work on it

Strange indeed.

It gets better; since posting my previous comment, I tried something based on a hunch (from far too much experience with the oddities of complex systems).

1. Opened Tickmate
2. Enter Settings UI
3. Disable reminder notification entirely
4. Completely exit Tickmate (back arrow until display shows home / launcher, then swiping up on the app-switcher UI to dismiss Tickmate)
5. I didn't force-kill Tickmate, in this first attempt, but would've in the next had this one failed
6. Relaunch Tickmate
7. Reenter Settings
8. Re-enable reminder notification
9. Wait until the time of when it was configured to fire (for me, that's mid-evening)

To my perplexed (but pleased) surprise, a notification appeared for the first time in many months.

Just to be sure: Samsung and many other phones now by default use features that stop some apps from running in the background or triggering notifications to save battery life. On Samsung phones this is called "deep sleep". Is it possible that this type of feature is preventing tickmate from creating notifications on your phone?

Since Android 12 I've had similar issues with several apps that were put into deep sleep even though I use them regularly. If you use a Samsung phone, you can find more information here.

On Samsung phones this is called "deep sleep". Is it possible that this type of feature is preventing tickmate from creating notifications on your phone?

I've diligently disabled a whole bunch of such misfeatures, including the sleep-mode you describe. However, I'll recheck.

I wouldn't be surprised if it does turn out to be an OS problem, though.

Most annoying, since I keep my device connected to an external power source (either a mains-powered charger, or external battery), so I should never encounter low-battery conditions. But, alas.

I tried something based on a hunch

After that bit of black-magic, notifications have appeared as expected for the past couple days. So, 🤷‍♂️.

Weirdness persists; I now seem to have fallen prey to #155.

Using the technique I described above causes notifications to resume … until the next reboot.