Brainstorming: What could be a possible reason to end up with zero elements after provisioning?

[BlueMike]

Dear Nordic Experts,
 
although the title says it all, please allow me to briefly explain the situation:
I'm working on a ble mesh firmware and an accompanying Android app. The firmware is working well so far. Provisioning, connecting, setting values, all works as intended using the Nordic nRF Mesh app. So this question relates to the Android nRF Mesh library.
 
Now about the app:
For efficiency reasons, I've decided to develop it in Flutter with a small native Android plugin that handles everything mesh related. The native Android plugin does basically the same as the example app from Android-nRF-Mesh-Library. Except one "minor", "little" thing:
After provisioning, the (Android) method MeshManager.getNodes() reports the new node with zero elements. Now the question is, what could be a possible reason for losing the Elements during provisioning?
Or to ask differently: Imagine you want to provision a node but skip its element, what would you change in the provisioning process of the Android example to accomplish that?
 
Please be aware that this is a brainstorming question and that every idea is welcome!  
Thanks a lot for your advise,
Michael.

[Hung Bui]

Hi BlueMike, 
I will forward the question to our Android team. 
I'm not very familiar with the Mesh app code but according to the spec, the number of elements is provided when the provisionee sends provisioning capabilities right after the invite. You can find the provisioning sequence here.

I would suggest to use a sniffer to check if you receive the capabilities properly. 

[BlueMike]

Hi Hung Bui,
 
Thanks for your help! Please close this case. It turned out that my Android implementation messed up the order of calls when provisioning multiple devices in a loop, which led to "half-provisioned" nodes.