RegistrationState.Unavailable reported but Wearables.startRegistration succeeds

[bddckr]

Summary

RegistrationState.Unavailable is emitted by Wearables.registrationState, but calling Wearables.startRegistration() from that state transitions through Registering → Registered successfully. We'd expect Unavailable to mean registration cannot proceed.

Steps to reproduce

1. Observe RegistrationState.Unavailable emitted from Wearables.registrationState
2. Call Wearables.startRegistration() anyway
3. State transitions: Unavailable → Registering → Registered

Expected behavior

If the SDK reports Unavailable, either startRegistration() should fail or the SDK should not report Unavailable in the first place.

Actual behavior

Registration succeeds despite the Unavailable state, suggesting the state is inaccurate.

Impact

We use RegistrationState to decide whether to prompt the user to register. When Unavailable is reported, we skip the registration prompt — which means users get stuck waiting even though registration would work fine.

Environment

• MWDAT version: 0.5.0 (mwdat-core)