Use Kable with a platform native ScanResult?

[curioustechizen]

Are there any ideas around using Kable with an already connected peripheral?

Context: I want to introduce Kable into an existing codebase (Android and iOS) that already uses platform native APIs to communicate with a BLE peripheral. It is what one might call a legacy codebase.

Now we are introducing a new version of the peripheral and for this I want to use Kable for communicating with it. However, the app would still need to continue supporting the older version of the peripheral using the existing legacy code.

The way I envision this is:

• Mobile app continues to use existing platform APIs to perform a scan. It scans for both versions of peripherals.
• Depending on which one the user wants to connect to, app either uses existing legacy code branch; or Kable APIs to connect to the peripheral and communicate.

This would require "entering the Kable flow" differently from the existing APIs. Specifically, it would require handing off a platform-specific scan result object to Kable. This is in essence the opposite of #905.

[twyatt]

Is #937 what you had in mind?

[curioustechizen]

This looks great for Android.
How about on iOS? It would mean using the CBPeripheral object passed to centralManager(_:didDiscover:advertisementData:rssi:) and creating a Kable Peripheral from that.

[curioustechizen]

Never mind, I see there already exists an API for this on iOS - one that takes a CBPeripheral and returns a Kable Peripheral.
https://juullabs.github.io/kable/kable-core/com.juul.kable/-peripheral.html