Xcode 15.3 and App Store Connect Issue

[johnarnaou]

Xcode 15.3 and App Store Connect Issue

[johnarnaou]

I hope this works 🤞

[neobeppe]

Don't know if devs should stop using FB or FB should change devs

[samcolak]

Solution requires a few steps - Please bare with me..

1. Download the Framework files (at https://github.com/facebook/facebook-ios-sdk/releases for 16.3.1)
2. Extract the zips
3. Download a copy of the Facebook-ios-sdk
4. Modify the file "package.swift" - commenting lines 245 - 249 EXCEPT line 246 (self=.local)
5. Copy the extracted zip files into the Facebook folder under "build/XCFrameworks/Static"
6. In each framework zip modify the file "Info.plist" under "ios-arm64" AND 'iOS-arm64_x86_64-simulator" - You'll see MinimumOSVersion = 12.0 / Change this to 100.0
7. Remove the dependancies in your project (linking to the Facebook sdk @ GitHub)
8. Add dependancy to local instance

DONE !!

[Arideno]

I have the same issue :( I am desperate! If you guys have some workaround while FB support release a fix .........

Just install previous Xcode, you can publish to AppStore Connect with it

[ersel95]

You probably installed the SPM with Dependency Rule which is limiting the version. I changed Facebook-Ios-Sdk Dependency rule to main Branch and everything is good to go now.

[krishan226]

Hi everyone,
Maybe Apple will resolve this issue in the next update, but due to urgent fixes of my current projects, I tried this way to upload the build on Appstore.
I've been facing across all my projects for the past 3 days. For those experiencing similar challenges, here's the solution that worked for me:

• Downgrade Xcode Version: Initially, I was using the latest Xcode version (15.3), but I found that downgrading to an older version resolved the problem. I uninstalled Xcode 15.3 and installed version 15.1 instead.
• You can download older versions of Xcode from this link.
• Resolve Package Dependency Issue: After downgrading Xcode, I addressed any package dependency issues that arose as a result of the version change.
• If you encounter package dependency issues with your SDK packages, you can find helpful guidance on resolving them here.
  I hope this solution proves helpful for others facing similar challenges.
  Best regards,
  Krishan Pahadiya

[jadebowl]

If you need a workaround you could point the Package to the commit e347cce.
They forgot to add the tag but they already bumped to version 17.0.0 3 weeks ago. It worked for me, I was able to Archive my build and send it to App Store Connect. Could be a temporary solution if you need to send it asap.

[EverGod]

This is a serious showstopper. Why is this opened for so long without a solution?

All of the above solutions are just workarounds (to downgrade Xcode), why Facebook does not add the needed lines like:
MinimumOSVersion
X
In all sub-SDKs plist's that does not have them?

[neobeppe]

@johnarnaou I also sent an email to the dev that made last tag 3 month ago. I saw more commits and more pending releases like 17.0.0

[neobeppe]

Got an answer from FB devs:

Hi Giuseppe,

Thanks for reporting the issue. We're now working on that and will keep the community updated.

Best,
Zilin

[umutturemen1496]

Hello Dear Facebook Team, please fix the issue as soon as possible. I am using the main branch to get the most updated version as soon as possible. Nothing has changed since 3 days. Either Apple or you should fix this quickly. We cannot send an update.

[ottosen]

Come on now Facebook! This ought to be dead easy to fix.
It is very tempting to just bin this package and remove FB support.

[ed-smokefree-ai]

Suggesting to use Xcode 15.2 is not a solution if you're building and deploying via Xcode Cloud.

@devedup it is a temporary solution, just modify your Xcode Cloud workflow to use Xcode 15.2 instead of Latest Release.

[sashastg]

Here solution:

From the organizer -> open the archived by finder -> open the content of the app -> frameworks -> framework which has the issue -> info.plist (double click, to open in xcode, if you open in editor its looks like encoded, but in xcode its ok)

MinimumOsVersion = 15.0.0

[mihaicris-adoreme]

Same issue here:

Asset validation failed
Invalid Bundle. The bundle AdoreMe.app/Frameworks/FBAEMKit.framework does not support the minimum OS Version specified in the Info.plist. (ID: d703b2c2-1cea-463d-9d36-d63bd2bdc8b2)

Asset validation failed
Invalid Bundle. The bundle AdoreMe.app/Frameworks/FBSDKCoreKit.framework does not support the minimum OS Version specified in the Info.plist. (ID: 19b532dc-13f4-4ff5-9c56-586af33ee787)

Asset validation failed
Invalid Bundle. The bundle AdoreMe.app/Frameworks/FBSDKCoreKit_Basics.framework does not support the minimum OS Version specified in the Info.plist. (ID: 554d3f99-bcbb-4234-a5fa-ff814287d381)

Asset validation failed
Invalid Bundle. The bundle AdoreMe.app/Frameworks/FBSDKLoginKit.framework does not support the minimum OS Version specified in the Info.plist. (ID: 8d1c9ff9-7cdf-400d-9697-4bcd7d4edc1e)

[VadimYakovliev]

I changed Facebook-Ios-Sdk Dependency rule to main Branch and everything is good to go now.

Nothing has changed, same error.

[samcolak]

SOLVED !!

[martarodriguezm]

For those downgrading as I did, just remove all the dependencies and import them again, it work for me, I have already my update live in the store.

[sam-bensley]

I was able to get around this issue temporarily by downgrading my Xcode to 15.0.1 via the following https://developer.apple.com/download/applications/
Not an idea scenario but at least i can push to app store connect now.

[martarodriguezm]

+1
Same with Facebook SDK version 16.3.1

[ersel95]

I changed Facebook-Ios-Sdk Dependency rule to main Branch and everything is good to go now.

Nothing has changed, same error.

did you try to reset package settings and Update to Latest Package versions?

[krotoff]

+1 here, waiting for the update

[ostatnicky]

If you need a workaround you could point the Package to the commit e347cce. They forgot to add the tag but they already bumped to version 17.0.0 3 weeks ago. It worked for me, I was able to Archive my build and send it to App Store Connect. Could be a temporary solution if you need to send it asap.

No, it doesn't work.

[RinStar2003]

SOLVED !!

How

[martarodriguezm]

Solution requires a few steps - Please bare with me..

1. Download the Framework files (at https://github.com/facebook/facebook-ios-sdk/releases for 16.3.1)
2. Extract the zips
3. Download a copy of the Facebook-ios-sdk
4. Modify the file "package.swift" - commenting lines 245 - 249 EXCEPT line 246 (self=.local)
5. Copy the extracted zip files into the Facebook folder under "build/XCFrameworks/Static"
6. In each framework zip modify the file "Info.plist" under "ios-arm64" AND 'iOS-arm64_x86_64-simulator" - You'll see MinimumOSVersion = 12.0 / Change this to 100.0
7. Remove the dependancies in your project (linking to the Facebook sdk @ GitHub)
8. Add dependancy to local instance

DONE !!

So it is not solved, you just found a workaround.
I finally downgrade xcode to 15.2 until Facebook or Apple solve the problem.

[LaurentiuUngur]

Found another solution by integrating it using Cocoapods

[rromanchuk]

1. care very little about integration partners

Don't hurt TEMU's feelings like that 😆

[Wei18]

Another workaround involves downgrading to Xcode 15.2

#!/bin/sh
mint run XcodesOrg/xcodes install --select 15.2 

ref:

• https://github.com/yonaskolb/Mint
• https://github.com/XcodesOrg/xcodes

[vahidsayad]

It's been 2 weeks, and there is still no fix. What's up with the support?

Here's a temporary fix that works for me:

I downloaded the following frameworks and did not use the rest of the FB frameworks:

FBSDKCoreKit_Basics
FBSDKCoreKit
FBAEMKit

Then, I made the following edit:

In each framework zip file, modify the "Info.plist" file under "ios-arm64". You'll see "MinimumOSVersion = 12.0". Change this to "MinimumOSVersion = 100.0".

After making these changes, my building and submission to the App Store were successful.

(Credit to samcolak)

[devedup]

Suggesting to use Xcode 15.2 is not a solution if you're building and deploying via Xcode Cloud.

[devedup]

Suggesting to use Xcode 15.2 is not a solution if you're building and deploying via Xcode Cloud.

@devedup it is a temporary solution, just modify your Xcode Cloud workflow to use Xcode 15.2 instead of Latest Release.

Cool, didn't know this was an option. Thanks

[jadebowl]

I am also experiencing this issue with the new version of Xcode

[antoinepalazzolo]

I'm also encountering this issue and am unable to upgrade due to #2326. We urgently need attention from the Facebook team on this matter.

[sam-bensley]

I am also experiencing this issue and urgently need it fixed.

[neobeppe]

+1, not possible to update apps with FB right now

[mmdumi]

+1

[larryonoff]

+1

[alpha-moisol]

+1

[SteffenKeller]

+1

[jondlew]

+1

[HSCOGT]

I'm also experiencing this issue with the new version of Xcode.

[gooson]

+1

[fahedalahmad]

+1

[matteocorvaro]

+1

[alpha-moisol]

Dear Facebook Team, we really do need this fixed! This issue is almost 3 days old

[michalnowak061]

same here

[johnarnaou]

Is this repo active ? Last update was 3 weeks ago.. I see multiple issues that are not closed or triaged from a long time ago. Is this the correct place to report this issue ? Does anyone know ?

[al3x88]

I have the same issue :( I am desperate! If you guys have some workaround while FB support release a fix .........

[hanlinag]

+1

[ersel95]

Having the same issue with Xcode version 15.3. Facebook and Google had the same issue and solved with an update. Waiting for an update from FB ASAP.

[Ariandr]

+1

[jeonghanjoo]

+1

[0xWOF]

Hello, I experience same issue when I write iOS Framework. And I solve this issue with updating iOS Framework's Info.plist's MinimumOSVersion from 11.0 to 12.0. I think the issue can be solved by update Facebook iOS SDK to 15+. (14's MinimumOSVersion is 11.0 and 15's MinimumOSVersion is 12.0) If you can not update Facebook iOS SDK, you can solve the issue with temporary modifying Facebook iOS SDK's xcframework's framework's Info.plist's MinimumOSVersion 11.0 to 12.0. (Personally I do not recommend this way)

[ed-smokefree-ai]

+1

Have had to change my Xcode Cloud workflow to use Xcode 15.2 as a temporary workaround until this is fixed.

[VadimYakovliev]

I have the same issue

[KeiroMidori]

+1, same issue here

[dppeak]

+1

[sharva89]

+1

[SamPetherbridge]

+1

[neriusv]

+1

[levochkaa]

Same issue here, unable to move to Xcode 15.3, because of that. Latest commit doesn't work, too

[SajjadKharrazi]

+1

[rajlunia]

This is happening everywhere.
This is the only useful information I could find, no clue how they came up with that temp workaround, though. googleads/swift-package-manager-google-mobile-ads#62 (comment)

Xcode 15.2 (works), and 15.3 (fails)

[LaurentiuUngur]

Any updates on this ?

[Jordan3900]

+1

[KimHyunMin1751]

+1

[oleksandryevdokymov]

I have the same issue. Is there any updates on this?

[michalnowak061]

@ryantobinmeta any updates?

[samcolak]

+1

[alpha-moisol]

Seems like Apple problem

[samcolak]

Seems like Apple problem

Normally I'd agree but knowing Apple (as I do), they will point fingers at people not following the (amended) specification - lol

[mneuburg-livefront]

+1

[RinStar2003]

+1

[rromanchuk]

Does the ads team even know this is their product? Or did they just give up after ATT? Just fast follow other ad networks, at least on the communication part. Deflect to apple, whatever, but bad vibes letting this rot here.

TLDR: (+1 xoxoxo)

[samcolak]

Does the ads team even know this is their product? Or did they just give up after ATT? Just fast follow other ad networks, at least on the communication part. Deflect to apple, whatever, but bad vibes letting this rot here.

TLDR: (+1 xoxoxo)

I imagine that they either 1) care very little about integration partners or 2) this isn't in their scope - In so far as I can understand this happens to be related to the build components of the framework more than the code itself. It can be that the adage, "if it aint broke, dont fix it" applies - For the last 4-5 hours ive been looking to where this "MinimumOSVersion" should be placed - frankly ive been through alot of combinations - If you are using SPM (Swift Package Manager), dropping back to 15.1 (on Xcode Cloud or local building) seems to have some benefits (as long as you have the package.resolved file appearing correctly) - If you are running ObjectiveC (with a bridge) into FB its a bigger headache to drop down to 15.1 - It just dont play ball..

BTW if anyone didn't notice, in 15.3 to have a repo appearing in the GitHub repos, simply "Star" the repo and refresh for it to appear

Take care all !

[samcolak]

Oh - side note - To have a repo appearing in SPM (under repos)....

[RinStar2003]

So it is not solved, you just found a workaround. I finally downgrade xcode to 15.2 until Facebook or Apple solve the problem.

When I downgraded, I see this in my projects: Package.resolved file is corrupted or malformed; fix or delete the file to continue: unknown 'PinsStorage' version '3' at ...

How to fix this?

[alpha-moisol]

So it is not solved, you just found a workaround. I finally downgrade xcode to 15.2 until Facebook or Apple solve the problem.

When I downgraded, I see this in my projects: Package.resolved file is corrupted or malformed; fix or delete the file to continue: unknown 'PinsStorage' version '3' at ...

How to fix this?

Delete Package.resolved file and open project in Xcode 15.2

[samcolak]

Per the above (in step 6) - theres a directory (usually the name of the sdk framework file) before you see the Info.plist

You need to do the 2 Info files (in simulator and iOS) as the CI infrastructure runs to check this on the GitHub repo

Additional note - No its not solved @martarodriguezm - Its a workaround to move us all forward for now

Per anyone downgrading, you'll see an issue with Package.resolved - this doesnt get autogenerated by the SPM at the moment - seems theres another bug...

[samcolak]

Solution requires a few steps - Please bare with me..

1. Download the Framework files (at https://github.com/facebook/facebook-ios-sdk/releases for 16.3.1)
2. Extract the zips
3. Download a copy of the Facebook-ios-sdk
4. Modify the file "package.swift" - commenting lines 245 - 249 EXCEPT line 246 (self=.local)
5. Copy the extracted zip files into the Facebook folder under "build/XCFrameworks/Static"
6. In each framework zip modify the file "Info.plist" under "ios-arm64" AND 'iOS-arm64_x86_64-simulator" - You'll see MinimumOSVersion = 12.0 / Change this to 100.0
7. Remove the dependancies in your project (linking to the Facebook sdk @ GitHub)
8. Add dependancy to local instance

DONE !!

So it is not solved, you just found a workaround. I finally downgrade xcode to 15.2 until Facebook or Apple solve the problem.

Indeed - its an intermediate fix

[samcolak]

The way the Facebook-sdk operates (for iOS) is that it downloads the framework files from GitHub - Theres no way around this than for FB to update the framework files directly. Not sure thats going to happen short-term

[andreyoshev]

+1

[Dimillian]

Any update?????????

[RinStar2003]

One of the basic and simplest solutions is to download Xcode 15.2 and use it for now

[cathalfarrell]

I can't submit to the App Store using Xcode 15.3 until this is fixed so I've had to revert to 15.2 instead.

[NicolaiBure]

Have to delete the package, and comment usage. Next week Im going to try again. You need to test when Xcode and iOS updated or before in betas

[ersel95]

Have to delete the package, and comment usage. Next week Im going to try again. You need to test when Xcode and iOS updated or before in betas

You can use #if canImport(Module) rather than commenting the code. With this way, you do not have to comment & uncomment.

[mkandler]

+1

[omz1990]

+1

[ArturoLee]

+1

[SajjadKharrazi]

any update!?!?!?

[Jodebjo]

+1

[davut]

Can we at least get estimate time this task is going to be done?

[ozgurshn]

Same issue with Xcode 15.3 Facebook SDK 16.3.1

[tnorbert]

I tried every suggested fix but only downgrading to xcode 15.2 helped :( This is madness that weeks passed since this bug revealed itself and other devs already fixed their library (like firebase)

[colemancda]

Also seeing this in my apps.

[arthurofbabylon]

From the organizer -> open the archived by finder -> open the content of the app -> frameworks -> framework which has the issue -> info.plist

MinimumOsVersion = 15.0.0

This works.

Note that the Minimum OS Version should match the app's Minimum OS Version – not necessarily 15.0.0.

Note that you'll need to do some right-clicking > Open Package Contents in order to find the frameworks' info.plist file.

Thanks @sashastg

[cemege]

Same issue:

• Xcode 15.3 (15E204a)
• Facebook SDK 16.3.1

[srostagno]

Hello, same issue, had to rollback to Xcode 15.2 :(

This didn't work for me:

From the organizer -> open the archived by finder -> open the content of the app -> frameworks -> framework which has the issue -> info.plist
MinimumOsVersion = 15.0.0

This works.

Note that the Minimum OS Version should match the app's Minimum OS Version – not necessarily 15.0.0.

Note that you'll need to do some right-clicking > Open Package Contents in order to find the frameworks' info.plist file.

Thanks @sashastg

[AntonPetrov83]

I have Xcode 15.0.1 and similar error is there. As I can see it is an error reported by App Store Connect after remote validation of the bundle. I have tried altool and Xcode Organizer to upload the build - outcome is the same:

Error: Asset validation failed Invalid Bundle. The bundle ***.app/Frameworks/IASDKCore.framework does not support the minimum OS Version specified in the Info.plist.

Very intriguing that XCode 15.2 solves the issue of the App Store Connect...