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 [email protected] http://lists.qt-project.org/mailman/listinfo/development
