[Interest] QNetworkReply: After abort() Signal finished() Not Called on iOS Targets

Robert Iakobashvili coroberti at gmail.com
Tue Mar 17 08:33:40 CET 2015


Gentlemen,
The doc for 5.4 QNetworkReply::abort() says that it:

"Aborts the operation immediately and close down any network
connections still open. Uploads still in progress are also aborted.
The finished() signal will also be emitted."


The doc 5.4 QNetworkAccessManager::finished(QNetworkReply * reply)
says that:

"This signal is emitted whenever a pending network reply is finished.
The reply parameter will contain a pointer to the reply that has just
finished. This signal is emitted in tandem with the
QNetworkReply::finished() signal."

In my derived QNetworkAccessManager
the signal connect done as:

connect(this, SIGNAL(finished(QNetworkReply*)),
SLOT(requestFinished(QNetworkReply*)));


After calling abort() on reply (application time expired), there's
signal finished() emitted and my requestFinished() slot being called
on Windows, Mac, Android, Linux,
but on iOS,
at least not at iPhone and iPad targets.

Questions:

Is this is a bug in docs (some intended platform-specific behavior)
or in the code or something is wrong in my usage?

Thank you.

Regards,
Robert



More information about the Interest mailing list