Will an await in an OnAppearing mean the screen I am navigating to will show up immediately?

user_1422604 0
Viewed 1521

If I have this code:

    protected override async void OnAppearing()
    {
        base.OnAppearing();
        await DoLengthDatabaseTaskAsync(); // takes 30 seconds
    }

Will the fact that it is an Async task mean that the screen appears quickly and does not wait on the database task to complete?

    protected override async void OnAppearing()
    {
        base.OnAppearing();
        await CallAndForgetAboutOutputTaskAsync(); // takes 30 seconds
    }

How about if I am not concerned "call and forget" about the completion of the CallAndForgetAboutOutputTaskAsync() method.

Is there a way I can run CallAndForgetAboutOutputTaskAsync() in the background so the screen appears as soon as possible

xamarin.forms xamarin
3 Answers

Yes and no.

OnAppearing means that the page has appeared on the screen and it performs immediately after that. So executing something there won't slow down anything.

However you should keep in mind that OnAppearing is executing on the UI thread and depending on the structure of your CallAndForgetAboutOutputTaskAsync() it may freeze your UI, but simple magic of Task.Run resolves the problem.

EDIT: So it should be like:

Task CallAndForget()
{
  return Task.Run(async() => await action());
}
user_2021790

No.

OnAppearing happens

"immediately prior to the Page becoming visible."

The purpose of async/await is to allow UI-accessing code to be written in a linear fashion - each line must complete before the next line executes - WITHOUT blocking UI. That is, UI events still occur - between each await.

However, the async method (here, OnAppearing), won't return until all of its lines of code have executed.

That means the page won't display until after all the work is done.

The compiler turns the method into a sequence of tasks with continuations.

IMPORTANT CAVEAT:

It is still necessary for each awaited method ("DoLengthDatabaseTaskAsync") to be well-written with async/await as needed. Each of those methods is executed on the UI thread.

If that method goes a long time without itself having awaits, it will block UI during that time.

async/await does this for you:

  1. Allows you to write code that is still executing on the UI thread, so you can access UI elements without cross-threading issues.
  2. Allows UI events to occur BETWEEN each await line.
  3. If the awaited method is also async/await, allows UI events to occur between each of its internal await lines.

That's all async/await does. It doesn't magically eliminate all UI blocking.

And it isn't always a substitute for Task.Run. If you need to do a lengthy operation that doesn't access UI elements, use Task.Run. That runs code on a background thread, so you don't have to be concerned with lengthy operations that lack awaits.

Ivan's answer is one approach. Though the explanation given there is partly wrong.

However there is a simpler answer, given that you have a "fire and forget" situation, where you don't need an answer back:

protected override void OnAppearing()
{
    base.OnAppearing();
    Task.Run(CallAndForgetAboutOutputTaskAsync);
}

Code inside Task.Run is sent to a background thread. The Run immediately returns to the calling method.

Note that I've removed async from OnAppearing declaration. In this simple case, there is no use of await, and there is very little time spent on the ui thread, so there is no need for async (which generates a bit of extra code/overhead).

user_1993640

Using an await frees up the UI Thread by returning execution to the calling method. This in theory will allow the UI to keep functioning while CallAndForgetAboutOutputTaskAsync() does its thing. There is no need for Task.Run() in this instance.

user_114828340
Related