Hello Apple Engineering Team,
I am investigating a specific Apple Watch connectivity behavior.
Devices:
- Apple Watch Series 7, watchOS 26.6 (release)
- Paired iPhone 17 Pro Max, iOS 27 beta 2
Observed behavior: the Apple Watch vibrated continuously for approximately 5–6 seconds. When the wrist was raised, a red "iPhone Disconnected" screen was visible.
However, a subsequent iPhone sysdiagnose contained NRBTPipe[Disconnected 158825.34s], suggesting that the associated communication pipe had already been disconnected for roughly 44 hours before the sysdiagnose was captured — i.e., well before the observed alert.
I would appreciate clarification on the following technical questions:
- What exactly triggers the red "iPhone Disconnected" screen on Apple Watch? Is it triggered immediately when Bluetooth connectivity is lost, or can it appear later?
- Does this screen automatically generate a haptic notification? Under what conditions could the user experience several seconds of repeated vibration?
- Does the alert depend only on the local Bluetooth connection, or does it also account for Wi-Fi/cloud connectivity? Could the local connection remain disconnected while the red screen appears substantially later?
- What does the internal
NRBTPipe[Disconnected ...]duration represent? Does it correspond directly to the connectivity state used by the Watch UI? - Is there any way to recover a historical watchOS sysdiagnose that may have been triggered using the Digital Crown and side button without a logging profile installed beforehand, particularly when the Watch and iPhone were not locally connected?
I understand that some implementation details may be private. Even confirmation of the expected UI timing and haptic behavior would be extremely helpful. If Feedback Assistant is the preferred route, I am happy to file a report with logs attached.
Thank you.