-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incopatible with react-native-windows (^0.70.xx) #1132
Comments
Unfortunately the support for windows is very minimal right now and we don't have anyone to work on it. I will keep this issue open in case someone volunteers to fix windows issues. |
@hpcrycki, I tested the versions of react-native-window |
@Victor0814gui Thanks for your response. Can you please share with me your code, I want to use it as an example if it is possible. Which type of |
I confess it was challenging for me to add this to a project, haha. I'll create a basic example repository with Lottie configuration and the steps you need to follow. I believe |
@Victor0814gui I think the correct question is: What type of application you created is |
Sorry, I didn't understand the question.😅 All the versions I created were with |
@hpcryck I put this together https://github.com/Victor0814gui/lottie-6.4.1-windows, tell me if it works for you too. 2023-11-28.19-10-49.mp4 |
@Victor0814gui thanks for your fast responses. Can you please share with me the When I try to load the C++ project in VS 2019 ( https://github.com/Victor0814gui/lottie-6.4.1-windows/blob/main/windows/cppwinrt/LottieReactNative.sln ) I got this error: |
Sorry for the delay, I ended up losing my schedule 😥. I'll try this now. |
Any updates? We don't personally have windows devices to test this out on, so any info is appreciated |
I'm stuck on this issue as well, using the repository https://github.com/Victor0814gui/lottie-6.4.1-windows. I've tested it on all versions of React Native 0.70.x, and it worked perfectly. My suspicion is that it might be because I'm using Visual Studio 2022. I'll need some time to reinstall 2019 and test this again. |
you need to install windows sdk for this issue. it works for. |
I stuck here, I don't understand what problem is occur. steps to reproducestep 1.install dependenices step 2.goto 'windows\sampleDesktop\sampleDesktop.vcxproj' this file and add this code to after this
step 3.install these NuGet packages: LottieGen.MsBuild step 4.add this code to 'windows\sampleDesktop\App.cpp' this file
system info:-
problem:-Caution × Building Solution: F:\sampleDesktop\windows\sampleDesktop\sampleDesktop.vcxproj(167,5): error MSB4019: The imp... expected:-solution should build. repo:- |
I was also having issues with building for C++ on Windows, but I think I figured out the root causes. First issue, the path to The Second issue when building with C++ is that you MUST have at least one JSON animation asset included in your build. I initially tried without adding any animations and this resulted in several targets in Another quirk about including animation assets: The code generation automatically capitalizes the first letter of the animation JSON file for the animated visual type, but maintains the original capitalization in
|
Description
I tried to integrate
lottie-react-native
withreact-native-window
but I got multiple issues.In the beginning, I installed the package using
yarn
.When I tried to integrate with
LottieView
I got this error:Invariant Violation: requireNativeComponent: "LottieAnimationView" was not found in the UIManager.
I saw that the
lottie-react-native
inside thenode-modules
folder and I didn't find anywindows
folder that needed to be loaded in the project.I added it manually (https://github.com/lottie-react-native/lottie-react-native/tree/master/packages/core) and I made all the setup using documentation (https://github.com/lottie-react-native/lottie-react-native#windows-react-native--063) and I got the following errors on building the solution.
Env info:
-react-native-windows:
^0.70.xx
-lottie-react-native:
v6.4.1
The text was updated successfully, but these errors were encountered: