-
-
Notifications
You must be signed in to change notification settings - Fork 132
Callbacks not called due to garbage collection #190
Comments
Solved using
That's strange |
I can clearly see correct messages from and to websocket, but callbacks never called, what the heck |
|
@rostopira I am actually started working on getting this project up to speed from many previous unreleased commits. I experienced the same thing you did and it caused me hours of trial and error and I could only get the delegate sorry "Subscription Handling" protocol to work. Where did you find weak var? Thats doesn't makes much sense when you're dealing with asynchronous tasks that passes a closure expression. Nothing during this process has any business being declared weak. |
@noobs2ninjas See this commit in my fork: rostopira@2473020 And |
@noobs2ninjas also, weak could make sense, if it were properly documented and actually cancels subscription, but it's not the case |
Even with documentation the place where it completely falls apart every time is when accessing the client via singleton as you can simply pass in closures eliminating the need to make a reference to anything. |
@noobs2ninjas so, if you agree with me, just remove |
I do. Just pointing out that it probably should be removed either way. Would you mind updating this issues title and doing a commit from your branch to resolve this issue? I'm looking to do a release soon and would love to get this in there and give you credit for the fix. |
NP, I will do |
I've installed this via CocoaPods, but build fails with following error:
P.S.: I use Xcode 10.2
The text was updated successfully, but these errors were encountered: