DisconnectHandler is never called
See original GitHub issueDescription
I created a Custom Control that inherits from ElementHandler and at the moment that the control is closed the DisconnectHandler method isn’t called, even if I set the VirtualView.Handler to null.
Steps to Reproduce
- Add breakpoints here
- Start the sample app
- Scroll to the bottom and press the button
- See the popup
- Click outside the popup to close it
- The
DisconnectHandlerisn’t called
Version with bug
Preview 10 (current)
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
Android 11
Did you find any workaround?
No
Relevant log output
No response
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:16 (11 by maintainers)
Top Results From Across the Web
Why is my disconnect() handler not getting fired in SignalR ...
I'm trying to hook some call backs in the client and they don't seem to be getting fired. I'd really like to get...
Read more >Disconnect handler not running
The disconnect handler appears to be ran only when a disconnect component is explicitly called. That is if the call ends execution on...
Read more >Disconnect handler does not work when turning on ...
But when I go into airplane mode, my disconnect handler is never called and the user still appears online. After reestablishing the connection, ......
Read more >Understanding and Handling Connection Lifetime Events ...
This article provides an overview of the SignalR connection, reconnection, and disconnection events that you can handle, and timeout and ...
Read more >Voice JS SDK v1: Twilio.Connection
Connection object represents a call to or from Twilio. You never instantiate it directly, but it's passed to event handlers and returned when...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Thats really surprising : counterintuitive. Isnt that the whole point of connect/disconnect, that I want my resources cleaned up at that point? I dont put anything in those blocks if I dont want that. Especially because ConnectHandler is where you attach touch handlers etc as far as Im aware, I think its a recipe for surprising behavior and memory leaking.
@pictos yea this is definitely going to become a thing 😃
An issue and some design docs around current recommendations will definitely be in order.