ITMS-90428: Invalid Swift Suppor

Question

kolobok1386 OP

Created Nov ’23

Replies 2

Boosts 0

Participants 2

I am trying to upload a new build of my app from the new Xcode 15.0.1 but it keeps failing with the below error:

ITMS-90428: Invalid Swift Support - The files libswiftMetal.dylib, libswiftCoreGraphics.dylib, libswiftCoreLocation.dylib, libswiftObjectiveC.dylib, libswiftCoreAudio.dylib, libswiftos.dylib, libswiftDarwin.dylib, libswiftsimd.dylib, libswiftFoundation.dylib, libswiftCoreImage.dylib, libswiftQuartzCore.dylib, libswiftNetwork.dylib, libswiftUIKit.dylib, libswiftCoreFoundation.dylib, libswiftCoreMedia.dylib, libswiftCore.dylib, libswiftDispatch.dylib, libswiftAVFoundation.dylib don’t match /Payload/goodville.app/Frameworks/libswiftMetal.dylib, /Payload/goodville.app/Frameworks/libswiftCoreGraphics.dylib, /Payload/goodville.app/Frameworks/libswiftCoreLocation.dylib, /Payload/goodville.app/Frameworks/libswiftObjectiveC.dylib, /Payload/goodville.app/Frameworks/libswiftCoreAudio.dylib, /Payload/goodville.app/Frameworks/libswiftos.dylib, /Payload/goodville.app/Frameworks/libswiftDarwin.dylib, /Payload/goodville.app/Frameworks/libswiftsimd.dylib, /Payload/goodville.app/Frameworks/libswiftFoundation.dylib, /Payload/goodville.app/Frameworks/libswiftCoreImage.dylib, /Payload/goodville.app/Frameworks/libswiftQuartzCore.dylib, /Payload/goodville.app/Frameworks/libswiftNetwork.dylib, /Payload/goodville.app/Frameworks/libswiftUIKit.dylib, /Payload/goodville.app/Frameworks/libswiftCoreFoundation.dylib, /Payload/goodville.app/Frameworks/libswiftCoreMedia.dylib, /Payload/goodville.app/Frameworks/libswiftCore.dylib, /Payload/goodville.app/Frameworks/libswiftDispatch.dylib, /Payload/goodville.app/Frameworks/libswiftAVFoundation.dylib. Make sure the files are correct, rebuild your app, and resubmit it. Don’t apply post-processing to /Payload/goodville.app/Frameworks/libswiftMetal.dylib, /Payload/goodville.app/Frameworks/libswiftCoreGraphics.dylib, /Payload/goodville.app/Frameworks/libswiftCoreLocation.dylib, /Payload/goodville.app/Frameworks/libswiftObjectiveC.dylib, /Payload/goodville.app/Frameworks/libswiftCoreAudio.dylib, /Payload/goodville.app/Frameworks/libswiftos.dylib, /Payload/goodville.app/Frameworks/libswiftDarwin.dylib, /Payload/goodville.app/Frameworks/libswiftsimd.dylib, /Payload/goodville.app/Frameworks/libswiftFoundation.dylib, /Payload/goodville.app/Frameworks/libswiftCoreImage.dylib, /Payload/goodville.app/Frameworks/libswiftQuartzCore.dylib, /Payload/goodville.app/Frameworks/libswiftNetwork.dylib, /Payload/goodville.app/Frameworks/libswiftUIKit.dylib, /Payload/goodville.app/Frameworks/libswiftCoreFoundation.dylib, /Payload/goodville.app/Frameworks/libswiftCoreMedia.dylib, /Payload/goodville.app/Frameworks/libswiftCore.dylib, /Payload/goodville.app/Frameworks/libswiftDispatch.dylib, /Payload/goodville.app/Frameworks/libswiftAVFoundation.dylib.

These optons are true, ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = YES EMBEDDED_CONTENT_CONTAINS_SWIFT = YES

Error occured after updating Xcode to the latest 15.0.1 from Xcode 14, can anybody point to the reason of this issue ?

Boost

Answer 1

kolobok1386 OP

Nov ’23

Just investigated old build (built with xcode 14) which worked and can see that Swift dylibs in Payload/MyApp.app/Frameworks have such output on command "file libswiftMetal.dylib" (libswiftMetal.dylib as an example)

file libswiftMetal.dylib 
libswiftMetal.dylib: Mach-O universal binary with 4 architectures: [arm_v7:Mach-O dynamically linked shared library arm_v7] [arm_v7s:Mach-O dynamically linked shared library arm_v7s] [arm64:Mach-O 64-bit dynamically linked shared library arm64] [arm64e:Mach-O 64-bit dynamically linked shared library arm64e]
libswiftMetal.dylib (for architecture armv7):	Mach-O dynamically linked shared library arm_v7
libswiftMetal.dylib (for architecture armv7s):	Mach-O dynamically linked shared library arm_v7s
libswiftMetal.dylib (for architecture arm64):	Mach-O 64-bit dynamically linked shared library arm64
libswiftMetal.dylib (for architecture arm64e):	Mach-O 64-bit dynamically linked shared library arm64e

And in folder SwiftSupport/iphoneos the same output:

file libswiftMetal.dylib 
libswiftMetal.dylib: Mach-O universal binary with 4 architectures: [arm_v7:Mach-O dynamically linked shared library arm_v7] [arm_v7s:Mach-O dynamically linked shared library arm_v7s] [arm64:Mach-O 64-bit dynamically linked shared library arm64] [arm64e:Mach-O 64-bit dynamically linked shared library arm64e]
libswiftMetal.dylib (for architecture armv7):	Mach-O dynamically linked shared library arm_v7
libswiftMetal.dylib (for architecture armv7s):	Mach-O dynamically linked shared library arm_v7s
libswiftMetal.dylib (for architecture arm64):	Mach-O 64-bit dynamically linked shared library arm64
libswiftMetal.dylib (for architecture arm64e):	Mach-O 64-bit dynamically linked shared library arm64e

But in new build with xCode 15.1 it hase such output in Payload/MyApp.app/Frameworks:

file libswiftMetal.dylib 
libswiftMetal.dylib: Mach-O 64-bit dynamically linked shared library arm64

And in new build (xCode 15.1) folder SwiftSupport/iphoneos output:

file libswiftMetal.dylib 
libswiftMetal.dylib: Mach-O universal binary with 1 architecture: [arm64:Mach-O 64-bit dynamically linked shared library arm64]
libswiftMetal.dylib (for architecture arm64):	Mach-O 64-bit dynamically linked shared library arm64

Seems the content of Payload/MyApp.app/Frameworks is the reason of this error on uploading to App Store. Maybe anyone can help resolve this issue ?

0

Answer 2

BenReedSysC OP

Feb ’24

Same issue here after upgrading to Xcode 15.2.

Project builds fine, runs fine and we can archive and export. Verification using Transport works as well.

Did you ever find a solution for this?

0