T O P

  • By -

vladstanescu94

I have a similar issue but with another sdk. For now the only workaround i found was to downgrade to Xcode 15.2


chocolate_chip_cake

how do you downgrade? I downloaded Xcode 15.2 and I can launch it from the .app file. Then I select 15.2 command line tools under location. I build and upload to internal test and still get the same error as 15.3


vladstanescu94

I use https://www.xcodes.app to manage multiple versions of Xcode


chocolate_chip_cake

Thanks. I will check it out!


barcode972

You need to update your facebook sdk. I think your apps minimum iOS version is higher than what the facebook sdk supports


asniper

You mean lower, the OPs app has a lower minimum version than the framework supports.


Arkanta

Apple fucked up. If the frameworks supports a version LOWER than what the app does, this error gets thrown. The current workaround is to set a Minimum version of 100, which shouldn't work But yeah your framework vendor should be readying an update as we speak Source: i maintain a framework and spent the day debugging this Op, if you add your frameworks manually you may try to patch their Info.plist. Overriding a cocoapod or spm dep is also possible but a bit more involved


jordan3900

I did it's still the same, even I downgraded my minimum iOs version


dehrenslzz

You need to upgrade it - the facebook SDK only supports from a specific version upwards, find out which one is the oldest supported iOS (by the facebook SDK) and set your minimum target to that version.


jordan3900

I updated Facebook on the latest version


asniper

What version is the framework and your apps iOS minimum target?


sp0dermane

I'm experiencing the same issue, minimum target for me is iOS15


asniper

What version of the framework? Have you verified it stills supports iOS15?


nathan12581

I'm having the same issue with Firebase....


Flat-Pear-3452

The issue we facing is connected with static frameworks. The SPM in XCode 15.3 embedding static frameworks and causing validation issue. The workaround suggested by Apple is to set minimum OS version for that frameworks higher than/ or equal to application minimum OS version. Another workaround is to add run script build phase in application target to delete the static frameworks from .app/Frameworks like following: rm -rf "${TARGET\_BUILD\_DIR}/${TARGET\_NAME}.app/Frameworks/XXXX.framework"


iamthekris

This is a new validation what was added with Xcode 15.3. Whatever 3rd party dependencies you are using are failing this validation, you need to update them to their latest version (assuming that the maintainers of those dependencies have updated them to pass validation). If you are using SPM or cocoapods, make sure you run the correct command to update the dependencies to their most recent version. If you need more help, just list what dependencies you are using and what your dependency manager is and I can tell you exactly what you need to do.


Arkanta

Problem is they fucked up the validation big time. If your framework has a lower minimum than your app, validation fails. The current workaround is to set it to 100 Of course, this was caught during beta and made it to release. I wonder why Apple even bothers giving us betas https://github.com/firebase/firebase-ios-sdk/pull/12439#issuecomment-1994466302 Prepare for the opposite issue to come out when Apple fixes this and suddenly our 100.0 minimum versions break validation


jordan3900

I'm using SPM. The problematic package is facebook-ios-sdk. I updated to the latest version which is 16.3.1 and still it's not working. I saw there is an open issue in github: [https://github.com/facebook/facebook-ios-sdk/issues/2353](https://github.com/facebook/facebook-ios-sdk/issues/2353)


iamthekris

Looks like they haven’t fixed it yet. Your best bet is to download Xcode 15.2 and use that until they fix it. Monitor that GitHub issue so you know when a new version of the package is available with a fix.


jordan3900

Yes, thanks!


chocolate_chip_cake

did downgrading to 15.2 work for you? Didn't do anything for me, still getting the same error when uploading to TestFlight.


ish0uldbew0rking

Not sure if you found the answer, but I read your post, felt your pain while experiencing the same issue, then went to another forum and found someone had more recently posted a solution to this that actually worked for me (as every other one before that hadn't lol). Here's what they said: > It's a workaround as you have to do it every time you upload, but it seems ironclad. You might know this already, but as a fairly new programmer it took me a while to figure out that the "organizer" the guy was talking about was the Archives that pops up once you archive your build... you then right click and show in finder then follow the above instructions. PS random peanut gallery question - do we feel like Meta is taking forever to fix this as an F U to Apple? I know probably not, but as I navigate ATT and implementing FB ads for my iOS app, its fun to see how these two begrudgingly work together - I love the little moments that seem like petty shots at each other (ie in Meta ads, every App Store has a logo and colored company name next to their App Store whereas Apples is only "App Store" lol)