Rick, have to issue another readValue call, as this is profile-specific. What you write into a characteristics is not linked to what is returned when you read it. There are also write-only characteristics (control points) where reading out a value wouldn't make sense at all. It's just a convenience for many characteristics like "Device Name", that the value that was previously written is stored for later read-out. Etan On 11.06.2013, at 08:40, Rick Mann <rmann@latencyzero.com> wrote:

In the callback after writing a characteristic's value, does the characteristic.value reflect the newly-written value? Or do I have to issue another -readValueForCharacteristic: call?

-- Rick

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/kissling%40oberon.ch

This email sent to kissling@oberon.ch

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com