While diagnosing an iOS problem for a customer today, I came across a situation where the code signature for the iOS app bundle being sent to the simulator was invalid. I thought that I had screwed something up so I dug a little deeper. What I found was that when running on the simulator, Xojo includes a dylib called rbframework.dylib in the bundle, but does not sign it properly. It still has the Xojo code signature on it and since app bundle contents all need to be signed by the same identity, the overall bundle signature reads as invalid.
I think that the screenshot (and related bug involving iOS 17 / Xcode 15) doesnāt relates with the issue exposed by Greg. In fact, the one involving iOS 17 / Xcode 15 has been fixed already: https://tracker.xojo.com/xojoinc/xojo/-/issues/74073
We will look into the signing issue but Iām kind of surprised because (AFAIK) we havenāt made changes on that.
On my tests I can run apps in the Simulator without problems. Please, it would be good if you can attach some example project (even if privately) showing the problem so we can dig into it.
Pretty sure I had this a few years ago, caused by signing which included the wrong certificate.
Took me a long time to fix it, trying to remove unwanted certs and profiles.
Try to install back Xcode 14.x, selecting its toolchain, and it should work again (always you donāt need to test on iOS 17.0 devices, because Xcode < 15 doesnāt support iOS 17).
I would be a better idea for Xojo to keep up with the apple changes. My xcode auto updates since i use xcode separately too. Having 2 versions cost me lots of valueable system space.
For now i will use the earlier version of xcode bug please try to keep up. (I know you are doing your best, itās just costing so much time not to be able to do, debug, build thingsā¦)
I would be a better idea for Xojo to keep up with the apple changes. My xcode auto updates since i use xcode separately too.
Yes, we completely agreeā¦ and we did it as soon it was possible. In this case Apple changed things (once more time) and we reacted to adapt Xojo to these BUT we canāt apply them to Xojo releases previous to the one we are working in (the next one to be released)ā¦ because thatās not possible.
Anyway, the solution to this specific problem is quite simple because both Xcode versions can coexist in the same Mac ( < macOS Sonoma ). Believe me, this is not an unusual situation even for developers using just Xcode.
As said in one of my previous replies in this thread (and also added to the Issue #) By now, I was not being able to replicate that issue in the Simulator even using Xcode 15 and even running it under Sonoma.
I get that you wouldnāt go back years, but it shouldnāt be impossible to make a VM holding the code and environment āas it wasā at release time for a couple of builds back.
Xojo iOS has never been capable of the followingā¦
Does my Xojo license expire?
Yes, but you can continue to build with any Xojo releases prior to the license expiration date, indefinitely.
Did you check the āWWDC Developer Certificatesā that expired? Iāve deleted the expired onceās before when i had issues building due to signatures failing. Make sure you donāt require to keep the old oneās.
