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

0.4.4

• Fix possible crash in handleAsyncData method – #62

0.4.3

• Remove Starscream code that automatically set Origin header

0.4.2

• Embed Starscream 3 – see discussion and pr #53.
• Support CentrifugeClientInfo in history publications.

0.4.1

• Use Client's sync queue for Subscription operations (previously each Subscription had its own sync queue). Fixes #24
• Fix already subscribed errors (code 105) on resubscribe after Subscription removing. Fixes #49

0.4.0

Update to work with Centrifuge >= v0.18.0 and Centrifugo v3.

Breaking change in server behavior. Client History API behavior changed in Centrifuge >= v0.18.0 and Centrifugo >= v3.0.0. When using history call it won't return all publications in a stream by default. See Centrifuge v0.18.0 release notes or Centrifugo v3 migration guide for more information and workaround on server-side.

• Protocol definitions updated to the latest version
• History method now accepts optional limit, since and reverse arguments and returns CentrifugeHistoryResult
• presence now returns CentrifugePresenceResult
• presenceStats now returns CentrifugePresenceStatsResult
• Publish now returns CentrifugePublishResult
• When working with Centrifugo v3 or Centrifuge >= v0.18.0 it's now possible to avoid using ?format=protobuf in connection URL. Client will negotiate Protobuf protocol with a server using WebSocket subprotocol mechanism (in request headers).