0.6.1

What's Changed

• Make info field of CentrifugePublicationEvent and CentrifugeServerPublicationEvent public by @YoavGro in #91

New Contributors

• @YoavGro made their first contribution in #91

Full Changelog: 0.6.0...0.6.1

0.6.0

What's Changed

Breaking change! This release changes the semantics of working with connection tokens described in Centrifugo v5 release post.

Previously, returning an empty token string from CentrifugeConnectionTokenGetter callback resulted in client disconnection with unauthorized reason.

Now returning an empty string from CentrifugeConnectionTokenGetter is a valid scenario which won't result into disconnect on the client side. It's still possible to disconnect client by returning a special CentrifugeError.unauthorized from CentrifugeConnectionTokenGetter.

And we are putting back SetToken method to the SDK – so it's now possible to reset the token to be empty upon user logout.

Full Changelog: 0.5.5...0.6.0

0.5.5

What's Changed

• Improve logger API: replace String with StaticString by @antonselyanin in #74

Full Changelog: 0.5.4...0.5.5

0.5.4

What's Changed

• Add centrifuge logger interface by @antonselyanin in #73
• Example app: replace CocoaPods with SPM by @antonselyanin in #72

Full Changelog: 0.5.3...0.5.4

0.5.3

• Fix: unset refreshRequired flag after getting connection token commit

0.5.2

• Fix connect when initial connection token not set but tokenGetter provided #71

v0.5.1

• Fix crashes caused by non-synchronized memory access upon getting no ping disconnect
• Fix issuing duplicate connecting state change events

v0.5.0 - new SDK API

Breaking changes

This release adopts a new iteration of Centrifugal protocol and a new iteration of API. Client now behaves according to the client SDK API specification. The work has been done according to Centrifugo v4 roadmap.

Check out Centrifugo v4 release post that covers the reasoning behind changes here.

New release only works with Centrifugo >= v4.0.0 and Centrifuge >= 0.25.0. See Centrifugo v4 migration guide for details about the changes in the ecosystem.

Note, that Centrifugo v4 supports clients working over the previous protocol iteration, so you can update Centrifugo to v4 without any changes on the client side (but you need to turn on use_client_protocol_v1_by_default option in the configuration of Centrifugo, see Centrifugo v4 migration guide for details).

Several important changes:

• new API according to the new SDK API specification
• all core features of Centrifugal client protocol are now supported
• delegateQueue to which Client submitted events is removed, it's now up to developer to utilize queues for processing callbacks
• SDK now uses Swift 5.0

0.4.6

• Added data filed to CentrifugeConnectEvent #67

0.4.5

• Fix crash accessing serverSubs from non-syncQueue #65