Websockets in swift for iOS and OSX

Last update: Jun 23, 2022

starscream

Starscream is a conforming WebSocket (RFC 6455) library in Swift.

Features

  • Conforms to all of the base Autobahn test suite.
  • Nonblocking. Everything happens in the background, thanks to GCD.
  • TLS/WSS support.
  • Compression Extensions support (RFC 7692)

Import the framework

First thing is to import the framework. See the Installation instructions on how to add the framework to your project.

import Starscream

Connect to the WebSocket Server

Once imported, you can open a connection to your WebSocket server. Note that socket is probably best as a property, so it doesn't get deallocated right after being setup.

var request = URLRequest(url: URL(string: "http://localhost:8080")!)
request.timeoutInterval = 5
socket = WebSocket(request: request)
socket.delegate = self
socket.connect()

After you are connected, there is either a delegate or closure you can use for process WebSocket events.

Receiving data from a WebSocket

didReceive receives all the WebSocket events in a single easy to handle enum.

func didReceive(event: WebSocketEvent, client: WebSocket) {
	switch event {
	case .connected(let headers):
		isConnected = true
		print("websocket is connected: \(headers)")
	case .disconnected(let reason, let code):
		isConnected = false
		print("websocket is disconnected: \(reason) with code: \(code)")
	case .text(let string):
		print("Received text: \(string)")
	case .binary(let data):
		print("Received data: \(data.count)")
	case .ping(_):
		break
	case .pong(_):
		break
	case .viabilityChanged(_):
		break
	case .reconnectSuggested(_):
		break
	case .cancelled:
		isConnected = false
	case .error(let error):
		isConnected = false
		handleError(error)
	}
}

The closure of this would be:

socket.onEvent = { event in
	switch event {
		// handle events just like above...
	}
}

Writing to a WebSocket

write a binary frame

The writeData method gives you a simple way to send Data (binary) data to the server.

socket.write(data: data) //write some Data over the socket!

write a string frame

The writeString method is the same as writeData, but sends text/string.

socket.write(string: "Hi Server!") //example on how to write text over the socket!

write a ping frame

The writePing method is the same as write, but sends a ping control frame.

socket.write(ping: Data()) //example on how to write a ping control frame over the socket!

write a pong frame

the writePong method is the same as writePing, but sends a pong control frame.

socket.write(pong: Data()) //example on how to write a pong control frame over the socket!

Starscream will automatically respond to incoming ping control frames so you do not need to manually send pongs.

However if for some reason you need to control this process you can turn off the automatic ping response by disabling respondToPingWithPong.

socket.respondToPingWithPong = false //Do not automaticaly respond to incoming pings with pongs.

In most cases you will not need to do this.

disconnect

The disconnect method does what you would expect and closes the socket.

socket.disconnect()

The disconnect method can also send a custom close code if desired.

socket.disconnect(closeCode: CloseCode.normal.rawValue)

Custom Headers, Protocols and Timeout

You can override the default websocket headers, add your own custom ones and set a timeout:

var request = URLRequest(url: URL(string: "ws://localhost:8080/")!)
request.timeoutInterval = 5 // Sets the timeout for the connection
request.setValue("someother protocols", forHTTPHeaderField: "Sec-WebSocket-Protocol")
request.setValue("14", forHTTPHeaderField: "Sec-WebSocket-Version")
request.setValue("chat,superchat", forHTTPHeaderField: "Sec-WebSocket-Protocol")
request.setValue("Everything is Awesome!", forHTTPHeaderField: "My-Awesome-Header")
let socket = WebSocket(request: request)

SSL Pinning

SSL Pinning is also supported in Starscream.

Allow Self-signed certificates:

var request = URLRequest(url: URL(string: "ws://localhost:8080/")!)
let pinner = FoundationSecurity(allowSelfSigned: true) // don't validate SSL certificates
let socket = WebSocket(request: request, certPinner: pinner)

TODO: Update docs on how to load certificates and public keys into an app bundle, use the builtin pinner and TrustKit.

Compression Extensions

Compression Extensions (RFC 7692) is supported in Starscream. Compression is enabled by default, however compression will only be used if it is supported by the server as well. You may enable compression by adding a compressionHandler:

var request = URLRequest(url: URL(string: "ws://localhost:8080/")!)
let compression = WSCompression()
let socket = WebSocket(request: request, compressionHandler: compression)

