Why do rapid clicks on button calls click event multiple times in .Net MAUI?

I am Navigating to a new page in the application using the following line of code:

  await Shell.Current.Navigation.PushAsync(new MyAccountsTabbedPage(_accountsViewModel, tcode, _supportPageViewModel, _contactusPageViewModel, _faqCategoryPageViewModel));

Navigation on button clicks causes multiple pages to open all at once if the button is pressed rapidly multiple times, resulting in poor user experience.

We can avoid it by applying the following check on Navigation stack before navigating to the particular page:

if (Shell.Current.Navigation.NavigationStack.Count == 0 || Shell.Current.Navigation.NavigationStack.Last().GetType() != typeof(MyAccountsTabbedPage))
            await Shell.Current.Navigation.PushAsync(new MyAccountsTabbedPage(_accountsViewModel, tcode, _supportPageViewModel, _contactusPageViewModel, _faqCategoryPageViewModel));

OR, by using logic on isEnabled in button (doesn't sound to be a good approach).

Refer to the following code on button click:

private async void ViewStatements_Clicked(object sender, EventArgs e) {
  var button = (Button) sender;
  _accountsViewModel.SelectedLease = (LeaseInfo) button.CommandParameter;
  string tcode = _accountsViewModel.SelectedLease.TenantCode;
  await _accountsViewModel.IsServiceChargeVisible(tcode);
  if (Shell.Current.Navigation.NavigationStack.Count == 0 || Shell.Current.Navigation.NavigationStack.Last().GetType() != typeof (MyAccountsTabbedPage))
    await Shell.Current.Navigation.PushAsync(new MyAccountsTabbedPage(_accountsViewModel, tcode, _supportPageViewModel, _contactusPageViewModel, _faqCategoryPageViewModel));

}

This doesn't seem to be a good approach, is there a better way of doing this or a better approach to do navigation to avoid it?

In case, the user presses the button multiple times to navigate to a certain screen, the behavior should be same as single click.

You're probably experiencing this issue because you're awaiting code between the event raised by the button click and the PushAsync instruction. This results in a delay navigating to the new page.

You could call this line

  await _accountsViewModel.IsServiceChargeVisible(tcode);

somewhere else (maybe in the initialization of MyAccountsTabbedPage?).

Otherwise, if you need to call it exactly when you press the button, you could use isEnabled as you suggested (it's not necessarily a bad practice) and show an ActivityIndicator.