This is not a certificate issue. the problem is that one of the dylibs that Xojo copies into the bundle is not getting signed with the same certificate as the rest of the bundle, leaving the signature broken.
Sounds pretty similar.
I had this a few years ago, caused by signing which included the wrong certificate.
But at least you know where the issue lies now. That is good.
@Jeff_Tullin - When quoting, please always include the person that youâre quoting. The way you wrote that makes it look like both of those quotes are from me, whereas the second one is actually from you.
Youâre right, I do. The problem is that Xojo isnât signing the entire contents of the bundle when doing a debug run with the same certificate. In this case, the IDE is choosing ad-hoc (which is really annoying if youâve selected a Team and a Build Type) but then not signing everything that it copies into the bundle, specifically rbframework.dylib which continues to have Xojoâs signature attached. This mismatch is whatâs causing me issues right now and not something that the average person is going to be able to track down by themselves.
Letâs take my WeatherKit wrapper for instance. I build and sign those frameworks. The user is expected to use a CopyFilesStep to copy that framework into their bundle. When you run, you end up with the WeatherKit framework with my signature, rbframework.dylib with Xojoâs signature and the binary and the bundle with an ad-hoc signature. iOS sees this as the signature for the bundle being broken because there are three different signatures. The fix is to create a post-build script which goes through and re-signs the necessary contents and then the whole package, but again, not something that the average person is going to know to do or how to do it.
@Greg_O So Iâm right if I say that you forgot to include some important steps in the description of the Issue you created, or it just fails also in your case on empty projects âwithout anything elseâ as the description states?
The case does not say that the project fails to run. it says that some features may fail to run if the signatures donât match and asks that Xojo make it so all the pieces are signed the same way.
âWhen running an empty iOS app on the simulator, the bundle contains rbframework.dylib, which it doesnât if you build the app. The problem is that the code signature on this framework is not being replaced with the signature used for the rest of the bundle. This can causes the bundle signature to be invalid and for some features to not work. Please make the build process sign all binary objects in the bundle in debug mode.â
No mention to add something else to the project. Ok, sorry⊠probably I understood it wrong, then. 