Shell: how to wait for initial content from async method on app start.

[SergTomcat]

I have dynamic content based on user settings and it is retrieved from SQLite DB asyncroniously. I need to set at least one ShellContent item inside shell on creation, and shell itself is created at CreateWindow method of Application.

Question is: how can I stall CreateWindow until I get all asyncronous info?

Here is some example (it's not a real code, it's just to get the idea of what is needed):

public partial class App : Application
{
	Task<MySettings> tSettings;

	public App(IServiceProvider serviceProvider)
	{
		//get data for shell content, need wait for it before App is created ideally
		tSettings = Task.Run( MyDatabaseService.InitializeSettingsAsync ); 

		InitializeComponent();	        
	}
	
	protected override Window CreateWindow(IActivationState? activationState)
       {
                var myShell = new MyShell();

                //! wait for settings to be ready!
                var settings = tSettings.GetAwaiter().GetResult(); //??? deadlock and bad code
                
                myShell.Items.Add(new ShellContent() { Content = settings.HomePage, Route = "home" });
                                
	        return myShell;
		
	}		
}

What is the possible solution or best practice? Because for now I have to insert "dummy page" in Shell constructor that mimic splash screen, while waiting for results. I would like it all happen behind initial loading splash screen.

Any help is appreciated. Thank you in advance.

[asi-evin]

I don't think we have control over when create window gets called. Creating a dummy page isn't terrible, no different than creating a login page that gets skipped if you're already logged in. You're probably looking at two scenarios you need to handle here:

1. Database loads first: In which case, create your shell as normal.
2. Window created first: In which case, create shell with loading page. When the database load is finished, populate your shell content and remove the loading page.

[SergTomcat]

That is what I'm doing at the moment. I was just hopeful it could be hidden behind splash screen. Thank you for clarification.

[asi-evin]

Well there are ways to do that on the native code side BUT you'll run into problems especially on iOS; if you take too long, it crashes.