Hi all，I have documented a defensive workaround that has so far prevented premature eventDidReachThreshold callbacks from producing premature notifications on physical devices running iOS 26.x: https://developer.apple.com/forums/thread/840907 The callback is treated only as a wake-up signal. Local timing state determines whether completion is actually due; early callbacks are rejected and the event is re-registered for only the locally remaining duration using a new generation identifier. This does not fix the underlying DeviceActivity issue, and the post includes its limitations. Additional testing and confirmation from Apple would be appreciated.