Skip to content
New issue

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

Document best practices on iOS #974

Open
peitschie opened this issue May 30, 2023 · 0 comments
Open

Document best practices on iOS #974

peitschie opened this issue May 30, 2023 · 0 comments

Comments

@peitschie
Copy link
Collaborator

Spawned from discussion on #963

The best approaches found on Android are:

  1. Use autoConnect and don't explicitly scan (i.e., let the OS schedule this itself) (in iOS, autoConnect is implemented purely in the JS layer, and is identical to approach 2)
  2. Explicitly scan and then use connect
  3. (Maybe) for a non-bonded device, it's safe to just use connect without an explicit scan (to be confirmed)

Additional things worth documenting:

  1. Handling Bluetooth authorization
  2. Known quirks regarding isEnabled state
  3. Background processing vs Restore state

Documenting the known caveats and quirks would help implementors more effectively use this plugin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant