Removing Last Item from ObeservableCollection for ListView.ItemsSource throws exception on Windows 8.1 (Desktop) about xamarin.forms HOT 7 CLOSED

Windows 8.1 is no longer supported, so this issue will be closed. If this affects UWP as well, please reopen it with a reproduction. Also, in the future, please aim to use the provided issue reporting template. Thanks!

from xamarin.forms.

Windows 8.1 is still supported on the Xamarin 2 branch. Our application is unusable due to this.

from xamarin.forms.

@mattclarkie from the bugzilla report it appears that issue was resolved and confirmed in a nightly build. Did you check that?

If that's the case and this is already fixed, then we could make sure that it is included in the next 2.5.0 service release.

from xamarin.forms.

@davidortinau the person who verified it as "resolved" "forgot" that Windows 8.1 exists, the renderer affected is full of #if !WINDOWS_UWP and it's clearly one of those blocks that's causing the error, the UWP path presumably works perfectly fine.

Please state either

• WinRT is dead, broken, all bets are off
• Actually provide some reasonable level of support, and importantly test for regressions

We are in the process of moving to UWP, in fact we've been working on the UWP port on and off for months and find xxx doesn't work in UWP or needs some extra workaround the other platforms don't. Our project started off using Xamarin.Forms 1.3.1.6296, we've put up with a lot over the years as Xamarin matured because it was fundamentally a good technology, but this experience, and your support processes make me question whether becoming so locked into your platform is a terrible mistake to make.

from xamarin.forms.

@mattclarkie I believe this has already been stated. The end of life for support of Windows Phone has been public for a long time. I'm sorry if our product communication on the impending removal of these platforms was not made more clear. For months we have been marking all Windows Phone 8/8.1 issues as "won't fix".

That said, we absolutely desire to support you and help you through this transition.

If the nightly build is confirmed to address your issue, I'll work with engineering to see that fix included in the next service release.

Please email me your UWP frustrations and identify the related Bugzilla or Issues so I can help prioritize those issues and/or provide guidance. [email protected]

from xamarin.forms.

@davidortinau
Firstly, this is not Windows Phone, this is Windows Desktop 8.1. They are not the same thing! Windows 8.1 is still in mainstream support until January 2018 so Xamarin's decision to pull the plug on it alongside Windows Phone is barely justifiable.

Secondly, you only introduced the issue a few months ago (October is my best guess from looking at your source), and now are washing your hands of it. If Windows 8.1 is EoL then please stop breaking the existing functionality, you could have left the v2.0 branch well alone instead of breaking it for those of us that are still using Windows RT. Deprecated doesn't mean actively break the existing functionality. We've upgraded to latest stable to get bug fixes required for UWP and the result is the Windows 8.1 application is so broken it can't be released thanks to "latest [un]stable".

from xamarin.forms.

@mattclarkie apologies, you're right. Thanks for correcting me. They are not the same thing.

We have not removed WinRT from the 2.5.0 branch.

Our next major release will not include WinRT and Windows Phone 8/8.1 backends and should be expected to occur sometime after the January 2018 mark.

For any future, long term work to these platforms, the best option is to fork and work from the 2.5.0 branch linked above.

In terms of how we can help in the immediate for this issue that's blocking you, have you been able to test a nightly release? Another option is for you to PR a fix and we'll get it into a 2.5.0 service release.

In terms of your Windows 8.1. and UWP situation, it is possible to configure your solutions to run different versions of Xamarin.Forms. It doesn't sound fun, but if it solve you situation until you can move completely to UWP, then perhaps it's worth it.

from xamarin.forms.