2019-01-30, 02:50
(2019-01-30, 02:43)jjd-uk Wrote:If that's what happened, then I totally get it. That is really what I thought would happen as well. At this point, we need a good mitigation strategy. Perhaps we can come up with a decent way to migrate away from the UWP application to the regular EXE? Would that process be pretty straight forward? I don't see much point it sticking with the UWP application on Windows 10 since it really seems like all existing functionality was thrown out the window (pun! in order to get something "universal" running on XBox.(2019-01-30, 02:32)robross0606 Wrote:(2019-01-30, 02:20)jjd-uk Wrote: If you had 17.6 then this was not the UWP version of the app, that was simply an adjusted version of the normal desktop exe app for Store distribution. The genuine UWP app is new for v18 as it was needed to get Kodi onto Xbox.With all due respect, this may be true in terms of how it was "hacked" onto the Windows Store. However, from an end-user perspective, we neither know this nor can we control the UWP update process. This at least deserved a BIG warning during one of the various blog entries about v18 release, as well as some type of documented process for those who need to upgrade. Are there any UWP users who were not completely broken by this release?
It could just be an error in understanding how the Store updates, it might have been assumed that the UWP version for v18 would not replace the desktop bridge created v17 version as appears to have happened. Please try and remember we are volunteers who do this in our free time and there are limited numbers if us, so perhaps something just slipped between the cracks.