[Interest] Mac App Store submission issues

[Till Oliver Knoll]

Am 15.02.2012 um 14:36 schrieb Matilainen Pasi <pasi.matilainen at digia.com>:

> Since the information about submitting Qt-based applications to the Mac
> App Store is scattered around in mailing lists ...

First off, thanks a lot for this great summary.

(And also for that other codesign summary!)

Indeed, information about how to get an application into the (any) "App Store" becomes more and more... hmmm... clouded ;)

A chapter in the Qt docs - somewhere in http://developer.qt.nokia.com/doc/qt-4.8/deployment.html - would be very helpful.

For the Mac App Store that could be:

- How and what to codesign

- What identifiers (company name, "bundle identifier", ...) to set and how (Info.plist, Qt API calls, ...)

- What modules are known to be rejected (WebKit)

- ???


It shouldn't describe "how to deploy a Mac application" (that's already described elsewhere) in detail, nor should it "copy" the Apple docs about sandboxing (linking there instead).

But I imagine a "fully working and acceptable" example app, with all necessary (if possible) steps done with qmake/*.pro files ("custom targets").

Maybe a few last words about uploading (XCode only? Or are there command line tools as well?) would not harm either.

Well, a minimal step-by-step manual, without explaining why to codesign or the theory behind it etc.


> 
> - File open/save dialogs crash when the application runs in sandbox
> (QTBUG-21609). 

That reminds me that someone wrote about "Recent Files" menus. One just needs to be aware that (to my knowledge) there exists no "Qt only" solution: One can't just store the filepaths anymore and then open those files via QFile, for example.

Cocoa applications solve this "automagically" in that the framework itself (was it NSDocument? Can't remember) provides a "Recent Files" functionality (which off course works nicely together with the sandboxing).

But as long as Qt doesn't provide a "QRecentFiles" class this isn't a Qt issue, IMHO. So for the time being one needs to dig into the Cocoa API and write platform-dependent code (anyone did this already? What APIs did you use? :))


Cheers, Oliver