Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a broad renaming and refactoring of the "companion" device setup feature across both Android and iOS platforms, standardizing terminology to "device setup" and improving code robustness and clarity. It also updates the example app to use the new APIs, enhances Bluetooth scanning logic, and adds iOS 18 AccessorySetupKit support for device setup. Below are the most important changes grouped by theme:
API and Naming Standardization:
BleManager.java,CompanionScanner.java) and iOS (BleManager.h,BleManager.mm,SwiftBleManager.swift), including exported methods likecompanionScan→deviceSetupScan,supportsCompanion→supportsDeviceSetup, and related event emitters. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]iOS Device Setup Support:
ASAccessory, and session management for accessory setup flows inSwiftBleManager.swift. [1] [2]Android Robustness Improvements:
CompanionScanner.javaby usingObjects.requireNonNulland checking for nulls before accessing values. [1] [2] [3]Example App Updates:
iOS Permissions:
app.config.jsfor iOS 18 compatibility.