Re: [Development] Getting QtWebEngineProcess.app to run in sandbox after being signed

> Could you please describe what's the procedure for getting the private API usage list from the MAS? Unfortunately I do not know that there is one. I found these API calls only because when they rejected my app, they sent me a list of the API calls that they wouldn't allow to be used. I will

Re: [Development] Getting QtWebEngineProcess.app to run in sandbox after being signed

I took a look at the patches, and I think it should be safe-ish to apply them. That is only the case because the Bootstrap Sandbox which uses the private XPC API is not actually used at the moment in Qt WebEngine. The other private API patches listed there are either not relevant to WebEngine,

Re: [Development] Getting QtWebEngineProcess.app to run in sandbox after being signed

I just meant are the changes to QtWebEngine you suggested stable enough for "production". But if it's still using private API, then I guess there's no point in trying to submit it to MAS. Damn. On Mon, May 8, 2017 at 11:32 AM, Alexandru Croitor wrote: > > On 08 May

Re: [Development] Getting QtWebEngineProcess.app to run in sandbox after being signed

On 08 May 2017, at 17:22, Adalid Claure > wrote: I changed the string like you suggested and it worked! Of course, I know this is very hack'ish. How stable do you think this is? I wouldn't know because this is the first time I tried doing it, and

Re: [Development] Getting QtWebEngineProcess.app to run in sandbox after being signed

On 08 May 2017, at 13:33, Adalid Claure > wrote: > Well, to be fair, it seems you haven't heeded my advice, and are going with > the approach of sandboxing the > whole application, instead of leaving that to be done by Chromium. Hmm.. I'm not sure

Re: [Development] Getting QtWebEngineProcess.app to run in sandbox after being signed

> Well, to be fair, it seems you haven't heeded my advice, and are going with the approach of sandboxing the > whole application, instead of leaving that to be done by Chromium. Hmm.. I'm not sure what you mean. How exactly should I be signing my app then? Per the MAS, I have to sign it my app

Re: [Development] Getting QtWebEngineProcess.app to run in sandbox after being signed

Hi, Well, to be fair, it seems you haven't heeded my advice, and are going with the approach of sandboxing the whole application, instead of leaving that to be done by Chromium. Regarding the issues you are seeing now, it is because of the "com.apple.security.application-groups" entitlement

Re: [Development] Getting QtWebEngineProcess.app to run in sandbox after being signed

Hi, I'm actually looking into this at the moment, as per the created issue here QTBUG-60443 I haven't completely finished my investigation, which I will post to the bug report. But the gist of it is: - the WebEngine / Chromium sub process calls manually sandbox_init, which is the macOS

Re: [Development] Getting QtWebEngineProcess.app to run in sandbox after being signed

Yeah, I saw that thread and unfortunately the suggestions there didn't help me. I attached a simple app and some other files to this bug I logged: https://bugreports.qt.io/browse/QTBUG-60443 Thanks for your reply! On Thu, May 4, 2017 at 8:45 AM, Morten Sørvig wrote: > Hi,

Re: [Development] Getting QtWebEngineProcess.app to run in sandbox after being signed

Hi, Not sure if I can be of much help, but: - This thread discusses and solves a similar problem: https://forum.qt.io/topic/49250/solved-qtwebengineprocess-not-working-in-sandboxed-application - If this could be reduced to a simple sandboxed-app-with-helper-process test case (no QtWebEngine

[Development] Getting QtWebEngineProcess.app to run in sandbox after being signed

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