Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Describe the bug
Steps To Reproduce
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.
So far, this only seems to happen when binding to a TextView. And if we use a OneWayBind (from ViewModel to View) the crash does not happen. So it seems that the problem originates from reacting to Android TextView changes.
I don't know anything about the ReactiveUI code base, so take this diagnosis with a grain of salt...
The very bottom of
And the logs seem to indicate that the crash is originating from within the Subscribe block, when
Could it be that the tuple declaration is in some way contributing to the runtime reflection crash?
It seems there is something about the reflection used to bind the properties that is causing this issue.
We have a WIP pull request where @glennawatson and I have been doing various fixes trying to address this issue. We rolled back the v10 change and that did not seem to fix the problem, which we found odd.
@arda-a A work around would be to just assign the values in the
@ajhuntsman That was the correct place, it seems the reflection is more the culprit as I did a bit of changing around the