Deprecated API Usage - Apple no longer accepts submissions of apps that use QuickTime APIs.
-
Thanks SGaist, so far we haven't found libqqt7engine or QTKit in our libraries. I'm still a little suspicious that QTKit might be in there somewhere, but we haven't found it yet. But I have a few other questions if you have time to answer:
Does Apple accept Apps using vlc player?
Could this be an outdated codec issue?
It seems AV Foundations only uses a few codecs. My programmer used ffmpeg to build our codec libraries. Would my app get rejected if it was using codecs that AV Foundations no longer accepts? Here's an interesting PDF file I found on Google when I searched: vlc player deprecated quicktime api
http://devstreaming.apple.com/videos/wwdc/2013/606xdx2xbp31zp28fdov8p0b6d/606/606.pdf?dl=1
One of the pages mentions all of the codecs that will no longer work with AV Foundations. I think the libraries in my App contain some of these.
Thanks again!
-
Did anyone find a solution for this? We have a mixed QWidget/QML app that does not include any video support and just got declined with the same message:
Deprecated API Usage - Apple no longer accepts submissions of apps that use QuickTime APIs.
This happened after the iTunesConnect update last week using Qt5.3.1. We successfully submitted another edition of this App previously without getting an error message.
We've used MacDependency to browse through all linked libraries, but could not find any links to QuickTime.Framwork. Does anybody know if Qt5.3.1 is really built without QutickTime dependencies? My guess right now is that Qt (= digia Qt) and Qt (= QuickTime) are too similar, but I want to make sure before opening a support Ticket with Apple.
-
@SGaist: the problem occurs with the latest edition needed to submit iOS8 and OSX10.10 apps (XCode 6GM on OSX 10.9.4). The problem also occurred with Xcode 5, but in both cases only after the "new" iTunesConnect interface for uploading Apps got online. It seems Apple made some changes to the validation routines with the interface update.
-
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 :)
