In some rare occasions, you may come across an issue where 18 R4 or newer would fail to sign a 3rd party plugin but would succeed in the 18.x. This issue is due to a change in the signing rules where 18 R4 or newer adds another check to make sure the plugin's file structure is correct. For example, outdated plugins may have the manifest.json file located in the Contents folder instead of the Resources folder. This misplacement of a file would cause 4D to fail the signing process.

To resolve the issue, it is best recommended to contact the original provider for the plugin and request that the plugin adhere to the new file structure rules and have the plugin resigned with the provider's certificate in order to successfully sign and build the 4D application.