I've had this annoying issue for several months where notify payloads were corrupted json but reading the characteristic worked correctly in my iOS app.
Looks like this is something nimble is doing internally, it's fitting the payload into the MTU and dropping the rest off the end.
What was tough was that I check all return values from esp-nimble-cpp and nothing ever returned a return value to indicate an issue.
It would be great if esp-nimble-cpp had some mechanism to indicate that this truncation was occurring, perhaps through an additional payload check in sendValue() where the return value could be an enum instead of a bool where if truncation occurred you'd return a SENT_TRUNCATED value or something.
Thoughts on this issue?
I've had this annoying issue for several months where notify payloads were corrupted json but reading the characteristic worked correctly in my iOS app.
Looks like this is something nimble is doing internally, it's fitting the payload into the MTU and dropping the rest off the end.
What was tough was that I check all return values from esp-nimble-cpp and nothing ever returned a return value to indicate an issue.
It would be great if esp-nimble-cpp had some mechanism to indicate that this truncation was occurring, perhaps through an additional payload check in sendValue() where the return value could be an enum instead of a bool where if truncation occurred you'd return a SENT_TRUNCATED value or something.
Thoughts on this issue?