Compression should be disabled if your application is transmitting already-compressed, random, or other uncompressable data.

Custom Queue

A custom queue can be specified when delegate methods are called. By default DispatchQueue.main is used, thus making all delegate methods calls run on the main thread. It is important to note that all WebSocket processing is done on a background thread, only the delegate method calls are changed when modifying the queue. The actual processing is always on a background thread and will not pause your app.

socket = WebSocket(url: URL(string: "ws://localhost:8080/")!, protocols: ["chat","superchat"])
//create a custom queue
socket.callbackQueue = DispatchQueue(label: "com.vluxe.starscream.myapp")

Example Project

Check out the SimpleTest project in the examples directory to see how to setup a simple connection to a WebSocket server.

Requirements

Starscream works with iOS 8/10.10 or above for CocoaPods/framework support. To use Starscream with a project targeting iOS 7, you must include all Swift files directly in your project.

Installation

CocoaPods

Check out Get Started tab on cocoapods.org.

To use Starscream in your project add the following 'Podfile' to your project

source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '9.0'
use_frameworks!

pod 'Starscream', '~> 4.0.0'

Then run:

pod install

Carthage

Check out the Carthage docs on how to add a install. The Starscream framework is already setup with shared schemes.

Carthage Install

You can install Carthage with Homebrew using the following command:

$ brew update
$ brew install carthage

To integrate Starscream into your Xcode project using Carthage, specify it in your Cartfile:

github "daltoniam/Starscream" >= 4.0.0

Accio

Check out the Accio docs on how to add a install.

Add the following to your Package.swift:

.package(url: "https://github.com/daltoniam/Starscream.git", .upToNextMajor(from: "4.0.0")),

Next, add Starscream to your App targets dependencies like so:

.target(
    name: "App",
    dependencies: [
        "Starscream",
    ]
),

Then run accio update.

Rogue

First see the installation docs for how to install Rogue.

To install Starscream run the command below in the directory you created the rogue file.

rogue add https://github.com/daltoniam/Starscream

Next open the libs folder and add the Starscream.xcodeproj to your Xcode project. Once that is complete, in your "Build Phases" add the Starscream.framework to your "Link Binary with Libraries" phase. Make sure to add the libs folder to your .gitignore file.

Swift Package Manager

The Swift Package Manager is a tool for automating the distribution of Swift code and is integrated into the swift compiler.

Once you have your Swift package set up, adding Starscream as a dependency is as easy as adding it to the dependencies value of your Package.swift.

dependencies: [
    .Package(url: "https://github.com/daltoniam/Starscream.git", majorVersion: 4)
]

Other

Simply grab the framework (either via git submodule or another package manager).

Add the Starscream.xcodeproj to your Xcode project. Once that is complete, in your "Build Phases" add the Starscream.framework to your "Link Binary with Libraries" phase.

Add Copy Frameworks Phase

If you are running this in an OSX app or on a physical iOS device you will need to make sure you add the Starscream.framework to be included in your app bundle. To do this, in Xcode, navigate to the target configuration window by clicking on the blue project icon, and selecting the application target under the "Targets" heading in the sidebar. In the tab bar at the top of that window, open the "Build Phases" panel. Expand the "Link Binary with Libraries" group, and add Starscream.framework. Click on the + button at the top left of the panel and select "New Copy Files Phase". Rename this new phase to "Copy Frameworks", set the "Destination" to "Frameworks", and add Starscream.framework respectively.

TODOs

  • Proxy support

License

Starscream is licensed under the Apache v2 License.

Contact

Dalton Cherry

Austin Cherry

GitHub

