how to end a stream task

[JoergTiedemann]

Hi
just a simple question.
I start a realtime database stream as in your example asyn/callback/stream/stream.ino

// Since v1.2.1, in SSE mode (HTTP Streaming) task, you can filter the Stream events by using RealtimeDatabase::setSSEFilters(<keywords>),
    // which the <keywords> is the comma separated events.
    // The event keywords supported are:
    // get - To allow the http get response (first put event since stream connected).
    // put - To allow the put event.
    // patch - To allow the patch event.
    // keep-alive - To allow the keep-alive event.
    // cancel - To allow the cancel event.
    // auth_revoked - To allow the auth_revoked event.
    // To clear all prevousely set filter to allow all Stream events, use RealtimeDatabase::setSSEFilters().
    Database.setSSEFilters("get,put,patch,keep-alive,cancel,auth_revoked");

    // The "unauthenticate" error can be occurred in this case because we don't wait
    // the app to be authenticated before connecting the stream.
    // This is ok as stream task will be reconnected automatically when the app is authenticated.
    Database.get(aClient, "/test/stream", asyncCB, true /* SSE mode (HTTP Streaming) */, "streamTask");

It works as expected. But what I have to do to stop the stream task ?
In the old library i could use Firebase.endstream an Firebase.removeStream

How can I stop or kill the stream task ?
I can stop it if I call
aClient.stopAsync("streamTask");
But after that I'm not able to start the stream again by calling

  Database.setSSEFilters("get,put,patch,keep-alive,cancel,auth_revoked");
  Database.get(aClient, streamPath, streamCallback, true /* SSE mode (HTTP Streaming) */, "streamTask");

I want to stop and start a stream task depending on internal status of my application to reduce memory consumption in some cases

[mobizt]

https://github.com/mobizt/FirebaseClient/blob/main/FAQ.md

[mobizt]

https://github.com/mobizt/FirebaseClient?tab=readme-ov-file#async-client

[mobizt]

Ok, I found the bug in task removal.

After you stopped the stream task, if you call aClient.taskCount() on the next iteration of loop(), it will return non-zero value which means stream task is still running.

[mobizt]

I will fix this which you can stop and restart the stream as usual as stated in the FAQ and documentation.

[JoergTiedemann]

Sounds good, thanks for your help

[mobizt]

Now this issue was fixed in v1.4.0, please update.