How to properly manage AntSDK WebSocket connections in Flutter when navigating away from a page

[kimPongsakorn]

How to properly manage AntSDK WebSocket connections in Flutter when navigating away from a page

Issue
I'm developing a Flutter app using AntSDK and encountering an issue with WebSocket connection management:

1. When I initiate an AntSDK connection on a page and navigate away before the WebSocket connection completes
2. The AntSDK continues attempting to connect in the background
3. When the connection eventually completes, the Ant audio gets stuck in the app
4. If I return to the original page, there's an audio overlap issue, as if both old and new Ant instances are running simultaneously

What I need:

• Terminate the WebSocket connection when navigating away from the page

• Completely clear the Ant instance when not in use

• Stop all AntSDK-related processes when not on that page
  What I've tried
  dart

  @OverRide
  void dispose() {
  // I've tried using the standard dispose method but it doesn't solve the issue
  super.dispose();
  }

Questions

1. What is the correct way to disconnect AntSDK and stop all processes when navigating away from a page?
2. Is there a specific method needed to directly close the WebSocket connection?
3. Are there any best practices for managing the lifecycle of AntSDK in a Flutter app?

Thank you!

[burak-58]

I have converted to a discussion to get answers for your questions.

[USAMAWIZARD]

Hi,
Can you please try to do something like below and let me know if that works for you.

@OverRide
void dispose() {
AntMediaFlutter.anthelper?.close();
​}

[kimPongsakorn]

Thank you for the suggestion, but I'm still encountering the issue. I've implemented the solution you provided:

dart
@Override 
void dispose() {
  AntMediaFlutter.anthelper?.close();
  super.dispose();
}

However, the problem persists specifically when:

1. The user has a slow network connection
2. The WebSocket is in the process of connecting
3. The user navigates away from the page (widget is disposed)

In this scenario, it seems the WebSocket connection continues in the background even after the widget is disposed. When the connection eventually completes, it causes audio conflicts when returning to the page.

[kimPongsakorn]

Thank you for the suggestion, but I'm still encountering the issue. I've implemented the solution you provided:

@Override 
void dispose() {
  AntMediaFlutter.anthelper?.close();
  super.dispose();
}

However, the problem persists specifically when:

1. The user has a slow network connection
2. The WebSocket is in the process of connecting
3. The user navigates away from the page (widget is disposed)

In this scenario, it seems the WebSocket connection continues in the background even after the widget is disposed. When the connection eventually completes, it causes audio conflicts when returning to the page.

Is there a more specific method to terminate the WebSocket connection while it's still in the "connecting" state? Perhaps something like:

@Override
void dispose() {
  // Force terminate any pending WebSocket connections?
  AntMediaFlutter.anthelper?.forceDisconnect(); // Does something like this exist?
  AntMediaFlutter.anthelper?.close();
  super.dispose();
}

Or should I be managing this differently, perhaps by using a singleton approach with better state management?

[USAMAWIZARD]

@kimPongsakorn here is my suggestions ,
connect weboscket in a separate thread , when disposed is called check if websocket is already connected , if its connected call close function if its not forcefully stop the thread