You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi I experience some problems with [self.connection cancel] in the dealloc method. I have a feeling it sometimes also cancel other ongoing request in the queue. Is this possible ? I have experimented both with and without FSN_QUEUED_CONNECTIONS.
- (void)dealloc {
NSAssert(!self.connection, @"non-nil connection: %@", self.connection);
#if TARGET_OS_IPHONE
// if this task was set to run in background then the expiration handler should be retaining self
NSAssert1(self.taskIdentifier == UIBackgroundTaskInvalid,
@"deallocated request has background task identifier: %@", self);
#endif
[self clearBlocks]; // not cleanup; assert no taskIdentifer above instead
// just to be safe in production
FSNVerbose(@"%p: dealloc", self);
[self.connection cancel];
}
The text was updated successfully, but these errors were encountered:
Hi I experience some problems with
[self.connection cancel]
in thedealloc
method. I have a feeling it sometimes also cancel other ongoing request in the queue. Is this possible ? I have experimented both with and without FSN_QUEUED_CONNECTIONS.The text was updated successfully, but these errors were encountered: