Temp fix for a crash faced by client using proxy connection #1493
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Probably closes #1437
Explanation:
ARTSRProxyConnect
object can potentially generate a proxy connection error even after initial success (or more than one error in a raw), which can depend on what proxy type is used, which will create a race condition:self->_proxyConnect = nil;
deallocatesARTSRProxyConnect
object on a_workQueue
, and a subsequent call to_failWithError:
on aio.ably.socketrocket.NetworkThread
insideARTSRProxyConnect
will cause crash when it'll try to accessself
.