Hello Niko,
Just a heads up: on latest macOS Beta from today (26.4 Beta 1), your app constantly ask to quit. I have tried to delete the app and reinstall as stated, but it is not working.
As usual, I know i’m on a beta and I don’t expect this to be top priority, just a heads up if you have a solution and/or a fix possible.
Hi Mathieu,
Thank you so much for the heads up!
I tried to reproduce it using a virtual machine running macOS 26.4 beta, but Apple doesn’t really allow App Store accounts on virtual machines.
I will install a proper macOS 26.4 beta soon and fix the issue before the final release.
Hello Niko, thanks for the reply. It is still happening as of today (beta 3). Can you share a temporary fix for this, maybe checking for the valid subscription less frequently or anything else that can at least prevent the app from quitting randomly?
I just installed macOS 26.4 beta 3 (25E5223i) on an external drive.
Then installed Timeframe from the App Store.
At first I had problems with the App Store receipt too, but I was able to launch Timeframe in “free” mode.
After I clicked “Restore Purchases” in Timeframe’s store and relaunched the app, everything was back to normal.
Can you try to “Restore Purchases” and see if it works?
Hello Niko, I did not detail all the troubleshooting steps I took before opening the ticket, I apologize for that!
I actually did the restore purchases on all three beta, I’ve also uninstalled and reinstalled the app and I did a full logout of the icloud account and log back in (after a full os reboot). It never worked. Sometimes it takes more time before giving the warning and/or force close itself, in which case I just see the menu bar item gone… Before replying here I went ahead and tried again just in case something is now fixed and I will report back if it changed and never close again.
Thanks for the reply
Unfortunately, after about 45 minutes of it running, it pops up again and needs to close.
Thanks for the in-depth testing, Mathieu"!
I will check this more thoroughly and let you know when I find the cause of this bug.
Hello Niko,
As this is still happening in the release candidate, I hope this will not affect too many of your users when launching in the coming days. Have you made progress on this? Can I provide you with anything to help you fix this?
Thank you
