The server caches your device list on the websocket, so sending on the websocket to a just-linked device will always fail. We could close/open the websocket, but that might be disruptive in it's own way. Instead we'll closely mirror the Android approach, where WebSocket sends are attempted only one time, and failure is handled by falling back to the original REST approach. So note: we don't do any special handling of failures on the websocket (409/410). We simply retry it with REST which will handle the 409/410/etc. Consequently, we don't want to decrement our retry count for websocket sends. |
||
|---|---|---|
| .. | ||
| Example | ||
| fastlane | ||
| protobuf | ||
| Resources/Certificates | ||
| src | ||
| tests | ||
| Utilities | ||
| .clang-format | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
SignalServiceKit
SignalServiceKit is an Objective-C library for communicating with the Signal messaging service for iOS & OS X
To use SignalServiceKit via Cocoapods add the following to your Podfile
pod 'SignalServiceKit', git: 'https://github.com/signalapp/Signal-iOS.git'