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
