Qt 6.3 or newer - submit to Apple App Store, Sandboxing, and QtWebEngine
-
We are currently building our App on Qt 6.3 under Enterprise license using std distribution model with Sparkle updating. Windows is using Indigo Rose Setup Factory and TrueUpdate. That all has been working fine for 15 years.
We would like to switch to App Stores and are looking at the issues surrounding sandboxing and not using private or deprecated apis.- Are there any available documents in the steps required to set up sandboxing, containerization, etc. using Qt functions for directory locations without going to Obj-C or Swift functions?
- We are using QtWebEngine. There are reports of Entitlement challenges that are most likely solvable - we are using full code signing and notarization now.
- But there are also reports of rejections due to the use of private and deprecated APIs in QtCore and QtWebEngine.
We are set up to build in Xcode both standalone (our new model) and using a separate packaging process during command line build and bundle assembly.
What's the story on all of this before my team starts burning time?
Help would be appreciated.
-- Harald
-
Regarding point 3. QTBUG-107167 refers to this issue and gives you the solution. The Qt for macOS page also refers.