birdofpreyru
[Windows] Support for New Architecture.
× Build failed with message 5:10>.\node_modules\react-native-windows\PropertySheets\external\Microsoft.ReactNative.Uwp.Common.props(12,5): error : Property 'RnwNewArch' was set to 'true'. Projects built against Microsoft.ReactNative.Uwp require RnwNewArch to be 'false'. [.\node_modules\@dr.pogodin\react-native-fion.
This prevents its usage in react-native-windows applications that use the new architecture.
Hey @KGGrande, have you seen #110, #113 ? For Windows it currently works with the library version v2.32.1 and [email protected]; because after that Microsoft team fell behind — they only released react-native-windows for [email protected] support when [email protected] was already out, and there is still no react-native-windows version for [email protected].
Thus, in this library, I just adopted [email protected] already, not planning to upgrade an older version for [email protected] support for Windows, and will try to revive Windows support once Microsoft team catches up with the latest RN development. Because, if people on fat, corporate Microsoft payroll fail to keep up supporting the latest RN versions, no way I (a freelance developer, not supported by anybody) am going out of my way to support legacy RN versions in an open source library, which (especially Windows support by the library) does not generate me a profit.
Hi @birdofpreyru , thank you for the quick response! I am actually using .76, the issue as I see it is that the windows version provided uses UWP which is restricted to the old architecture as opposed to using WinAppSDK which is backed by the new architecture.
Agh... yeah... the story behind it is the following — originally I started to support Windows here (UWP was the only option back then), because I got paid once to support Windows in react-native-static-server, to work alongside react-native-webview; and also my test app for react-native-static-server relies on react-native-webview. Thus, migration from UWP to WinAppSDK only makes sense to me if I migrate both libraries, and it keeps working alongside react-native-webview. Now, I tried, react-native-webview as is does not work with WinAppSDK, thus for now keeping everything UWP is the only feasible option, unless there is a serious financial incentive to work on it (and react-native-webview is very poorly maintained in general, and for Windows in particular, as it is done by the same Microsoft team — my guess, migration to WinAppSDK in that library is not going to happen any time soon).