gt;
> Could you please describe what's the procedure for getting the private API
> usage list from the MAS?
>
> On 08 May 2017, at 22:29, Adalid Claure wrote:
>
> For the fun of it, I tried submitting my app and yeah, it was rejected:
>
> Your app uses or references the fol
t; its current state will not be app store compliant (because of the sandbox
> issue, and because of the private API usage).
>
>
> On Mon, May 8, 2017 at 7:41 AM, Alexandru Croitor > wrote:
>
>>
>> On 08 May 2017, at 13:33, Adalid Claure wrote:
>>
>&
;/qt_source/qtwebengine/src/
> 3rdparty/chromium/base/mac/foundation_util.mm:241" to hardcode the bundle
> id to your "team_id + suffix" entitlement key. That made it work for me.
>
> Regards, Alex.
>
> On 06 May 2017, at 14:46, Adalid Claure wrote:
>
> FWIW,
t case (no QtWebEngine usage), that that’s something I could look at,
> and something we could eventually add an autotest for.
>
>
> Morten
>
>
> > On 28 Apr 2017, at 18:49, Adalid Claure wrote:
> >
> > I have a desktop app that I have been trying to get onto t
Does this mean that at some point this new QtWebKit would be packaged with
Qt (like in the old days)?
On Wed, May 3, 2017 at 10:25 AM, Sergio Martins
wrote:
> On 2017-05-03 15:02, Konstantin Tokarev wrote:
>
>> Remaining question is versioning. While it's fine to dub current
>> release "5.9" (bu
I have a desktop app that I have been trying to get onto the Mac App store
but I have been having problems getting it to run in sandbox mode. For
context I am (preferably) using Qt 5.8 running on macOS 10.11.6.
The crux seems to be QtWebEngineProcess.app refuses to run after I codesign
the bundle.
