Re: [Development] Mac app built with Qt5.3.0 RC got rejected by Mac App Store because of non-public API calls.
Unfortunately the workaround described here https://bugreports.qt-project.org/browse/QTBUG-31419 did not work with Qt5.3.0RC. I could not get it compiled after the patch. I have to use Qt5.3 because it fixed a serious sandbox bug. Is there any way to completely disable usage of QML/QtQuick/Webkit2 stuff? My mac app only uses QWebView in pure C++. If that's possible I think I would be all set. Thanks, Ping___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Mac app built with Qt5.3.0 RC got rejected by Mac App Store because of non-public API calls.
Regard QtWebkit on iOS: Source http://qt-project.org/qt5/qt52#ios Qt WebKit is also not supported under Qt for iOS and because of App Store policies, it will not be supported either. For now, you need to use the native WebKit in iOS. This can be done by using the native Objective-C libraries, which is possible with the iOS compiler, clang.” So even in the case of QtWebEngine its unlikely that we will ever be able to support iOS. Even in the case of the Chrome browser app on iOS they are using the native web view instead of their own WebEngine to comply with the same App Store policies. Regards, Andy Nichols On 15 May 2014, at 02:48, Thiago Macieira thiago.macie...@intel.commailto:thiago.macie...@intel.com wrote: Em qua 14 maio 2014, às 16:39:15, P Bai escreveu: As to the first two issues, from what I read online, it is because of QtWebkit, which I have to use in my app. Is there any hope we could get these fixed? Correct, all of them come from QtWebKit. Anyway, there's no plan on further updating QtWebKit from upstream because upstream WebKit is no longer cross-platform. I have no clue about the bootstrap symbols, but all of the ICU symbols are documented to be stable in icu-project.orghttp://icu-project.org and have been for some time. -- Thiago Macieira - thiago.macieira (AT) intel.comhttp://intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.orgmailto:Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Mac app built with Qt5.3.0 RC got rejected by Mac App Store because of non-public API calls.
Hello, As to the first two issues, from what I read online, it is because of QtWebkit, which I have to use in my app. Is there any hope we could get these fixed? Correct, all of them come from QtWebKit. Anyway, there's no plan on further updating QtWebKit from upstream because upstream WebKit is no longer cross-platform. I have no clue about the bootstrap symbols [...] Unfortunately, even an update from upstream QtWebKit won't help here, as Apple's WebKit version also uses the private bootstrap APIs as it seems that not even Apple has an adequate replacement for them yet - the problem is not that big for Apple as it is for us since Apple's WebKit is a system component on OS X and the restrictions of the Mac App Store do not apply of course. If your application does not need WebKit, I would recommend skipping it entirely. If you need it, there are some workarounds for this issue described in https://bugreports.qt-project.org/browse/QTBUG-31419 . Please not that these workarounds will factually disable the QML API for WebKit2 and only the QtWebKit widgets API can be used. Best regards, Michael ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Mac app built with Qt5.3.0 RC got rejected by Mac App Store because of non-public API calls.
Hi All, My mac app just got rejected by the Mac App Store for the following reasons: The use of non-public APIs can lead to a poor user experience should these APIs change in the future, and is therefore not permitted. The following non-public APIs are included in your application: '/usr/lib/libSystem.B.dylib' : bootstrap_look_up2 : bootstrap_register2 '/usr/lib/libicucore.A.dylib' : ubrk_getRuleStatus : ubrk_setUText : ucnv_getCanonicalName : ucnv_reset '/usr/lib/libiodbc.2.dylib' : SQLAllocHandle : SQLBindParameter : SQLCloseCursor : SQLColAttributeW : SQLColumnsW : SQLDescribeColW : SQLDisconnect : SQLDriverConnectW : SQLEndTran : SQLExecDirectW : SQLExecute : SQLFetch : SQLFetchScroll : SQLFreeHandle : SQLGetData : SQLGetDiagRecW : SQLGetFunctions : SQLGetInfoW : SQLGetStmtAttrW : SQLGetTypeInfoW : SQLMoreResults : SQLNumResultCols : SQLPrepareW : SQLPrimaryKeysW : SQLRowCount : SQLSetConnectAttrW : SQLSetEnvAttr : SQLSetStmtAttrW : SQLSpecialColumnsW : SQLTablesW -- First of all, my app doesn't even use SQL, why are those APIs being called? As to the first two issues, from what I read online, it is because of QtWebkit, which I have to use in my app. Is there any hope we could get these fixed? Thank you! Ping ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Mac app built with Qt5.3.0 RC got rejected by Mac App Store because of non-public API calls.
On 2014-05-14, at 07:39 PM, P Bai ap...@yahoo.com wrote: Hi All, My mac app just got rejected by the Mac App Store for the following reasons: The use of non-public APIs can lead to a poor user experience should these APIs change in the future, and is therefore not permitted. The following non-public APIs are included in your application: '/usr/lib/libSystem.B.dylib' : bootstrap_look_up2 : bootstrap_register2 '/usr/lib/libicucore.A.dylib' : ubrk_getRuleStatus : ubrk_setUText : ucnv_getCanonicalName : ucnv_reset '/usr/lib/libiodbc.2.dylib' : SQLAllocHandle : SQLBindParameter : SQLCloseCursor : SQLColAttributeW : SQLColumnsW : SQLDescribeColW : SQLDisconnect : SQLDriverConnectW : SQLEndTran : SQLExecDirectW : SQLExecute : SQLFetch : SQLFetchScroll : SQLFreeHandle : SQLGetData : SQLGetDiagRecW : SQLGetFunctions : SQLGetInfoW : SQLGetStmtAttrW : SQLGetTypeInfoW : SQLMoreResults : SQLNumResultCols : SQLPrepareW : SQLPrimaryKeysW : SQLRowCount : SQLSetConnectAttrW : SQLSetEnvAttr : SQLSetStmtAttrW : SQLSpecialColumnsW : SQLTablesW -- First of all, my app doesn't even use SQL, why are those APIs being called? As to the first two issues, from what I read online, it is because of QtWebkit, which I have to use in my app. Is there any hope we could get these fixed? Thank you! Ping ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development The ODBC APIs are probably from the Qt ODBC SQL plugin. Simply don't deploy it with your app and it should resolve that issue. Not sure about the rest. -- Jake Petroules - jake.petroules at petroules.com Chief Technology Officer - Petroules Corporation ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Mac app built with Qt5.3.0 RC got rejected by Mac App Store because of non-public API calls.
Em qua 14 maio 2014, às 16:39:15, P Bai escreveu: As to the first two issues, from what I read online, it is because of QtWebkit, which I have to use in my app. Is there any hope we could get these fixed? Correct, all of them come from QtWebKit. Anyway, there's no plan on further updating QtWebKit from upstream because upstream WebKit is no longer cross-platform. I have no clue about the bootstrap symbols, but all of the ICU symbols are documented to be stable in icu-project.org and have been for some time. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Mac app built with Qt5.3.0 RC got rejected by Mac App Store because of non-public API calls.
BTW, when will QtWebkit be replaced? On Thu, May 15, 2014 at 8:48 AM, Thiago Macieira thiago.macie...@intel.comwrote: Em qua 14 maio 2014, às 16:39:15, P Bai escreveu: As to the first two issues, from what I read online, it is because of QtWebkit, which I have to use in my app. Is there any hope we could get these fixed? Correct, all of them come from QtWebKit. Anyway, there's no plan on further updating QtWebKit from upstream because upstream WebKit is no longer cross-platform. I have no clue about the bootstrap symbols, but all of the ICU symbols are documented to be stable in icu-project.org and have been for some time. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development -- Regards, Fan Yang ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Mac app built with Qt5.3.0 RC got rejected by Mac App Store because of non-public API calls.
Em qui 15 maio 2014, às 09:18:31, Yang Fan escreveu: BTW, when will QtWebkit be replaced? From yesterday: http://blog.qt.digia.com/blog/2014/05/13/news-from-the-qt-webengine-team/ -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
