I’m developing a watchOS gentle-wake alarm using WKExtendedRuntimeSession and repeating haptics.
When the app determines it is time to wake the user, I want the watch to present the app’s custom wake screen immediately. That screen includes a Stop control. The goal is for the custom screen to be the alarm experience, rather than requiring the user to tap Open on the system’s Open/Stop alert or having that system alert replace the custom screen.
In hardware tests of my watchOS app (version 0.1, build 10) on November 9, 2026, I observed the system’s Open/Stop alert during the alarm. After selecting Open, the custom UI appeared, but the system alert returned after the app subsequently became inactive while the alarm session was still running.
Test environment
Apple Watch Series 11, watchOS 27.2 (24S118)
Xcode 27.2 (27B52), watchOS 27.2 SDK
Watch unlocked, Always On enabled, no attached debugger
The app schedules the session with start(at:), calls notifyUser(hapticType:repeatHandler:) once, and presents a SwiftUI fullScreenCover with the wake interface and Stop button. Stop invalidates the session.
In the 15-second Wake Duration test, logs showed reduced luminance after 15 seconds and inactivity about one second later. I observed the Open/Stop alert return twice after selecting Open. In the 70-second test, reduced luminance occurred 70 seconds after activation, followed by inactivity. Neither test logged a duplicate notifyUser call, process restart, or disappearance of the custom view before session termination. The logs establish lifecycle timing, but do not directly record system-alert presentation.
Questions
Is there a supported watchOS API or alarm architecture that can present a third-party app’s custom wake screen immediately when its alarm starts, without first showing or subsequently replacing it with the system Open/Stop alert?
If so, what lifecycle, presentation, and background-haptic requirements apply, including when the app is inactive or the watch is in Always On mode?
If this isn’t supported, is the system alert mandatory for WKExtendedRuntimeSession alarms, and what is the recommended alternative? Would AlarmKit with an iPhone companion change what can be presented on the watch?
The custom screen would provide a clear way to stop the alarm. I’m not asking to remove the user’s ability to stop it or to keep the display at full brightness indefinitely.
I also prepared a focused Watch-only sample isolating the runtime session, repeating haptics, custom presentation, and lifecycle logging. It builds successfully but has not been tested on hardware. The observations above are from the app, not the sample.