Xamarin Forms中ReactiveUI的WhenActivated未触发，求排查方案

Let’s break down the key areas to check for your scenario—where your LoginView loads but WhenActivated never triggers, even with a ViewModel implementing ISupportsActivation and a View inheriting from a custom ContentPageBase.

1. Verify Your IViewFor<T> Implementation in ContentPageBase #

ReactiveUI relies entirely on the IViewFor<T> interface to link your View and ViewModel. If this implementation is incomplete or incorrect, activation events won’t be passed between the two.

Double-check that your ContentPageBase properly implements both the typed ViewModel property and the untyped IViewFor.ViewModel property (required for ReactiveUI’s internal logic):

public class ContentPageBase<TViewModel> : ContentPage, IViewFor<TViewModel>
    where TViewModel : class, IRoutableViewModel, ISupportsActivation
{
    public static readonly BindableProperty ViewModelProperty =
        BindableProperty.Create(nameof(ViewModel), typeof(TViewModel), typeof(ContentPageBase<TViewModel>));

    public TViewModel ViewModel
    {
        get => (TViewModel)GetValue(ViewModelProperty);
        set => SetValue(ViewModelProperty, value);
    }

    // Required untyped implementation for ReactiveUI compatibility
    object IViewFor.ViewModel
    {
        get => ViewModel;
        set => ViewModel = (TViewModel)value;
    }
}

If you’re using a non-generic ContentPageBase, ensure the ViewModel casting matches your LoginViewModel type exactly.

2. Confirm ViewModel’s ISupportsActivation Setup #

Your LoginViewModel must initialize the ViewModelActivator property correctly—this is the core component ReactiveUI uses to track activation state:

public class LoginViewModel : ReactiveObject, IRoutableViewModel, ISupportsActivation
{
    // Critical: Initialize the activator here
    public ViewModelActivator Activator { get; } = new ViewModelActivator();

    // Rest of your ViewModel logic...
}

Without a properly initialized Activator, WhenActivated has no mechanism to trigger.

3. Forward View Lifecycle Events to ReactiveUI #

Xamarin Forms ContentPages don’t automatically notify ReactiveUI of lifecycle changes like OnAppearing or OnDisappearing. Your ContentPageBase needs to explicitly forward these events to kick off activation:

protected override void OnAppearing()
{
    base.OnAppearing();
    this.ActivateViewModel(); // Tells ReactiveUI the View/ViewModel is now active
}

protected override void OnDisappearing()
{
    base.OnDisappearing();
    this.DeactivateViewModel(); // Tells ReactiveUI to deactivate the ViewModel
}

Skip this step, and ReactiveUI never knows when your View is visible—so WhenActivated will never fire.

4. Check Timing of WhenActivated Registration in the View #

Make sure you’re calling this.WhenActivated in your LoginView’s constructor after InitializeComponent(), and either before setting the ViewModel or ensuring the ViewModel is assigned before the View appears:

public LoginView()
{
    InitializeComponent();

    // Register WhenActivated here—this ensures it's ready to catch activation events
    this.WhenActivated(disposables =>
    {
        // Your service setup and bindings go here
        this.Bind(ViewModel, vm => vm.Username, v => v.UsernameEntry.Text)
            .DisposeWith(disposables);
    });

    // If setting ViewModel manually (not via binding/navigation)
    ViewModel = new LoginViewModel(/* inject your dependencies */);
}

If you register WhenActivated after the View has already appeared, it won’t trigger until the next lifecycle change (like navigating away and coming back).

5. Validate Navigation and ViewModel Assignment #

If you’re using IRoutableViewModel, navigate via ReactiveUI’s IScreen navigation service instead of raw Xamarin Forms navigation. Manual calls like Navigation.PushAsync(new LoginView()) often fail to properly link the ViewModel to the View’s activation system.

Also, confirm your ViewModel is actually assigned to the View’s ViewModel property before the View appears—if it’s null when OnAppearing fires, there’s nothing for ReactiveUI to activate.

6. Check for Swallowed Exceptions #

Sometimes WhenActivated does fire, but an exception in your setup code crashes the block silently. Wrap your code in a try-catch and log errors to rule this out:

this.WhenActivated(disposables =>
{
    try
    {
        // Your service setup and bindings here
    }
    catch (Exception ex)
    {
        System.Diagnostics.Debug.WriteLine($"WhenActivated failure: {ex.Message}\n{ex.StackTrace}");
    }
});

Check your IDE’s output window for any unhandled exceptions that might be hiding the issue.

7. Verify Version Compatibility #

Outdated or mismatched versions of ReactiveUI and Xamarin Forms can break lifecycle integration. Ensure you’re using a ReactiveUI version explicitly compatible with your Xamarin Forms release (check ReactiveUI’s release notes for version matching guidelines).

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