We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
With CoreBluetooth I can save peripheral identifier, and later – even after app restarts – can use that identifier to get CBPeripheral in
CBPeripheral
let peripheral = centralManager.retrievePeripherals(withIdentifiers: [identifier]) .first!
Then proceed with the retrieved peripheral as usual:
centralManager.connect(peripheral, options: nil)
Here is a project demonstrating this: https://github.com/paiv/btpage
Currently this is not possible with PTDBeanManager since every operation checks against internal list of beanRecords discovered.
PTDBeanManager
beanRecords
What is your suggested workaround for an app to store known peripheral identifier and then connect to that peripheral by its identifier?
The text was updated successfully, but these errors were encountered:
Fix PunchThrough#31 Allow rediscovering bean by peripheral identifier
48766ba
de565a6
Merge pull request PunchThrough#31 from PunchThrough/update-fw-bean+
c741130
Bean+ FW Update
No branches or pull requests
With CoreBluetooth I can save peripheral identifier, and later – even after app restarts – can use that identifier to get
CBPeripheral
inThen proceed with the retrieved peripheral as usual:
Here is a project demonstrating this: https://github.com/paiv/btpage
Currently this is not possible with
PTDBeanManager
since every operation checks against internal list ofbeanRecords
discovered.What is your suggested workaround for an app to store known peripheral identifier and then connect to that peripheral by its identifier?
The text was updated successfully, but these errors were encountered: