What is the current best practice to update or keep updated. I apologize since there is so much noise around this issue I wanted to ask and a ticket seemed like the sanest way.
I am having an issue which I believe should be solved by tx power and I read https://github.com/nkolban/esp32-snippets/issues/197
which I believe is the path to a fix. But I am unsure what is the current best practice to keep up to date or be sure I am on the same version as that fix. I will backup my arduino environment before I make any changes to be able to roll back .
I believe this is best option for you and most arduino ide users https://github.com/nkolban/esp32-snippets/blob/master/cpp_utils/ArduinoBLE.md#replacing-the-version-that-comes-with-arduino-esp32
You can track this repo for any changes, and whenever you see that update is fixing any bugs or add feature that suits you you should update to latest version. Its just my opinion.
Mr @chegewara Is bang on. There is no hard science as to when we refresh the Arduino libraries as distributed with the Arduino ESP32 release. My opinion would be to wait until the official 3.0 release of the ESP-IDF.
I would wait if I could but I am developing a product which I need to be ready enough to demo to people, a
ble spectrometer for ag, which this library does great. I am happy with dealing with a rough road as long as I can ask questions and provide feedback. I was able to get it to update using the build instructions. I believe in your and the community abilities to provide a finished product within the next few months, progress is good.
Thanks for the kind words ... but do realize, that this is an open source, community project. Use at your own risk. If something goes foobar, we'll try and assist as best we can ... but there are no SLAs or assurances ... we all chip in as best we can.
Most helpful comment
Thanks for the kind words ... but do realize, that this is an open source, community project. Use at your own risk. If something goes foobar, we'll try and assist as best we can ... but there are no SLAs or assurances ... we all chip in as best we can.