https://github.com/daltoniam/Starscream
Comments
  • 1. Move CommonCrypto and zlib dependencies mapping to custom module map

    Hi! I faced an issue similar to this and this this. In my project I use Carthage and commit my artefacts into my repo. And CI(and any other machine) is not able to compile it without running 'carthage update'. Basically the problem that to link Starscream.framework with other app or library you should provide module.map similar to the one, located in /zlib folder (but without header, which is required only for build). To make this work I created new custom module map and added a wrapper for SHA1 algorithm used by Starscream. Also updated cocoapods spec to add custom module map + private headers.

    Please consider this PR as a possible way of resolving issues linked above and also I'd be happy to hear from you any suggestions on this.

    Thank you! Cheers!

    Reviewed by turbulem at 2018-06-14 18:22
  • 2. Proxy connect

    This pull request added proxy support. The proxy info is from the system configuration. PAC is supported.

    Proxy protocol supported include HTTPS (via CONNECT method) and SOCKS

    Reviewed by oldshuren at 2016-06-04 07:11
  • 3. Fixed "invalid HTTP upgrade" issue

    I was getting occasional errors from my app stating "invalid HTTP upgrade". It sounds like a few other users of the library were also seeing this issue. I tracked down the problem: there were some extra garbage bytes at the beginning of the HTTP response from the server. These garbage bytes come out of NSStream, and are identified as a leading fragment for the response packet. The extra bytes didn't show up when I was inspecting the packets using Wireshark.

    To fix the issue, I added some code in processHTTP to look for the start of the response, and ignore any bytes before the response.

    I should also note that I was having trouble with running the tests, as stated in issue #297. Let me know if there's any test failures.

    @daltoniam Please review.

    Reviewed by psahgal at 2017-01-04 15:15
  • 4. Crashes in 1.1.1

    In the latest version I've noticed some crashes after the delegate is released. It doesn't happen all the time, but it happens pretty often. Not sure if I'm doing something crazy.

    Test project: https://github.com/nuclearace/WebSocketCrash

    Reviewed by nuclearace at 2016-01-20 18:07
  • 5. Error: Invalid HTTP upgrade

    Hi,

    I have random connection problem which display these logs:

    websocket is connected
    websocket is disconnected: "Invalid HTTP upgrade"
    

    code:

        let useSSL = true
        let websocketScheme = "wss"
        let host = "x.x.x.x"
        let port: NSNumber = 8080
    
        public init() {
            let components = NSURLComponents()
            components.scheme = websocketScheme
            components.host = host
            components.port = port
            components.path = "/"
    
            webSocket = WebSocket(url: components.URL!)
            webSocket?.selfSignedSSL = useSSL
            webSocket?.delegate = self
            webSocket?.connect()
        }
    

    It happens on iOS 9.0.1 (iPads). With swift 1.x and Xcode 6.x everything worked well, but now it randomly failed. Please give me some suggestion. Thank you.

    Reviewed by wakinchan at 2015-09-28 10:35
  • 6. Using with System Proxy on Simulator

    It seems that when using this framework on a simulator (I've been using it for a while now, but never on the simulator), the connection request ignores the system proxy. Other network requests (e.g. REST API calls using Alamofire) are handled appropriately and routed through the proxy. IS there a way to set the proxy for this framework or have others experienced this issue?

    Reviewed by kevinmlong at 2016-08-25 02:11
  • 7. Bug: UInt64 maybe negativ

    Hi.

    Very often get a runtime error on the latest version.

    This is around the 500. row: var len = dataLength if dataLength > UInt64(bufferLen) { len = UInt64(bufferLen-offset) // runtime error position }

    the bufferLen value is 8, and the offset value is 10. I dont know how it happens but it will be negativ.. Unfortunately I didnt implement the server so I cannot check it. maybe it would be a good way to handle this case in this library.

    Reviewed by szuniverse at 2015-04-21 16:57
  • 8. Crash NSStream

    Error if i uses this class

    Log: 2014-08-13 22:02:46.079 WebSocket[2937:1803] +[NSStream getStreamsToHostWithName:port:inputStream:outputStream:]: unrecognized selector sent to class 0x3853e86c 2014-08-13 22:02:46.083 WebSocket[2937:1803] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '+[NSStream getStreamsToHostWithName:port:inputStream:outputStream:]: unrecognized selector sent to class 0x3853e86c'

    Reviewed by seropunov at 2014-08-13 19:09
  • 9. Added callbacks for pings and pongs

    I took the changes from #268 and reimplemented them in Swift 3. These changes add callbacks and a delegate for apps to listen for when a ping has been sent, a ping has been received, and a pong has been sent.

    I should also note that I was having trouble with running the tests, as stated in issue #297. Let me know if there's any test failures.

    @daltoniam Please review.

    Reviewed by psahgal at 2017-01-03 22:38
  • 10. When connecting to a wss:// socket, getting an SSL handshake error

    The same host with a different WebSock Swift framework (https://github.com/tidwall/SwiftWebSocket) connects just fine. Am I missing some extra configuration?

    Error printout:

    [BoringSSL] boringssl_context_handle_fatal_alert(1872) [C1.1:1][0x7fcec6701630] write alert, level: fatal, description: certificate unknown
    [BoringSSL] boringssl_context_error_print(1862) boringssl ctx 0x6000000d40a0: 140526066114904:error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED:/BuildRoot/Library/Caches/com.apple.xbs/Sources/boringssl_Sim/boringssl-283.60.3/ssl/handshake.cc:369:
    [BoringSSL] boringssl_session_handshake_error_print(111) [C1.1:1][0x7fcec6701630] 140526066114904:error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED:/BuildRoot/Library/Caches/com.apple.xbs/Sources/boringssl_Sim/boringssl-283.60.3/ssl/handshake.cc:369:
    [BoringSSL] nw_protocol_boringssl_handshake_negotiate_proceed(726) [C1.1:1][0x7fcec6701630] handshake failed at state 12288
    error: Optional(-9858: Optional(handshake failed))
    

    Code that triggers the SSL handshake error:

    websock = WebSocket(request: URLRequest(url: URL(string: "wss://myhost:9110/")!))
    websock.delegate = self
    websock.connect()
    
        func didReceive(event: WebSocketEvent, client: WebSocket) {
            switch event {
            case .connected(let headers):
                print("websocket is connected: \(headers)")
            case .disconnected(let reason, let code):
                print("websocket is disconnected: \(reason) with code: \(code)")
            case .text(let string):
                print("Received text: \(string)")
            case .binary(let data):
                print("Received data: \(data.count)")
            case .ping(_):
                break
            case .pong(_):
                break
            case .viablityChanged(_):
                break
            case .reconnectSuggested(_):
                break
            case .cancelled:
                print("cancelled")
            case .error(let error):
                print("error: \(String(describing: error))")
            }
        }
    
    Reviewed by yuriymacdev at 2020-01-21 01:13
  • 11. Support websocket compression

    Fixes #169.

    Using the Autobahn test suite, I confirmed that these changes perform comparably with the Autobahn library itself. See attached report:

    autobahn_test.html.zip

    Reviewed by joejune at 2017-05-25 00:26
  • 12. If WSEngine canSend is false, write fails silently and doesn't call continuation

    Describe the bug

    If you are doing a async call on a socket and expecting a completion call, and the socket can't send, the write method of WSEngine fails silently so that the completion is never called and async leaks occur because resume is not called.

    Steps to Reproduce

    Consider this code snippet:

        func sendHeartbeat() async throws {
            guard let socket = socket else { throw WebSocketError.notConnected }
            await withCheckedContinuation({ continuation in
                socket.write(string: heartbeatMessage, completion: {
                    continuation.resume()
                })
            })
        }
    
    

    If socket.write fails because of this piece of WSEngine:

        public func write(data: Data, opcode: FrameOpCode, completion: (() -> ())?) {
            writeQueue.async { [weak self] in
                guard let s = self else { return }
                s.mutex.wait()
                let canWrite = s.canSend
                s.mutex.signal()
                if !canWrite {
                    return
                }
    

    Then the completion is never called and so the continuation.resume will not be called either.

    Expected behavior

    I would expect either write to throw an error or to return an error in the completion call.

    Environment:

    • OS/Version: iOS 15.5
    • Starscream Version: 4.0.4
    • Xcode version: 13.4

    Additional context

    Add any other context about the problem here.

    Reviewed by jamesturner-mark43 at 2022-05-26 18:03
  • 13. Release

    What do you want to happen?

    Any chance you could cut a release? There have been a number of PRs merged to main that would be nice to make available via CocoaPods. In particular, the recently merged PR to change the deprecated use of the class keyword to define a class-constrained protocols to AnyObject would clean up a lot of warnings in everyone's builds.

    Thanks!

    Reviewed by ameter at 2022-05-10 14:51
  • 14. Update README.md

    Modify the version reference to prevent user copy errors

    Issue Link 🔗

    Please attach the link to an issue if it exists.

    Goals ⚽

    What you hope to address within this PR.

    Implementation Details 🚧

    Additional details about the PR.

    Reviewed by HuginChen at 2022-05-10 03:34
  • 15. "Invalid HTTP upgrade", code: 404)) for 3.0.6 version of Starscream

    Describe the bug

    We have deployed an Application Load Balancer (ALB) for our spingboot application which consists of both Rest and Websocket services hosted in EKS cluster. We added health check, ssl redirect etc. annotations in the ingress.yaml file. The listener is HTTPS: 443 and the SSL certificate is from ACM and TLS termination is happening at the ingress.

    When we hit the ALB endpoint, rest service is working fine but receiving the following error with the websocket service.

    Websocket Optional(wss://xxx.xx.xx.com:443/xx/xx/xx/xx) disconnected with error Optional(Starscream.WSError(type: Starscream.ErrorType.upgradeError, message: "Invalid HTTP upgrade", code: 404))

    The same is working fine with the Network Load balancers in AWS.

    app.kubernetes.io/instance: aws-load-balancer-controller app.kubernetes.io/name: aws-load-balancer-controller app.kubernetes.io/version: v2.3.0 helm.sh/chart: aws-load-balancer-controller-1.3.2 Kubernetes version: 1.19 Platform version: eks.7

    Environment:

    • Starscream Version: 3.0.6
    • Xcode version: 13.2.1

    Any help in resolving this issue is highly appreciated. Thank you!

    Reviewed by rampn443 at 2022-05-02 03:50
  • 16. Bump cocoapods-downloader from 1.3.0 to 1.6.3

    Bumps cocoapods-downloader from 1.3.0 to 1.6.3.

    Release notes

    Sourced from cocoapods-downloader's releases.

    1.6.3

    Enhancements
    • None.
    Bug Fixes
    • None.

    1.6.2

    Enhancements
    • None.
    Bug Fixes
    • None.

    1.6.1

    Enhancements
    • None.
    Bug Fixes
    • None.

    1.6.0

    Enhancements
    • None.
    Bug Fixes
    • Adds a check for command injections in the input for hg and git.
      orta #124

    1.5.1

    Enhancements
    • None.
    Bug Fixes
    • Fix "can't modify frozen string" errors when pods are integrated using the branch option
      buju77 #10920

    1.5.0

    ... (truncated)

    Changelog

    Sourced from cocoapods-downloader's changelog.

    1.6.3 (2022-04-01)

    Enhancements
    • None.
    Bug Fixes
    • None.

    1.6.2 (2022-03-28)

    Enhancements
    • None.
    Bug Fixes
    • None.

    1.6.1 (2022-03-23)

    Enhancements
    • None.
    Bug Fixes
    • None.

    1.6.0 (2022-03-22)

    Enhancements
    • None.
    Bug Fixes
    • Adds a check for command injections in the input for hg and git.
      orta #124

    1.5.1 (2021-09-07)

    Enhancements
    • None.

    ... (truncated)

    Commits
    • c03e2ed Release 1.6.3
    • f75bccc Disable Bazaar tests due to macOS 12.3 not including python2
    • 52a0d54 Merge pull request #128 from CocoaPods/validate_before_dl
    • d27c983 Ensure that the git pre-processor doesn't accidentally bail also
    • 3adfe1f [CHANGELOG] Add empty Master section
    • 591167a Release 1.6.2
    • d2564c3 Merge pull request #127 from CocoaPods/validate_before_dl
    • 99fec61 Switches where we check for invalid input, to move it inside the download fun...
    • 96679f2 [CHANGELOG] Add empty Master section
    • 3a7c54b Release 1.6.1
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    Reviewed by dependabot[bot] at 2022-04-05 22:22
Reactive WebSockets

RxWebSocket Reactive extensions for websockets. A lightweight abstraction layer over Starscream to make it reactive. Installation RxWebSocket is avail

Mar 1, 2022
Socket.io iOS and OSX Client compatible with v1.0 and later
Socket.io iOS and OSX Client compatible with v1.0 and later

SocketIO-Kit ⚠️ This project is no longer maintained. Please use the official framework Socket.IO-Client-Swift. SocketIO-Kit is a Socket.io iOS client

Mar 9, 2022
Easy-to-use ICMP Ping for iOS (and maybe OSX)

CDZPinger Easy-to-use ICMP ping for iOS - just create a CDZPinger and you delegate gets a callback every second with the average ping time. Installati

Feb 2, 2022
Conforming WebSocket (RFC 6455) client library for iOS and Mac OSX
Conforming WebSocket (RFC 6455) client library for iOS and Mac OSX

SwiftWebSocket Conforming WebSocket (RFC 6455) client library for iOS and Mac OS

Dec 24, 2021
A lightweight, one line setup, iOS / OSX network debugging library! 🦊
A lightweight, one line setup, iOS / OSX network debugging library! 🦊

Netfox provides a quick look on all executed network requests performed by your iOS or OSX app. It grabs all requests - of course yours, requests from

Jun 18, 2022
WKZombie is an iOS/OSX web-browser without a graphical user interface.
WKZombie is an iOS/OSX web-browser without a graphical user interface.

WKZombie is a Swift framework for iOS/OSX to navigate within websites and collect data without the need of User Interface or API, also known as Headless browser. It can be used to run automated tests / snapshots and manipulate websites using Javascript.

Jun 16, 2022
Server-side Swift. The Perfect core toolset and framework for Swift Developers. (For mobile back-end development, website and API development, and more…)
Server-side Swift. The Perfect core toolset and framework for Swift Developers. (For mobile back-end development, website and API development, and more…)

Perfect: Server-Side Swift 简体中文 Perfect: Server-Side Swift Perfect is a complete and powerful toolbox, framework, and application server for Linux, iO

Jun 27, 2022
Mar 3, 2022
Socket framework for Swift using the Swift Package Manager. Works on iOS, macOS, and Linux.

BlueSocket Socket framework for Swift using the Swift Package Manager. Works on iOS, macOS, and Linux. Prerequisites Swift Swift Open Source swift-5.1

Jun 19, 2022
Jan 26, 2022
🌏 A zero-dependency networking solution for building modern and secure iOS, watchOS, macOS and tvOS applications.
🌏 A zero-dependency networking solution for building modern and secure iOS, watchOS, macOS and tvOS applications.

A zero-dependency networking solution for building modern and secure iOS, watchOS, macOS and tvOS applications. ?? TermiNetwork was tested in a produc

Jun 27, 2022
RestKit is a framework for consuming and modeling RESTful web resources on iOS and OS X

RestKit RestKit is a modern Objective-C framework for implementing RESTful web services clients on iOS and Mac OS X. It provides a powerful object map

Jun 13, 2022
Lightweight Networking and Parsing framework made for iOS, Mac, WatchOS and tvOS.
Lightweight Networking and Parsing framework made for iOS, Mac, WatchOS and tvOS.

NetworkKit A lightweight iOS, Mac and Watch OS framework that makes networking and parsing super simple. Uses the open-sourced JSONHelper with functio

May 24, 2022
Bonjour networking for discovery and connection between iOS, macOS and tvOS devices.
Bonjour networking for discovery and connection between iOS, macOS and tvOS devices.

Merhaba Bonjour networking for discovery and connection between iOS, macOS and tvOS devices. Features Creating Service Start & Stop Service Stop Brows

Jun 20, 2022
QwikHttp is a robust, yet lightweight and simple to use HTTP networking library for iOS, tvOS and watchOS

QwikHttp is a robust, yet lightweight and simple to use HTTP networking library. It allows you to customize every aspect of your http requests within a single line of code, using a Builder style syntax to keep your code super clean.

Mar 20, 2022
OAuth2 framework for macOS and iOS, written in Swift.
OAuth2 framework for macOS and iOS, written in Swift.

OAuth2 OAuth2 frameworks for macOS, iOS and tvOS written in Swift 5.0. ⤵️ Installation ?? Usage ?? Sample macOS app (with data loader examples) ?? Tec

Jun 21, 2022
SwiftSoup: Pure Swift HTML Parser, with best of DOM, CSS, and jquery (Supports Linux, iOS, Mac, tvOS, watchOS)
SwiftSoup: Pure Swift HTML Parser, with best of DOM, CSS, and jquery (Supports Linux, iOS, Mac, tvOS, watchOS)

SwiftSoup is a pure Swift library, cross-platform (macOS, iOS, tvOS, watchOS and Linux!), for working with real-world HTML. It provides a very conveni

Jun 27, 2022
MQTT for iOS and macOS written with Swift

CocoaMQTT MQTT v3.1.1 client library for iOS/macOS/tvOS written with Swift 5 Build Build with Xcode 11.1 / Swift 5.1 Installation CocoaPods Install us

Jun 15, 2022
Minimalistic Swift HTTP request agent for iOS and OS X

Agent Table of Contents Introduction Usage HTTP Verbs Overloading Method Chaining Response Closure Verbs Methods NSMutableURLRequest Contributing Lice

Apr 14, 2022