The current implementation of the compatibility checking does not make distinction between a missing message and message with different CRC.
This has recently caused issue in the last VPP release 23.06 where new messages where added to interface API which caused the compatibility check in examples fail. As a quick workaround the examples now only log warning message on failing this check for interface API.
The proper solution for this is to fail only if the messages that are being checked actually exist in the connected VPP and are truly incompatible - have different CRC.
The current implementation of the compatibility checking does not make distinction between a missing message and message with different CRC.
This has recently caused issue in the last VPP release 23.06 where new messages where added to
interfaceAPI which caused the compatibility check in examples fail. As a quick workaround the examples now only log warning message on failing this check forinterfaceAPI.The proper solution for this is to fail only if the messages that are being checked actually exist in the connected VPP and are truly incompatible - have different CRC.