DisconnectReasons
Note: As of July 10, 2024, watch faces must use the Watch Face Format in order to be installed on new watches that launch with Wear OS 5 pre-installed. Learn more about the user-facing changes in this Help Center article.
Additionally, starting in early 2025 (specific date to be announced during Q4 2024), all new watch faces published on Google Play must use the Watch Face Format.
object DisconnectReasons
Disconnect reasons for InteractiveWatchFaceClient.ClientDisconnectListener.onClientDisconnected.
Summary
Constants |
|
|---|---|
const Int |
ENGINE_DETACHED = 2Wallpaper service detached from the engine, which is now defunct. |
const Int |
ENGINE_DIED = 1The underlying engine died, probably because the watch face was killed or crashed. |
Constants
ENGINE_DETACHED
const val ENGINE_DETACHED = 2: Int
Wallpaper service detached from the engine, which is now defunct. The watch face itself has no control over this. Usually in response a new InteractiveWatchFaceClient should be created (see WatchFaceControlClient.getOrCreateInteractiveWatchFaceClient).
ENGINE_DIED
const val ENGINE_DIED = 1: Int
The underlying engine died, probably because the watch face was killed or crashed. Sometimes this is due to memory pressure and it's not the watch face's fault. Usually in response a new InteractiveWatchFaceClient should be created (see WatchFaceControlClient.getOrCreateInteractiveWatchFaceClient), however if this new client also disconnects due to ENGINE_DIED within a few seconds the watchface is probably bad and it's recommended to switch to a safe system default watch face.