@NeoNacho Invalid bundle for the frameworks that got moved to SwiftPM. Was complaining about not supporting the minimum OS version listed in the Info.plist (it does, we are already using it, lol), and also complaining about the version numbers in the Info.plists for them. Which - the Info.plists inside there are different from before the migration.
Idk, I’ll have to look into it more. I’m sure I’m doing something wrong. This was supposed to be a noop change :/
@NeoNacho Aaah wow no kidding. We literally just upgraded to 15.3. Might have to put this on hold and wait for 15.4 to do this then? You don't know of any workarounds?
@cjwirth@jsq BTW, to explain what is happening here, 15.3 started embedding any static frameworks from packages into the app bundle in order to retain resources (e.g. privacy manifest), but doing so requires injecting a dynamically linked stub binary to make a valid embeddable framework.
What I fixed in 15.4 is matching the deployment target as specified in the original framework’s Info.plist when creating the stub, but if there are other issues with the framework, they can still crop up.
@NeoNacho@jsq Ah ok yeah that makes sense with what was broken and what was fixed in 15.4. And using CocoaPods (or previous Xcodes) it wouldn’t be an issue because that new framework wasn’t being added.
So at this point we gotta get the upstream to make their version numbers work.
Add comment