Hi,
My application is currently using s132 v5.1.0. The Release notes for s132 v6.0.0 say:
"Fixed an issue where incorrect timing calculations during the LE Data Length Update procedure could lead to an assert."
Upgrading the SoftDevice is very difficult at our stage of development, so we would like a way to avoid this by compensating in our application.
If the Central requests a Data Length Update, how can the application avoid the conditions that cause this issue? I've tried calling "sd_ble_gap_data_length_update(connHandle, NULL, NULL);", but I'm not sure whether using automatic values will reliably prevent the assert.
