-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Proper shutdown #149
Comments
It looks like this is it. There's a problem with l2cap servers, but this I'm trying to address upstream. |
Sorry for the delay, looks like you found the solution though. Interesting issue with the l2cap servers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In my application for ESP32S3, we offer similar services both through BLE/L2CAP and WiFi. In order to make things smoothly coexist, upon connection setup, we want to shutdown the respective "other" service.
What's the preferred way to shutdown the stack using
esp-nimble-cpp
? Here is how I set it up:Do I need to remove the callbacks and do I need to keep the handles for the services around so I can stop them?
Or is there a more simple way to cleanup where all the registered services are shut down automatically?
Update: I have found
BLEDevice::deinit
-- is that a coordinated shutdown?The text was updated successfully, but these errors were encountered: