Qt 6.8.0 ITMS-90426 Invalid Swift Support Error When submitting to Test Flight
-
I have a cross platform app written in QtQuick / cpp that started in Qt 6.4.1, and have since upgraded, without issues, to 6.7.3. I regularly deploy to iOS (as well as Android, OSX, Windows, and Linux).
Since upgrading to 6.8.0, and submitting the iOS app to the app store for Test Flight for evaluation, I receive an incomaptible (blocking) invalid binary error from Apple. CMake is my build system. The specific error is:
ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.I have, and have had, the latest GM versions of XCode.
Apple won't allow the app on Connect, even as a Test Flight eval version. I can deploy locally to my iOS devices just fine. Has anyone else in the community seen this issue? Code Signing is managed directly by iOS, and I'm not using any ad-hoc builds (Google returns alot of hits for this error related to ad-hoc builds being submitted to Connect for Test Flight).
When I create a new project in Qt Creator, targeting 6.8.0, and deploy that bare bones app to the App Store, I do not receive that error. There's something about the modules I'm using in my product app, I suspect, that could lead to that error. Here's a snapshot of the modules I'm importing. I don't have any other third party libraries outside of Qt that I'm importing and building.
find_package(Qt6 6.8 REQUIRED COMPONENTS Quick QuickControls2 PrintSupport Gui Multimedia Pdf)Also, for Qt 6.8.0, I have to use this CMake convenience function to build for iOS. This is not necessary for <=6.7.3.
qt_add_ios_ffmpeg_libraries(${PROJECT_NAME})When I downgrade this project to <=6.7.3, I can deploy to iOS just fine.
The reason I'm trying to push for 6.8.0, is that 6.8.0 resolves bugs related to rendering PDFs in QtQuick for iOS. Prior versions of Qt cause hard crashes when rendering PDFs in QML. PDF rendering is currently a high priority feature.
Anyone else experience a similar issue? Looking for a way to narrow down the problem area. I've attempted to replace my custom iOS Info.plist file for the auto-generated Qt Info.plist, and that didn't resolve it. I'll work on narrowing down issues, myself, for now.
Thanks community.
-
It seems it's related to the ffmpeg library, according to others with the same problem from this post: https://www.reddit.com/r/QtFramework/comments/1gh5xb2/issues_with_qt_68_and_ffmpeg_on_ios_anyone_else/
-
Known issue in the Qt bug tracker:
https://bugreports.qt.io/browse/QTBUG-130813?filter=-4&jql=text ~ "ios ffmpeg" order by created DESC
and
https://bugreports.qt.io/browse/QTBUG-129533