A common error when building components or 4D applications is Signed file: CertificateName: no identity found. This error is found in the buildApp.log.xml file and might also cause an alert in 4D containing Code Signature failed. Please read more about this error in this Tech Tip: Resolving Certificate Authority Signing and Trust Issues on macOS Sequoia.

Depending on the business requirements of an application, the issue might be resolved with a self-signed certificate generated with the Apple Certificate Assistant.

In the Build Application menu, click on the Licenses and Certificates tab, then on the button Generate self-signed certificate. This will prompt the Apple Certificate Assistant.

Choose the following options when prompted and name your certificate:

Create a certificate for yourself - Certificate type: Code Signing

Back in 4D, in the Licenses and Certificates tab, in the bottom signing section, please make sure that Name of certificate matches the name of the certificate just created.