RSH8j:
If during library initialisation the LocalDevice id or deviceSecret attributes are not able to be loaded then those LocalDevice details must be discarded and the ActivationStateMachine machine should transition to the NotActivated state. New LocalDevice id and deviceSecret attributes should be generated on the next activation event.
Found out about this whilst investigating a situation that caused deviceSecret to fail to load. It's important, because when we regenerate the id in this situation, we might end up with an id that doesn't match the currently-stored deviceIdentityToken, and we hence need to validate the latter (RSH3a2a).
Update, 15 May 2026: ably/specification#474 replaces this spec point with RSH3h and RSH8a1 — the current issue should implement those spec points instead.
┆Issue is synchronized with this Jira Bug by Unito
RSH8j:
Found out about this whilst investigating a situation that caused
deviceSecretto fail to load. It's important, because when we regenerate theidin this situation, we might end up with anidthat doesn't match the currently-storeddeviceIdentityToken, and we hence need to validate the latter (RSH3a2a).Update, 15 May 2026: ably/specification#474 replaces this spec point with RSH3h and RSH8a1 — the current issue should implement those spec points instead.
┆Issue is synchronized with this Jira Bug by Unito