access_model_publish_period_set() stopped working when migrating to Mesh SDK 4.2.0

[EAn]

Greetings,

I am currently using nRF5 SDK 16.0.0, Softdevice s140_nrf52_7.0.1_softdevice.hex, and Mesh SDK 4.2.0. I migrated all my code base from  nRF5 SDK 15.3.0, Softdevice s140_nrf52_6.1.1_softdevice.hex, and Mesh SDK 3.2.0. 

I have a Bluetooth mesh device which I hard-coded the publication address and period after initializing. This has always worked just fine, but after switching to the newest SDKs I got a mesh assert in the access_model_publish_period_set... If I comment that line everything works fine and I can setup the publication via the nRF Mesh App.

Could you point me in the direction of what I should be looking at? I've tried backtracking and debugging the error and I was able to trace it all the way back to "void bearer_event_flag_set(bearer_event_flag_t flag)" in /nrf5_SDK_for_Mesh_v4.2.0_src/mesh/core/src/bearer_event.c ... but didn't get any inkling as to what is generating the issue...

I found a workaround where I use a normal timer (app_timer type) and call the publication cb from there... It's not the most elegant solution but works for now, as for the time being we are hardcoding the publication setup in our devices....

Could you please give me some pointers/solutions? Thank you very much!

Best regards!

//EA

[EAn]

Thanks for your pointer. The issue was solved somehow. Your reply made us more aware of the timing and priority issues that may emerge with the mesh SDK. Thanks Tesc!