Flutter: Bloc dispose without waiting for the server response












1















As soon as the user enters in a page, a call to the server will be executed. If the snapshot has data, a stream will be send to the UI with which will create a ListView, otherwise, if the snapshot has an error, a stream error message will be sinked.



So, the call I have:



try {
List answer = await call();
createList.sink.add(answer);
} on Exception catch (e) {
createList.sink.addError(e);
}


The problem is: if the connection is slow, and the user quits that page before the call is completed, the controllers will be disposed and the app will complain that the error cannot be sinked after that I've disposed the controller.
So, is there a way to "abort" the call to the server when the user quits the page?










share|improve this question



























    1















    As soon as the user enters in a page, a call to the server will be executed. If the snapshot has data, a stream will be send to the UI with which will create a ListView, otherwise, if the snapshot has an error, a stream error message will be sinked.



    So, the call I have:



    try {
    List answer = await call();
    createList.sink.add(answer);
    } on Exception catch (e) {
    createList.sink.addError(e);
    }


    The problem is: if the connection is slow, and the user quits that page before the call is completed, the controllers will be disposed and the app will complain that the error cannot be sinked after that I've disposed the controller.
    So, is there a way to "abort" the call to the server when the user quits the page?










    share|improve this question

























      1












      1








      1








      As soon as the user enters in a page, a call to the server will be executed. If the snapshot has data, a stream will be send to the UI with which will create a ListView, otherwise, if the snapshot has an error, a stream error message will be sinked.



      So, the call I have:



      try {
      List answer = await call();
      createList.sink.add(answer);
      } on Exception catch (e) {
      createList.sink.addError(e);
      }


      The problem is: if the connection is slow, and the user quits that page before the call is completed, the controllers will be disposed and the app will complain that the error cannot be sinked after that I've disposed the controller.
      So, is there a way to "abort" the call to the server when the user quits the page?










      share|improve this question














      As soon as the user enters in a page, a call to the server will be executed. If the snapshot has data, a stream will be send to the UI with which will create a ListView, otherwise, if the snapshot has an error, a stream error message will be sinked.



      So, the call I have:



      try {
      List answer = await call();
      createList.sink.add(answer);
      } on Exception catch (e) {
      createList.sink.addError(e);
      }


      The problem is: if the connection is slow, and the user quits that page before the call is completed, the controllers will be disposed and the app will complain that the error cannot be sinked after that I've disposed the controller.
      So, is there a way to "abort" the call to the server when the user quits the page?







      server dart flutter call bloc






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 1 at 19:15









      Little MonkeyLittle Monkey

      18912




      18912
























          1 Answer
          1






          active

          oldest

          votes


















          1














          Using the controller's isClosed property, you could just check if the controller is closed before adding the events, like so:



          try {
          List answer = await call();
          if (!createList.isClosed) {
          createList.sink.add(answer);
          }
          } on Exception catch(e) {
          if (!createList.isClosed) {
          createList.sink.addError(e);
          }
          }





          share|improve this answer


























          • I think you put a "sink" more. I just do "!createList.isClosed"

            – Little Monkey
            Jan 6 at 17:05











          • Of course, you're right. I fixed the code now.

            – Marcel
            Jan 6 at 22:57











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53998240%2fflutter-bloc-dispose-without-waiting-for-the-server-response%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          Using the controller's isClosed property, you could just check if the controller is closed before adding the events, like so:



          try {
          List answer = await call();
          if (!createList.isClosed) {
          createList.sink.add(answer);
          }
          } on Exception catch(e) {
          if (!createList.isClosed) {
          createList.sink.addError(e);
          }
          }





          share|improve this answer


























          • I think you put a "sink" more. I just do "!createList.isClosed"

            – Little Monkey
            Jan 6 at 17:05











          • Of course, you're right. I fixed the code now.

            – Marcel
            Jan 6 at 22:57
















          1














          Using the controller's isClosed property, you could just check if the controller is closed before adding the events, like so:



          try {
          List answer = await call();
          if (!createList.isClosed) {
          createList.sink.add(answer);
          }
          } on Exception catch(e) {
          if (!createList.isClosed) {
          createList.sink.addError(e);
          }
          }





          share|improve this answer


























          • I think you put a "sink" more. I just do "!createList.isClosed"

            – Little Monkey
            Jan 6 at 17:05











          • Of course, you're right. I fixed the code now.

            – Marcel
            Jan 6 at 22:57














          1












          1








          1







          Using the controller's isClosed property, you could just check if the controller is closed before adding the events, like so:



          try {
          List answer = await call();
          if (!createList.isClosed) {
          createList.sink.add(answer);
          }
          } on Exception catch(e) {
          if (!createList.isClosed) {
          createList.sink.addError(e);
          }
          }





          share|improve this answer















          Using the controller's isClosed property, you could just check if the controller is closed before adding the events, like so:



          try {
          List answer = await call();
          if (!createList.isClosed) {
          createList.sink.add(answer);
          }
          } on Exception catch(e) {
          if (!createList.isClosed) {
          createList.sink.addError(e);
          }
          }






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jan 6 at 22:57

























          answered Jan 2 at 22:39









          MarcelMarcel

          978515




          978515













          • I think you put a "sink" more. I just do "!createList.isClosed"

            – Little Monkey
            Jan 6 at 17:05











          • Of course, you're right. I fixed the code now.

            – Marcel
            Jan 6 at 22:57



















          • I think you put a "sink" more. I just do "!createList.isClosed"

            – Little Monkey
            Jan 6 at 17:05











          • Of course, you're right. I fixed the code now.

            – Marcel
            Jan 6 at 22:57

















          I think you put a "sink" more. I just do "!createList.isClosed"

          – Little Monkey
          Jan 6 at 17:05





          I think you put a "sink" more. I just do "!createList.isClosed"

          – Little Monkey
          Jan 6 at 17:05













          Of course, you're right. I fixed the code now.

          – Marcel
          Jan 6 at 22:57





          Of course, you're right. I fixed the code now.

          – Marcel
          Jan 6 at 22:57




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53998240%2fflutter-bloc-dispose-without-waiting-for-the-server-response%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Monofisismo

          Angular Downloading a file using contenturl with Basic Authentication

          Olmecas