Re: Sending ATT Prepare Write Request to iOS 7
Re: Sending ATT Prepare Write Request to iOS 7
- Subject: Re: Sending ATT Prepare Write Request to iOS 7
- From: K S <email@hidden>
- Date: Wed, 07 Aug 2013 15:23:31 -0500
Sorry, that was a typo. The remaining 10 bytes, written with offset 20.
For more information, my peripheral is not communicating with my own app. I'm attempting to communicate with the ANCS. But the ANCS characteristic I write to is confirmed receiving the first 20 bytes of the message, because I receive a notification from it with the requested data from that first 20 bytes. But I do not get anything from the information I had requested in the remaining 10 bytes.
My understanding of the prepare write/execute write commands are that the execute write should atomically write all data that was prepared to the appropriate handle(s), but this does not seem to be the case here. It seems to be writing the data of the first prepare, but not the second.
On Wed, Aug 7, 2013 at 3:09 PM, Jason Conn
<email@hidden> wrote:
No one can say for certain without being able to see the app side of things (your
peripheralManager:didReceiveWriteRequests: implementation), but
I send a Prepare Write Request with the remaining 10 bytes, offset 0, and receive a Prepare Write Response with matching data and offset
You've just overwritten the first 10 bytes of your previous write.
Can anyone confirm whether using a Prepare Write Request from a peripheral device to iOS 7 seed 5 works correctly?
I'm attempting to write data to a writeable characteristic, but the data is longer than the MTU, so I use prepare write requests instead.
For an example case, say I have 30 bytes of data, but can only fit 20 bytes in the first request, and the remaining 10 in the second request.
I send a Prepare Write Request with the first 20 bytes, offset 0, and receive a Prepare Write Response with matching data and offset
I send a Prepare Write Request with the remaining 10 bytes, offset 0, and receive a Prepare Write Response with matching data and offset
I send an Execute Write Request, and receive an Execute Write Response indicating the write succeeded.
The problem is, it appears as if only the first 20 supplied in the first prepare write request were actually written to the characteristic.
Can anyone confirm or deny whether this problem exists, or if there is a workaround for it or if I am doing something wrong? Thanks.
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden