Ryan Powell
Ryan Powell
Interesting, could you try removing the code to get the services and just loop while connected and see what the logs show? Also try this while accepting the peer connection...
Perfect, thanks! That's the data I was hoping to see. Looks like something isn't communicating the peer parameter response, not sure why that would happen but I'll look into it.
It's working fine for me for both simple and long reads, what IDF / NimBLE version are you using?
Strange for sure. With that small amount of data it should not be a long read issue so that's not a problem. What is the client device that is reading...
I've attempted to reproduce this issue and still have not been able to. The packet header length check is a bit of a hack to workaround NimBLE spamming the callback...
Thanks, I'll see what I can do about this.
Unfortunately I am still unable to reproduce this locally, I suspect I would need to use your apps for this. I did come up with a potential workaround, it's not...
@huming2207, Thanks for confirming the patch. I'll merge that soon. Are you also getting this issue when using a custom phone app?
Awesome, thanks for the update!
Interesting, the patch should be working for this as it also checks if the data size is less than the MTU, perhaps the MTU is not set somehow...