What is the recommended way to protect characteristic value from modification while it is being read by a client?
I have a test application with 500-byte long characteristic value. The application updates it every 20 seconds.
On the other end of the connection I have nRF Connect where I manually trigger reading of the characteristic.
From time to time I see that read data is corrupted - half is old value, half is new (updated).
I believe this is because I update the characteristic while it is being read by a client.
I'm using nRF52840-DK with nRF5_SDK_15.3.0_59ac345.
The application is a modified template example - I added a custom service.
