You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked the documentation and FAQ without finding a solution
I checked to make sure that this issue has not already been filed
I'm sure that question is related to the library itself and not Bluetooth Low Energy or Classic in general. If that so, please post your question on StackOverflow.
I'm running the latest version
Question
I tried searching the issues (open and closed) as well as the Wiki, Google, and StackOverflow...
Perhaps I have not been using the correct search terms, but I was unable to find explicit information WRT using this library.
Use-case:
There will be 2 Expo applications.
The first application will act as the "central" device (on physical device A), this topic/process is covered extensively (good to go) CRUX: The second application will act as the "peripheral" device (on physical device B), where, with the app running, it must define/setup/advertise the services and characteristics expected by the first application (on device A)
The two applications can then communicate over the defined characteristics associated with the expected services.
If this is already an existing feature/capability of this library, I do apologize, and would simply kindly ask for a reference to the existing documentation!
If this is not an existing feature/capability of this library, any information as to why this is not a feature (or a potential roadmap to obtain this feature) would be greatly appreciated!
If you are aware of existing mechanisms to achieve this use-case (using other libraries or external tools), any additional information would be genuinely greatly helpful to me!
Many many thanks in advance!
Question related code
N/A
The text was updated successfully, but these errors were encountered:
@MDale-RAC The library does not currently support acting as a peripheral and it is not on the roadmap. I will record it as a feature request for future consideration. In the meantime, I'll talk with our team to see if they know of another way you can do this.
Prerequisites
Question
I tried searching the issues (open and closed) as well as the Wiki, Google, and StackOverflow...
Perhaps I have not been using the correct search terms, but I was unable to find explicit information WRT using this library.
Use-case:
There will be 2 Expo applications.
The first application will act as the "central" device (on physical device A), this topic/process is covered extensively (good to go)
CRUX: The second application will act as the "peripheral" device (on physical device B), where, with the app running, it must define/setup/advertise the services and characteristics expected by the first application (on device A)
The two applications can then communicate over the defined characteristics associated with the expected services.
If this is already an existing feature/capability of this library, I do apologize, and would simply kindly ask for a reference to the existing documentation!
If this is not an existing feature/capability of this library, any information as to why this is not a feature (or a potential roadmap to obtain this feature) would be greatly appreciated!
If you are aware of existing mechanisms to achieve this use-case (using other libraries or external tools), any additional information would be genuinely greatly helpful to me!
Many many thanks in advance!
Question related code
The text was updated successfully, but these errors were encountered: