[BUG] UIKit.UIKitThreadAccessException in iOS as canExecute: this.IsValid() doesn't tick in MainThread about reactiveui.validation HOT 4 CLOSED

Hey @gsgou 👋,

Thank you for opening an issue. We will get back to you as soon as we can. Also, check out our Open Collective and consider contributing financially.

https://opencollective.com/reactiveui

PS.: We offer priority support for all financial contributors. Don't forget to add priority label once you start contributing 😄

ReactiveUI - Open Collective

An advanced, composable, functional reactive model-view-viewmodel framework for all .NET platforms!

from reactiveui.validation.

@gsgou this is expected behavior. ReactiveCommands do not explicitly schedule anything on the UI thread. Since CanExecute controls whether a button is enabled/disabled, if you use the BindCommand extension, you need to ensure that the observable that controls CanExecute pushes the notification on the UI thread. Not all commands need to notify on UI thread, so there is no blanket policy to apply or force that on any of the Bind or BindCommand extensions.

from reactiveui.validation.

@michaelstonis tks a lot, i get it now.
Maybe the Sample could be updated for XF then
and an overload of the IsValid() with a scheduler.

from reactiveui.validation.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from reactiveui.validation.