In Xamarin.Android we fixed an issue where private nested classes were getting unintentionally bound. However, thanks to Java's lax rules regarding visibility, you can reference those classes in public API. C# does not allow you to do this, so you need to expose the class as public so it will be bound and thus usable.
This updates 2 samples that were relying on exposing private nested classes to explicitly mark then as public via metadata.
In Xamarin.Android we fixed an issue where private nested classes were getting unintentionally bound. However, thanks to Java's lax rules regarding visibility, you can reference those classes in public API. C# does not allow you to do this, so you need to expose the class as
publicso it will be bound and thus usable.This updates 2 samples that were relying on exposing private nested classes to explicitly mark then as public via metadata.