https://github.com/socketmobile/swift-package-capturesdk
CaptureSDK is the easiest solution for adding barcode scanning and RFID/NFC reading capability to an iOS application
https://github.com/socketmobile/swift-package-capturesdk
barcode bluetooth bluetooth-le bluetooth-low-energy camera-scanner camera-scanning capture capturesdk ios qrcode scanner swift
Last synced: 28 days ago
JSON representation
CaptureSDK is the easiest solution for adding barcode scanning and RFID/NFC reading capability to an iOS application
- Host: GitHub
- URL: https://github.com/socketmobile/swift-package-capturesdk
- Owner: SocketMobile
- License: other
- Created: 2022-03-02T10:16:32.000Z (about 4 years ago)
- Default Branch: master
- Last Pushed: 2025-02-21T15:42:33.000Z (about 1 year ago)
- Last Synced: 2025-02-21T16:36:44.560Z (about 1 year ago)
- Topics: barcode, bluetooth, bluetooth-le, bluetooth-low-energy, camera-scanner, camera-scanning, capture, capturesdk, ios, qrcode, scanner, swift
- Language: Objective-C
- Homepage:
- Size: 35.6 MB
- Stars: 10
- Watchers: 10
- Forks: 1
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
# CaptureSDK Version 2.0.63 - Swift Package Manager
Socket Mobile is a leading innovator of data capture and delivery solutions for enhanced productivity.
CaptureSDK is the easiest solution for adding barcode scanning and RFID/NFC reading capability to an iOS application.
The Socket Mobile barcode scanner and contactless reader/writer are an ergonomic, fast and accurate solution to a variety of data entry scenarios.
This SDK is very easy to integrate to an application without requirement to follow a specific design architecture.
Within 10 minutes the barcode scanning or RFID/NFC reading capability can be integrated into an application.
The CaptureSDK offers a built-in barcode scanner called SocketCam, allowing to test and integrate the SDK even before getting a Socket Mobile scanner, using the exact same API, which makes the transition from using SocketCam to a Socket scanner totally frictionless.
More documentation can be found [here in our CaptureSDK Documentation](https://docs.socketmobile.dev/capture/ios/en/latest/).
## From 8th of October 2025 - Noticeable change from version 2.0
**There are 2 choices to connect and use our Bluetooth LE readers:**
**- Install our [Socket Mobile Companion app](https://apps.apple.com/app/socket-mobile-companion/id1175638950) which takes care of the discovery and the selection of the reader to connect to.**
**- Write some code to fit the Bluetooth discovery flow to your application's design by creating an UI that starts and shows discovered devices and select them to be paired to your application.**
[See our Getting Started section in our documentation](https://docs.socketmobile.dev/capture/ios/en/latest/gettingStarted.html)
## Devices compatibility and CaptureSDK versions
| Devices | < 2.0 | 2.0 |
| :----------------------------------------------------: | :--------------------: | :--------------------: |
| **SocketCam C820, C860** | ✅ | ✅ |
| **S720/D720/S820** | ✅ | ✅ |
| **D600, S550, and all other barcode scanners** | ✅ | ✅ |
| **S370** | ✅ | ✅ |
| **M930** | ✅ | ✅ |
| **S320** | ✅ | ✅ |
| **S721** (new Bluetooth LE barcode scanner) | ❌ | ✅ |
## Table of Contents
* [Breaking changes V2.0](#breaking-changes)
* [Quick install notes](#quick-install-notes)
* [CaptureSDK usage](#capturesdk-usage)
* [Sample code](#sample-code)
* [SocketCam C820 & C860](#socketcam-c820-and-c860)
* [Configure and connect a Socket Mobile device](#configure-and-connect-a-socket-mobile-device)
* [Device Notifications (Battery Level)](#device-notifications-battery-level)
* [Closing CaptureSDK](#closing-capturesdk)
## Breaking changes
We have made a step forward and changed a few things to stay up to date with requirements. The SDK still works as you expect.
* CaptureSDK is built with Xcode 26
* The minimum target is now iOS 15.0
* The Bluetooth discovery flow is a bit different. The transition of our products from Bluetooth Classic to Bluetooth Low Energy forces to change the Developers and Users Experience slightly. You can use our CaptureSDK to connect devices either through our [Socket Mobile Companion app](https://apps.apple.com/app/socket-mobile-companion/id1175638950) which takes care of the discovery and the selection of the reader to connect to, or, you can write your own code, using the new CaptureSDK APIs, to make a UI for the discovery that fits your design and application's flow.
## Quick install notes
CaptureSDK is using [Swift Package Manager](https://www.swift.org/package-manager/).
First, you need to install Xcode.
To include the SDK in your Xcode project you have to add a `Package Dependency` in the project's settings section and in the tab "Package Dependencies".
Add the url of this repository: [https://github.com/SocketMobile/swift-package-capturesdk.git](https://github.com/SocketMobile/swift-package-capturesdk.git)
Once you have added the package, you should see `CaptureSDK` added to your Package Dependencies in Xcode's Project Navigator as follow:
**VERY IMPORTANT**: Supported external accessory protocols array in the application settings.
In order to be able to use the Socket Mobile barcode scanners, the scanners external accessory protocol string needs to be added in the application project info in the **supported external accessory protocols array**.
The protocol string is `com.socketmobile.chs`.
If the application does use a Socket Mobile barcode scanner it will need to be MFi whitelisted before submitting the application in the App Store. Socket Mobile will handle the whitelist (MFi) application process for you, when you submit your app for MFi in your Socket Mobile developer account. This has to be done once for the first version supporting the barcode scanner.
You also need to add the following key to your `Info.plist`: **CFBundleAllowMixedLocalizations** (*Localized resources can be mixed*) to **`YES`**. That allows or SDK to display localized strings.
An AppKey is required in order to use CaptureSDK.
The AppKey can be generated by logging in Socket Mobile developer portal and registering your application.
This registration needs the Socket Mobile developer ID, the application Bundle ID (which is case sensitive).
Now you're ready to add `import CaptureSDK` in your main controller, and make it derive from one of the `CaptureHelperDelegate` that your application needs.
Go to the `CaptureHelperDelegate` source and copy paste the delegates you want to override, at minimum the onDecodedData delegate in order to be able to receive the barcode decoded data in your application.
## CaptureSDK usage
`CaptureSDK` is described in greater details in the [documentation](https://docs.socketmobile.dev/capture/ios/en/latest/ "CaptureSDK Documentation").
The recommended way of using `CaptureSDK` is by using `CaptureHelper`. `CaptureHelper` is now included into the framework and not as a separate file: [CaptureHelper](https://docs.socketmobile.dev/capture/ios/en/latest/captureHelper.html)
### 1. Getting a `CaptureHelper` instance
`CaptureHelper` can be instantiated in one of your application controllers using its `CaptureHelper.sharedInstance` static member.
### 2. `CaptureHelper` delegates stack
The chosen controller must implement one of the `CaptureHelper[xxxxx]Delegate` protocols in order to receive the various `CaptureSDK` asynchronous events.
The reference of the controller deriving from at least one of the `CaptureHelper[xxxxx]Delegate` can be set by using the `CaptureHelper pushDelegate` method.
`CaptureHelper` maintains a delegates stack. The delegate on top of the stack is the one that receives the notification from `CaptureSDK`. So if the application has multiple views requiring the scanning feature, it can push a reference of a new view controller to the `CaptureHelper` delegates stack, and remove that reference when the view is no longer active.
### 3. Opening `CaptureHelper`
In order to start `CaptureSDK`, the API uses the `openWithAppInfo:withCompletionHandler` method with the application information.
This open method **can be called only once**, in the main view controller by example, and the `CaptureHelper.sharedInstance` can be used at various place in the application code as singleton reference without the need to pass it through various controllers.
The application information is retrieved from the Socket Mobile developer portal, by registering the application with its application ID, the developer ID. The application key is then generated and all three initialize the AppInfo required to open `CaptureSDK`.
The application ID is composed by the application bundle ID prefixed by the platform on which the application is designed to run.
Here is an example of such application ID: `"ios:com.socketmobile.SingleEntry"`. The application ID is **case sensitive**.
Once `CaptureSDK` is open, then the device arrival notification can occurs as soon as a scanner is connected to the iOS device.
The decoded data coming from the scanner can be retrieved by overriding the `onDecodedData` delegate.
**IMPORTANT**:
If a property is not accessible through the available `CaptureHelper` methods, it is very easy to add new ones, by creating a `CaptureHelper` **extension** class and copy and paste a similar get/set method and change the property settings inside the new method.
Creating a `CaptureHelper` extension allows to avoid an overwrite of a modified version of `CaptureHelper` when updating to a more recent `CaptureSDK` CocoaPods.
### 4. Sample code
Try out our sample [our Single Entry app on Github SocketMobile](https://github.com/SocketMobile/capturesingleentryswift-ios)
## SocketCam C820 and C860
We have included `SocketCam C820` & `SocketCam C860` into the SDK, formerly known as SoftScan.
For SocketCam C860 is an enhanced version of SocketCam C820, you also need to add the following key to your `Info.plist`: **LSApplicationQueriesSchemes** (*Queried URL Schemes*) with a new item: **sktcompanion** (in lower case).
In order to use it you have to install [Socket Mobile Companion](https://apps.apple.com/app/socket-mobile-companion/id1175638950) on your device.
You can find more details about SocketCam C860 [on our website](https://www.socketmobile.com/readers-accessories/data-readers/camera-based-socketcam).
`SocketCam` feature refers to the capability of using the phone's camera in order to scan a barcode. The main purpose of integrating this feature in `CaptureSDK` is to provide a consistent interface to barcode readers.
Whether it is a Socket Mobile scanner, or simply the phone's camera, the application relies on the same interface, same API, which makes the transition from using SocketCam to a physical Socket scanner totally frictionless.
The application using the `SocketCam` feature needs to do 2 things differently, which Socket Mobile scanners don't require.
The first thing is to provide a trigger logic that starts the `SocketCam` scanning operation. The trigger is a `CaptureSDK` property `kSktCapturePropIdTriggerDevice` that exists since the first version of `CaptureSDK`.
A third property `kSktCapturePropIdSocketCamStatus` allows to enable or disable the `SocketCam` feature. This is a `CaptureSDK` property that is persistent across the life cycle of the application using it.
If the `SocketCam` feature is enabled, `CaptureSDK` will send a device arrival notification to the application referencing a `SocketCam` device the application can control.
Once the application triggers a read, the decoded data arrives the same way with the same information than as any other Socket Mobile devices supported by `CaptureSDK`.
For more information please check the [documentation](https://docs.socketmobile.dev/capture/ios/en/latest/ "CaptureSDK Documentation").
With the new version of CaptureSDK available, you will be able to present SocketCam as you wish in a custom view, a popover and still in full screen. Now you decide where and when triggering and removing SocketCam view controller in your application's flow. And this is your responssability to handle the presentation and the dismissal of the view controller.
However, there's a minimal size of 250px x 250px to observe in order to display all SocketCam's UI elements.
BEFORE
AFTER
### Sample code
```swift
let scanner = CaptureHelperDevice()
scanner.setTrigger(.start, withCompletionHandler: { result, propertyObject in
DispatchQueue.main.async {
if let anObject = propertyObject?.object, let dic = anObject as? [String: Any], let objectType = dic["SKTObjectType"] as? String, objectType == "SKTSocketCamViewControllerType", let socketCamViewController = dic["SKTSocketCamViewController"] as? UIViewController {
////
// Present the socketCamViewController in a popover or a subview or in full screen
////
}
}
})
extension YourViewController: CaptureHelperDeviceDecodedDataDelegate {
// This delegate is called each time a decoded data is read from a scanner or SocketCam
func didReceiveDecodedData(_ decodedData: SKTCaptureDecodedData?, fromDevice device: CaptureHelperDevice, withResult result:SKTResult) {
print("--->>> didReceiveDecodedData for device: \(device.deviceInfo.deviceType)")
if result == .E_NOERROR {
let str = decodedData!.stringFromDecodedData()
print("Decoded Data \(String(describing: str))")
DispatchQueue.main.async {
////
// When receiving your decoded data you can dismiss, hide, remove the SocketCam custom view controller
////
}
}
}
}
```
Depending on how you want to display SocketCam in your application, it may require to show or hide the close button of the SocektCam view controller. Ideally, you can execute this at the device arrival of a SocketCam device, whether it is C820 or C860. In order to do so, add a specific configuration as follow:
```swift
let prop = SKTCaptureProperty()
prop.id = SKTCapturePropertyID.configuration
prop.type = .string
prop.stringValue = "SocketCamCloseButton=enabled" /// to show the close button
// OR
prop.stringValue = "SocketCamCloseButton=disabled" /// to hide the close button
self.captureHelper.setProperty(prop) { result, complete in
}
```
If you add the SocketCam view controller as a subview in another view controller (`myView.addsubview(self.socketCamViewController.view)`), then you need to remove the SocketCam view controller's view when you finish using it (`self.socketCamViewController.view.removeFromSuperview()`) otherwise it won't be displayed the next time you trigger SocketCam. So it's good to keep a reference on the SocketCam view controller when it is given by the CaptureHelper method `setTrigger`
## Configure and connect a Socket Mobile device
`CaptureSDK` is designed for using all of the Socket Mobile devices on the iOS platforms.
As the application developer, `CaptureSDK` will give you full programmatic access to a connected Socket Mobile data capture device to customize the data source (barcode symbology or RFID Tag), data support and manage device feedback
messages and functions.
The API documentation for `CaptureSDK` can be found [here](https://docs.socketmobile.dev/capture/ios/en/latest/ "Capture Documentation")
The Socket Mobile devices are shipped by default in **MFi mode** which is compatible with the `CaptureSDK`.
The device can be configured to the **Application mode** by using the [Socket
Mobile Companion app](https://itunes.apple.com/us/app/socket-mobile-companion/id1175638950?mt=8 "Socket Mobile Companion").
You can also refer to the [documentation](https://docs.socketmobile.dev/capture/ios/en/latest/ConfigureInAppMode.html "Configure and connect scanner") for instructions without using Companion.
**Bluetooth LE Devices**
For our Blueetooth LE devices (D600, S550, S370, S320 and S721), use the following:
**- Install our [Socket Mobile Companion app](https://apps.apple.com/app/socket-mobile-companion/id1175638950) which takes care of the discovery and the selection of the reader to connect to.**
**- Write some code to fit the Bluetooth discovery flow to your application's design by creating an UI that starts and shows discovered devices and select them to be paired to your application.**
## Themes selection
The Themes Selection allows to choose LEDs sequences that are played on S550 or S370 devices. Please check the [documentation](https://docs.socketmobile.dev/capture/ios/en/latest/topicsThemesSelection.html "CaptureSDK Documentation - Themes Selection").
## Device Notifications (Battery Level)
The Device Notifications can be configured in order to receive a notification each time one or more of those events occur:
* Battery Level change
* Power State change
* Buttons State change
By default the device notifications are turned off. The recommended usage is to first check if a particular notification is turned off or on. Depending on this reading, then the application can set a specific notification to be received if it is not already set. That setting stays persistent in the Socket Mobile device across scanner shutdown. It is not recommended to set systematically a notification in the device without checking first if that setting is already correct.
For the Battery Level and Power State, it could take a long time before the state changes, so usually the initial value is read using the corresponding `CaptureHelper` Get method.
Last, some devices don't support some of the notifications. If that's the case, an error `ESKT_NOTSUPPORTED (-15)` is returned when trying to set a notification that is not supported.
For more information please check the [documentation](https://docs.socketmobile.dev/capture/ios/en/latest/ "CaptureSDK Documentation").
## Closing `CaptureSDK`
**It is not recommended to close `CaptureSDK` because the scanner will go through reinitialization the next time `CaptureSDK` is open which causes a delay before being able to use the scanner.**
Closing `CaptureSDK` does not affect power consumption, since the scanner stays connected to the iOS host for Bluetooth Classic scanners.
For Bluetooth LE scanners, the CaptureSDK releases the connection to devices or it remains connected to the iOS host if added with Companion.
It is also worth noting that when the Socket Mobile device is connected the power consumption is really minimal, compare to establishing a connection.
If the motive of closing `CaptureSDK` is to not receive any decoded data from the device then the application delegate can simply be removed and the application will no longer receive any event from the scanner until it sets its delegate back again.