I have a device that advertises as `BLE_GAP_ADV_TYPE_CONNECTABLE_SCANNABLE_UNDIRECTED`. When a device connects, it restarts its advertising as `BLE_GAP_ADV_TYPE_NONCONNECTABLE_SCANNABLE_UNDIRECTED`. I read in the softdevice documents that "Non-scannable types do not support scan response data." Was this a new behavior since version 3 of the softdevice?
Previously I was running my softdevice on s132 v3.1. I was not able to receive scan response data while my peripheral was connected to a user. However, since upgrading to s112 v6.1, I am now able to.
Is this behavior expected?