That sounds like a weird question given that I want to use something from Google on a Google platform, but: Given that XF Forms depends on those really old Google Play and Forms libraries, is including the Places Picker even feasible? I didn't have an issue on iOS, but there I don't struggle with XF's hardcoded dependency issues.
If anybody could comment on this before I'm starting a potentially pointless attempt, that would be awesome.
Thanks,
Philipp
Posts
@PhilippSumi
I believe the next version (2.4.0) will break that dependency issue.
Also you can now surface native views directly into Xamarin Forms with platform specifics so that might be an option. In 2.4.0 you can use native views with XamlC
https://blog.xamarin.com/introducing-xamarin-forms-2-3-3-native-view-declaration-and-platform-specifics/
https://forums.xamarin.com/discussion/85747/xamarin-forms-feature-roadmap/p1
Regarding the dependency issue, maybe david can confirm if that's the case or if I'm wrong.
@DavidOrtinau
@NMackay Yeah, with Xamarin Forms having that dependency on the 23.3.0 version of the Xamarin.Android.Support.V4 lib, this is off the table
With regards of killing that hard dependency, this was mentioned recently with a link to a very small code change that looked trivial. I wonder whether that could be backported for a custom build of XF 2.3.4.*, or leverages changes in a future version anyway. I didnt' find that therad anymore, but will go looking for it tomorrow. @DavidOrtinau might know about this.