E24 Oh. I'm sorry. I completely forget one thing about changes made to Android 14. The advice in my last post probably won't help. I forget the exact details so I just searched around quickly to see what the change was. I didn't research this in depth, so something I say about this change might not be 100% correct, but the general idea is still the same.
In Android 14, apps are no longer automatically granted permission to schedule alarms at precise times. It's possible ClockYou is crashing because it doesn't check if it has the permission and is crashing because it just assumes the permission is automatically granted and doesn't know how to handle its request to be rejected.
I am not sure if this will help, but you can try granting an alarm permission, though I'm not sure if it's the same permission. Try making sure ClockYou is allowed here:
Settings > Apps > All apps > Special app access > Alarms & reminders > ClockYou
If you can change the above permission to enabled, try again to see if that resolves the issue.
I checked the app's GitHub, and found that the permission was added 6 months ago. Are you sure you have the latest version installed? It looks like they update frequently, so they might have made some other changes that make it cooperate with Android 14 better.
If the app is up to date and the permission I mentioned is set to enabled, then maybe you can reset the app by going to the app's settings and clear its storage (Settings > Apps > All apps > ClockYou > Storage and cache), then open the app again to see if you're prompted to allow it to schedule precise alarms.
If all of those fail, you can try the exploit protection compatibility mode. Enabling it for one app is probably not a big deal since the rest of the apps and OS are still protected/hardened.
And, finally, if everything fails, you might want to open an issue with them on their GitHub repository, which I think is this one.
Sorry for the super long post, but hopefully it helps!