Yea, I agree. That is a good theory. At the moment, I really don't want to erase all my content, but there's a chance it will have to come down to that.

Even resetting all content did not fix this issue 🤷

Thank you! Tested and this works :) I'll make sure that users see directions that this needs to be turned on.

@cinnamontoast thank you so much for this! I've been staring at the API's for months and I had no idea "Displaying Activity Labels" exists

+1 to bring this to Mac too! :)

Feedback: FB11868772

I filed this feedback with steps : FB19807175 I don't think I could even select AlarmKit in the Feedback frameworks? Or the correct iOS build (I am on Beta 7).

Update: seems ok on the third night so hopefully just me 🤞 I did change the "device state" (ex. blocking different apps + different number of them), and performed various steps like restarting the device. The most important is that no one else is getting this particular problem.

basically what you said haha: "under the impression that my device is cursed when it comes to screen time" I'm mainly talking about whether this specific issue (aside from the other eventDidReachThreshold bugs) is something that is a legitimate new iOS 26.2 RC problem that's wide-spread, or if it happens that it was caused due to some non-realistic combination of factors because I am also testing things on my device.

There are, as you said, other bugs that exist. I was just afraid of whether there could be something especially wrong with 26.2 RC.

@Quappi Thank you for testing 🙏 that's the most important: that there isn't some wide-spread obvious new issue. I haven't seen the problem again since I reported it too. What set the alarm bells is that it happened two nights in a row (with the same behavior confirmed by debug logs) + that it was the RC.