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
Assuming that MTU can be reliably checked on all platforms, Kable should throw an exception if a write is performed with a payload that exceeds the current MTU.
Currently (at least on Android and Core Bluetooth) it appears that the data is silently not sent, which can result in difficult to debug bugs (see #297).
The text was updated successfully, but these errors were encountered:
How can we query the MTU for iOS so we don't even perform write with a payload that exceeds the current MTU. I can see that this method returns the currently negotiated MTU for iOS, but currently it is not exposed throughout the kotlin code. Is there a plan to improve this in the future or maybe there is another recommended way to do this already?
Thanks for the link, I hadn't discovered that method. That'll be helpful when we try to tackle this.
It might be a while before we can prioritize this effort though.
PRs or discussions (to go over possible solutions/API designs) are welcome in the mean time.
Assuming that MTU can be reliably checked on all platforms, Kable should throw an exception if a
write
is performed with a payload that exceeds the current MTU.Currently (at least on Android and Core Bluetooth) it appears that the data is silently not sent, which can result in difficult to debug bugs (see #297).
The text was updated successfully, but these errors were encountered: