Closed davidkessler-ch closed 9 months ago
@nuclearace
Fixed this by removing the weak self capture in the timingOut
function. Not sure why self is lost, but retain cycles are not a problem since they are only temporary anyways with asyncAfter(...) { }
Anyways, I could create a pull request for this.
We are using
socket.emitWithAck
and the server has not yet implemented the ack functionality for this event. However, the callback never gets called, i.e. the timingOut never actually times out, independent of the provided duration.Shouldn't the timeout be called completely independently of if the server even gets an event with that name, let alone bothers about sending an ack?
Interestingly, this still gets logged:
LOG OnAckCallback: OnAckCallback for 0 being released
I should also mention: sometimes the app just completely crashed with BAD_ACCESS error at some line that had something to do with acks.. unfortunately I don't remember the exact error / line and neither is it currently happening.. it just sort of "went away" without changing anything.
(using version 16.1.0)
logs: