Hi,
It looks like the nRF Mesh App on Android configures incorrect CCCD when an unprovisioned device exposes both Provisioning and Proxy Service in its GATT Database.
Though according to Mesh 1.0 spec the "unprovisioned" device "shall" not expose both Provisioning and Proxy services, the nRF mesh App should also write to provisioning Data out CCCD of the unprovisioned device. The nRF mesh App on iOS seems to be doing this where as on Android it writes to the Proxy CCCD(The last encountered CCCD in Discovery process).
To observe this behavior, one could run the "MESH/CL/PROX/BV-01-C" testcase from PTS 7.2.1 or PTS 7.3.0 where PTS is the Node and Client is nRF mesh Android App.
From inter-operability point of view, there could be many available mesh devices which exposes both the services and this behavior seems to be a blocker on Android.
Regards,
Srikkanth