My company has made a significant investment in XF. We have come to the realization that memory issues with XF are so extreme they are beyond fixing irrespective of the coding strategy and implementation patterns used. We have a 6th generation commercial product with over 150 views. It has been constructed using PRISM since version 1 and we are very experienced in building highly modular decoupled applications and the pitfalls of memory leaks that are potentially associated with such architectures. We are not strangers to understanding how to code to avoid memory leaks. Profiling is a daily component of our practice. The problems with XF are beyond anything we have ever seen before. We have observed the countless amounts of others with the same problems and we have observed Xamarin do absolutely nothing about it. What Xamarin should have done is clearly stated that this product is not stable.
We are done sharing code, having discussions and talking about this in general. Its pointless to attempt to say that GC in XF works. What we expect is a direct answer from Xamarin in a official / formal capacity that says we are either going to fix this or we are going to continue doing what we have been doing. Pushing out new builds ontop of broken / unstable builds.
No one wants XF version 2.0 or 3.0 until XF version 1.0 is stable. Were tired of hearing about all the other things that Xamarin must do before they get back to fixing an issue that makes their product unusable for enterprise settings and commercial offerings. Please stop stacking broken features ontop of half baked patches.
Please take the time to explain to us and the rest of the community your plans or lack there of in addressing your broken memory leak issue. At one point this platform had so much promise. Now its getting a rather poor reputation as something that should be avoided at all costs