Deprecated API Usage - Apple no longer accepts submissions of apps that use QuickTime APIs.
-
Sounds like you should take a look at the "bug report system":http://bugreports.qt-project.org to see if it's something known, if not please consider opening a new report providing as much details as possible to reproduce the failure.
Does it also happen with a minimal default project ?
-
Yes, QT = Quicktime and Qt or qt = digia qt. I suspected that this might be an issue too, but it wasn't.
My programmer looked deeper into my libraries and it turns out that some of my libraries did have QTKit (which Apple released years ago) references in them. My app is video based and uses ffmpeg and vlclib and it was somewhere within these libraries that he found QTKit. He removed them and my app was accepted recently to the App Store.
Here's more info about QTKit: https://developer.apple.com/quicktime/
Can you use MacDependency to search for QTKit instead of QuickTime.Framework?
-
It's not qt, it's Qt.
Good point about QTKit though, Apple is getting tricky with their frameworks
-
We've verified all libraries linked with our app and found that libqqt7engine.dylib links agains QtKit.
https://bugreports.qt-project.org/browse/QTBUG-41326
I'm not quite sure why the dylib was copied to our app bundle by macdeployqt in the first place - we don't use multimedia features in our app.
-
Webkit ? Got QT += multimedia somewhere in your project ?
-
What modules are you currently using ?
-
webkitwidgets wouldn't surprise me as having a dependency on multimedia.
You can use otool -L on the libs to check
-
Just to finalize discussion: Yoann Lopez fixed the issue for Qt5.4 - there was an outdated reference to QuickTime, which is for supporting Mac OS X 10.6. As support for Mac OS X 10.6 was dropped, this is no longer needed in the future. This solved the issue for me! Thanks!!!
-
Nice !
Then please update the thread title prepending [solved] so other forum users may know a solution has been found :)
