Because the APIs are deprecated by Apple so they would have had to be removed/changed soon anyways, especially when an alternative (which is the default now) is already available. Also it caused build failure on tvOS/watchOS.
On Sep 13, 2016, at 11:25 AM, Thiago Macieira <[email protected]<mailto:[email protected]>> wrote: The changelog contains this entry: - [QTBUG-45031] The NSURLConnection backend of QNetworkAccessManager has been removed, since SecureTransport is the default SSL backend on iOS and is enabled by default. This means that building with -no-openssl -no-securetransport will no longer provide SSL capabilities on iOS. WTH? Why are we removing options in a patch release? What happened? Is the backend so severely broken that it needed to be removed? -- Thiago Macieira - thiago.macieira (AT) intel.com<http://intel.com> Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list [email protected]<mailto:[email protected]> http://lists.qt-project.org/mailman/listinfo/development -- Jake Petroules - [email protected]<mailto:[email protected]> Consulting Services Engineer - The Qt Company Qbs build tool evangelist - qbs.io<http://qbs.io>
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
