In order to protect my device from becoming bricked when APP and NET side implementation of RPC application differs, due to wrong version being flashed or OTA fails on one of the cores, I would like to gracefully handle these errors and make my device available for other OTA attempt.
The thing is, any error I am able to catch via RPC global error handler, makes my device unusable.
Is there, generally speaking, some known ways to handle nRF RPC errors in gentle way?
PS: I am aware of this piece of documentation: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.7.0/nrfxlib/nrf_rpc/doc/architecture.html#error-handling, which states that nRF RPC will not recover due some errors.
Any recommendations?
As an example I would like to recover from situations where my APP and NET application differ in number of defined (supported) groups.
Or if APP part sends an CMD to which there is no implemented handler on the NET side.
These are all examples of wrong nRF RPC usage, but I need to be able to survive trough these never the less.
