.NET MAUI MVVM Toolkit注册页Android线程异常问题求助

我们使用.NET MAUI和MVVM Community Toolkit开发跨平台账号注册页，为实现异步检查用户名是否已存在，给用户名输入框添加了UserStoppedTypingBehavior。相关XAML代码如下：

<StackLayout Orientation="Horizontal">
    <Image Source="{AppThemeBinding Light=user_icon.png, Dark=user_icon_dark.png}" Style="{StaticResource EntryIcon}" />
    <Entry x:Name="UserNameEntry" Text="{Binding Username}" Placeholder="User name"
           IsEnabled="{Binding IsBusy, Converter={helpers:InverseBoolConverter}}" Style="{StaticResource Default}">
        <Entry.Behaviors>
            <toolkit:UserStoppedTypingBehavior 
                Command="{Binding UsernameCheckCommand}"
                StoppedTypingTimeThreshold="500"
                MinimumLengthThreshold="5"/>
            <toolkit:TextValidationBehavior
                x:Name="UsernameValidator"
                Flags="ValidateOnValueChanged"
                MinimumLength="5" MaximumLength="20"
                IsValid="{Binding UsernameIsValid}"/>
        </Entry.Behaviors>
    </Entry>
</StackLayout>

ViewModel核心代码：

[ObservableProperty]
[NotifyCanExecuteChangedFor(nameof(RegisterCommand))]
private string _username;

[ObservableProperty]
private bool _usernameIsValid;

[NotifyCanExecuteChangedFor(nameof(RegisterCommand))]
[ObservableProperty]
private bool _accountExists = false;

[ObservableProperty]
private string _errorMessage;

private readonly Dictionary<ErrorTypes, string> Errors = [];

[RelayCommand]
private async Task UsernameCheck()
{
    AccountExists = false;
    if (UsernameIsValid)
    {
        Errors.Remove(ErrorTypes.AccountExists);
        var accountCheckResponse = await CheckAccountExists();
        if (accountCheckResponse.IsOK)
        {
            AccountExists = accountCheckResponse.Data;
            if (AccountExists)
            {
                Errors.Add(ErrorTypes.AccountExists, "This username is already taken, please try another.");
            }
        }
        else
        {
            Errors.Add(ErrorTypes.AccountExists, $"Opps, something went wrong. {accountCheckResponse.Message}.");
        }
    }
    UpdateErrorMessage();
}

private async Task<Response<bool>> CheckAccountExists()
{
    var response = new Response<bool>();
    try
    {
        response = await AccountService.CheckAccountExistsAsync(Username);
    }
    catch (Exception ex)
    {
        response.AddErrorMessage(ex.Message);
    }

    return response;
}

private void UpdateErrorMessage()
{
    ErrorMessage = string.Join(" ", Errors.Values.ToList());
}

注册命令相关代码：

private bool CheckCanRegister()
{
    UpdateErrorMessage();
    return !IsBusy && UsernameIsValid && !AccountExists && PasswordIsValid && Password == ConfirmPassword;
}

[RelayCommand(CanExecute = nameof(CheckCanRegister))]
public async Task Register()
{
    // 注册逻辑
}

AccountService内部所有异步调用均使用ConfigureAwait(false)。在Android模拟器运行时，部分输入场景会抛出异常：

Android.Util.AndroidRuntimeException: Only the original thread that created a view hierarchy can touch its views.
   ...
   at Microsoft.Maui.Controls.Button.Microsoft.Maui.Controls.Internals.ICommandElement.CanExecuteChanged(Object sender, EventArgs e)
   at CommunityToolkit.Mvvm.Input.AsyncRelayCommand.NotifyCanExecuteChanged()
   at RewardsApp.ViewModels.RegisterViewModel.set_AccountExists(Boolean value)
   at RewardsApp.ViewModels.RegisterViewModel.UsernameCheck()

异常核心是跨线程操作UI控件，具体逻辑链：

1. AccountService.CheckAccountExistsAsync用ConfigureAwait(false)，导致await后后续代码（设置AccountExists）运行在后台线程，而非UI线程。
2. AccountExists标记了[NotifyCanExecuteChangedFor(nameof(RegisterCommand))]，属性值变更时，MVVM Toolkit会自动调用RegisterCommand.NotifyCanExecuteChanged()。
3. NotifyCanExecuteChanged()会触发绑定该命令的注册按钮更新启用状态，而Android要求只有创建视图的UI线程才能操作视图，后台线程直接操作就会抛出上述异常。

方案1：更新UI相关属性时切换到UI线程 #

修改UsernameCheck方法，将属性更新逻辑包裹在MainThread.BeginInvokeOnMainThread中，确保在UI线程执行：

[RelayCommand]
private async Task UsernameCheck()
{
    bool accountExistsResult = false;
    string newErrorMsg = null;

    if (UsernameIsValid)
    {
        Errors.Remove(ErrorTypes.AccountExists);
        var accountCheckResponse = await CheckAccountExists();
        if (accountCheckResponse.IsOK)
        {
            accountExistsResult = accountCheckResponse.Data;
            if (accountExistsResult)
            {
                newErrorMsg = "This username is already taken, please try another.";
            }
        }
        else
        {
            newErrorMsg = $"Opps, something went wrong. {accountCheckResponse.Message}.";
        }
    }

    // 切换到UI线程更新属性
    MainThread.BeginInvokeOnMainThread(() =>
    {
        AccountExists = accountExistsResult;
        if (!string.IsNullOrEmpty(newErrorMsg))
        {
            Errors.Add(ErrorTypes.AccountExists, newErrorMsg);
        }
        UpdateErrorMessage();
    });
}

方案2：移除ConfigureAwait(false)（业务允许时） #

如果AccountService的异步调用不需要强制留在后台线程，可以去掉内部的ConfigureAwait(false)，让await后代码自动回到UI线程：

// 修改AccountService中的异步方法示例
public async Task<Response<bool>> CheckAccountExistsAsync(string username)
{
    // 移除ConfigureAwait(false)
    var rpcResponse = await _rpcClient.CallAsync<bool>("check_account", username);
    // 其他逻辑
}

方案3：手动实现属性的UI线程更新 #

如果ViewModel有多个类似属性，可以手动编写属性setter，确保变更通知在UI线程触发（放弃源生成器的自动实现）：

private bool _accountExists;
[NotifyCanExecuteChangedFor(nameof(RegisterCommand))]
public bool AccountExists
{
    get => _accountExists;
    set
    {
        if (_accountExists != value)
        {
            _accountExists = value;
            MainThread.BeginInvokeOnMainThread(() =>
            {
                OnPropertyChanged();
                RegisterCommand.NotifyCanExecuteChanged();
            });
        }
    }
}

内容的提问来源于stack exchange，提问作者Thomas Kelly