ITMS-90429: Invalid Swift Support – Swift libraries not at expected location in iOS app submission

Question

dharmik808 OP

Created 1w

Replies 8

Boosts 0

Participants 2

Hello Apple Developer Community,

I’m facing an issue when submitting my iOS app to App Store Connect.

ITMS-90429: Invalid Swift Support libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreGraphics.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftCoreImage.dylib aren’t at the expected location: /Payload/Runner.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it.

My setup:

Using Flutter for iOS development Flutter version: 3.32.8 Xcode version: Version 16.3

What I have tried so far:

Cleaned build folder: flutter clean Upgraded Flutter and CocoaPods to the latest version. Rebuilt the project using latest Xcode GM version. Verified that Always Embed Swift Standard Libraries is set to YES in Xcode. Reinstalled pods and ensured use_frameworks! is correctly set in Podfile.

Despite this, I still get the same error.

My questions:

What is the correct way to ensure the Swift libraries are embedded in the correct location for Flutter apps? Is there any known issue when building with Flutter and integrating static .a libraries that could cause this problem? Has anyone successfully submitted a Flutter iOS app with external static libraries linked and avoided this error?

Are there any manual steps required to fix the location of Swift dylibs during the build process?

Thank you in advance for your help!

Boost

Answer 1

DTS Engineer OP

Apple

1w

Can you post a file listing of your app? Export the app from Xcode as an .ipa file for the App Store, and then run unzip -l /Path/To/YourApp.ipa, and post that output here. Make sure to use backticks to format as a code block, or if the listing is big, use the file attachment feature.

Since your app is created with Flutter, a third-party tool, it's likely that you'll have to resolve this by working backwards from the build producing these errors into their tools, and you may need to talk to their support for help. My goal with the above is to at least point out more precisely why the app's bundle structure is wrong, to enable you to begin working backwards into their tools to correct for this.

— Ed Ford,  DTS Engineer

0

Answer 2

dharmik808 OP

1w

Please find below attachement of file listing of my app

file listing.txt

0

Answer 3

dharmik808 OP

1w

Thank you for your review.

I have checked the IPA structure of my app, and all the libraries listed in the error message are present in the correct location: Payload/Runner.app/Frameworks/

All required dylibs are included in the IPA structure as expected.

0

Answer 4

dharmik808 OP

1w

@DTS Engineer Have you had a chance to review the file listing of my app? If you noticed any issues, I’d really appreciate your help in resolving them.

0

Answer 5

DTS Engineer OP

Apple

1w

What is your minimum deployment target set to? All of these libswift* files should no longer be included. They were necessary for compatibility purposes on iOS versions prior to Swift being built into iOS directly, which is long past now.

14221248 09-16-2025 10:33 Payload/Runner.app/Frameworks/libAudioFeature.a

This is also an issue — that's a static library. .a files should never show up in a final app bundle, because their contents has been linked into some other binary during the build process.

— Ed Ford,  DTS Engineer

0

Answer 6

dharmik808 OP

1w

@DTS Engineer

What is your minimum deployment target set to?

minimum deployment target set to 1

This is also an issue — that's a static library. .a files should never show up in a final app bundle, because their contents has been linked into some other binary during the build process.

How can I integrate a static library (.a file) into an iOS app so that it does not appear in the final app bundle?

Currently, I have defined a .podspec file and installed it via pod install.

0

Answer 7

DTS Engineer OP

Apple

1w

minimum deployment target set to 1

That sounds like your app's version number or maybe its build number. The deployment target is the minimum iOS version your app supports. It should be at least iOS 15, if not something more recent. If it's something older (like iOS 12), then you should raise it and expect to see the libswift files disappear from your app, since they aren't needed for recent iOS versions.

How can I integrate a static library (.a file) into an iOS app so that it does not appear in the final app bundle?

It should appear in the Link Binary with Libraries build phase, and not subsequently appear in any build phases that copy files into the built app. Cocoapods is a third-party tool, so you'll want to check that they aren't doing anything to copy the file and seek their support if you need help with configuring their tool.

— Ed Ford,  DTS Engineer

0

Answer 8

dharmik808 OP

1w

minimum deployment target set to 1

It was a typo; it is 13.

By the way, thanks for your help. Issue resolved.

1