I have a circular problem. I'm having issues when compiling with the hosted builder:
Sending data to remote compiler. Error
Failed to parse certificate file.Error: security: SecKeychainDelete: The specified keychain could not be found.
I checked my Mac and the keychain entry is missing. Probably got wiped out after the xcode 13.4 update. Normally a compile to the local Mac will add the keychain entry, but when I try to start the B4i BuildServer it stops and displays the error "Failed to find xcode version". It's probably looking for xcode 13.2 which is not available. Is there another way to restore the keychain?
I was compiling with the hosted builder with no problems, so the signing key was not an issue. Then xcode got updated and the problem started.
Yes, the xcode additional components are installed but the BuildServer will not start because of the xcode version.
In the first post you say that it doesn't work with the hosted builder. Lets start with this issue. What exactly happens when you compile with the hosted builder?
This error usually happens when the key and certificate do not match. Delete all files in the keys folder. Revoke the certificate and create new ones: Creating a certificate and provisioning profile
Yes I deleted files in the keys folder but it made no difference. I created a test app and was able to compile and run it but when I went back to my real app I got the same keychain error. It looks like the package name causes it to look for the keychain entry and might be related to not being able to start the BuildServer:
$ java -jar B4iBuildServer.jar
Build server version: 7.5
-------------------------------------------------
2022-06-07 11:30:11.959:INFO::main: logging initialized @162ms to org.eclipse.jetty.util.log.StdErrLog
loading default configuration file.
AppPath=/Users/MacAir/Desktop/BuildServer
Mac version 10.16
Failed to find xcode version.
It took a lot of testing to find this, but the problem only occurs when the iCustomListView or xCustomListView library is selected (even if not used). I have no idea why. As soon as the custom list view library is unchecked, the problem goes away.