Skip to content

Conversation

@maratal
Copy link
Collaborator

@maratal maratal commented Feb 4, 2024

Updated the spec so that it reflects the behaviour implemented in ably/ably-cocoa#1847, where a new device ID is generated as soon as the previous ones are cleared, so that id is never null.

Originally posted by @lawrence-forooghian here

Closes #180

**** @(RSH3g1a)@ Transitions to @WaitingForDeregistration@.
*** @(RSH3g2)@ On event @Deregistered@:
**** @(RSH3g2a)@ Clears all local @DeviceDetails@.
**** @(RSH3g2a)@ Generates a new pair of device @id@ and @deviceSecret@ as described in "RSH3a2b":#RSH3a2b. Clears all other local @DeviceDetails@.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This only partially describes the ably-cocoa behaviour, doesn't it? In ably-cocoa, id and deviceSecret generation are completely decoupled from the CalledActivate event, meaning that RSH3a2b and RSH8b would also need to be changed if we wished for the spec to describe the behaviour of ably-cocoa.

Also, same point as #182 (comment) re spec point modification.

@SimonWoolf
Copy link
Member

I'm not really familiar with the context here or the push activation state machine implemented in sdks, so going to untag myself and suggest @owenpearson instead

@SimonWoolf SimonWoolf requested review from owenpearson and removed request for SimonWoolf February 12, 2024 20:35
…y/ably-cocoa#1847, where a new device ID is generated as soon as the previous ones are cleared, so that id is never null.
@lawrence-forooghian
Copy link
Collaborator

@maratal are you intending to update this one?

@maratal
Copy link
Collaborator Author

maratal commented Apr 9, 2025

@maratal are you intending to update this one?

Will take a closer look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

DeviceDetails.id (PCD2) should be nullable.

4 participants