Hi friends, here we are again, my first blog post in 2020. Today we will talk about how to navigate to a page and wait results. This can be really useful by making our code easier to read, as compared to using Xamarin Forms’ Messaging Center each time a page needs to send back results to its caller.

The Problem

In Xamarin Forms, you can navigate asynchronously to a page or a modal. With the Xamarin Forms Shell, you can perform URL navigation and even pass parameters to the page or the page’s View Model. But once you navigate to this page or modal and it completes the processing for which it ways called. How do you return directly a result to the underlying layer which called the page ?. As of when I’m writing this post to my knowledge, the most common way to receive a result back from a page which just disappeared is by using Xamarin Forms’ Messaging Center. Though the messaging center works well, The code you write to register to various events might be hard to read.

Simple Solution

To resolve this, we will just leverage one of C#’s awesome features Tasks. Bellow, we will implement a simple navigation service. This service will wait for the page’s OnDisappearing method to be called. Then return a result gotten from the data input by the user on that page. This sample is done with MVVM pattern, but for simplicity, you will find code behind the view. So, how to we navigate to a page and wait results in Xamarin Forms.

You can download the source code here.

If you like this post, don’t hesitate to follow me on Twitter or Github and subscribe to this page’s notifications to stay updated with new articles or like my page on Facebook.

First, we create a base page with a generic type <T>. Which contains the event fired when the page disappears. This event is made of an action delegate which has as parameter the datatype T.

NB: I chose to make the page responsible of returning the data and calling the event because of simplicity. You could implement this in your View Model to make your app abide more to the MVVM design pattern.

Every page which will have to navigate to and wait results, should implement this base page.

Now in the navigation service, we create an instance of the page we want to display. Subscribe to its “PageDisapearing” event. And use the “TaskCompletionSource” to wait for the page to finish what it was called for.

Using Our Navigation Service

Now, here is how you should use this service. Below, we call the create items page which will allow the user to create an item and return the new item when creation completes.


Above, you have a complete solution that permits you to navigate to a page and wait results. You can leverage this to make your Xamarin Forms code more readable. Note that, this way of using the TaskCompletionSource can be leveraged in several other scenarios. Specifically scenarios where you want your code to wait for a certain work (which does not depend on your code) to complete and return before continuing your code execution.

Follow me on social media and stay updated


  1. mister_giga


    Once it was not guaranteed that OnDissapearing would get called all the time. Also it will get called when mavigating deeper on other pages.

    • Khalil Yamoun


      To avoid loosing events/actions while navigating deeper, just add the test, do so:

      if (Navigation.NavigationStack.LastOrDefault() == this)
      if (PageDisapearing != null)
      foreach (var @delegate in PageDisapearing.GetInvocationList())
      PageDisapearing -= @delegate as Action;

  2. Reply

    For now in 2021, isn’t it state of the art to use the shell navigation instead? Why or why not? Any pros/cons? TY

    • Damien Doumer


      It is good practice to use shell navigation, but
      the technique I described above is the one I use for modal navigation, where I need a result after navigation is complete. And you can apply it in Shell or standard Xamarin.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.