lottie-react-native
lottie-react-native copied to clipboard
React Native Windows: Package does not work
Description
I've followed all steps mentioned in docs. first of all the docs are out dated and need to be updated. For example: I had to remove src from this to make it work
<PropertyGroup Label="LottieReactNativeProps"> <LottieReactNativeDir>$([MSBuild]::GetDirectoryNameOfFileAbove($(MSBuildThisFileDirectory), 'node_modules\lottie-react-native\package.json'))\node_modules\lottie-react-native</LottieReactNativeDir> </PropertyGroup> <ImportGroup Label="LottieReactNativeTargets"> <Import Project="$(LottieReactNativeDir)\windows\cppwinrt\PropertySheets\LottieGen.Auto.targets" /> </ImportGroup>
Issue: When i try to build the project it gives this error
× Building Solution: Microsoft.ReactNative.Managed.CodeGen -> E:\MyApp\node_modules\react-native-wind... × Build failed with message E:\MyApp\windows\pos\obj\x64\Debug\Generated Files\Animations\LoadingLottie.cs(220,58): error CS1061: 'Compositor' does not contain a definition for 'CreateAnimationController' and no accessible extension method 'CreateAnimationController' accepting a first argument of type 'Compositor' could be found (are you missing a using directive or an assembly reference?) [E:\some\pos-windows\windows\pos\pos.csproj]. Check your build configuration. Command failed. Re-run the command with --logging for more information.
I'm using VS 2022. I had to update properties of project as well
Snack or a link to a repository
Lottie React Native version
6.7.2
React Native version
0.74.5
Platforms
Windows
Workflow
React Native
Architecture
Paper (Old Architecture)
Build type
Debug app & dev bundle
Device
Real device
Acknowledgements
Yes
We don't have resources and time to test windows integration. We will update you on this as soon as we find someone working on react native windows.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.