This is a quick follow-up with some more information on the case.
After downloading the ReactiveUI source code and debugging it locally, we have determined that there is a potential issue with ReactiveUI's source which causes this exception. A specific part of ReaciveUI's implementation merges Android resource IDs into a Dictionary without considering the possibility of duplicate dictionary keys. When you reference the Telerik UI for Xamarin.Android assemblies there are two resource IDs which are the same but with different casing. ReactiveUI's code doesn't consider the casing and sees them as two identical resource IDs which leads to an attempt to insert an item into this Dictionary which has a key that already exists. This causes the exception.
We will contact ReactiveUI's team to inform them about this case and discuss a possible solution.
This is currently all we can do.
Let us know if you have additional questions.
Telerik by Progress
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items