Roadmap or expectations for Fabric support and V3.

[AndreiCalazans]

Hi, thank you for your work on Reanimated. I couldn't find any roadmaps or set of expectations for when V3 will have a stable release with support for Fabric. What are the expectations around this? Is there a place we can track?

Thank you again.

[psycheangel]

Hi, also there is no follow-up on how to build from the source for reanimated v3.

I have tested v3 using aar RN 70 (with RN init cra) seems to be working in debug mode, but for the release version of apk still have crash issue

[tomekzaw]

Hi, also there is no follow-up on how to build from the source for reanimated v3.

Do you mean compiling Reanimated C++ codebase when building the app? Reanimated v3 is only built from sources (there are no AARs in the npm package) and thus it requires Android NDK to be installed and properly set up.

but for the release version of apk still have crash issue

Can you please submit an issue with the full stack trace of this crash you are experiencing?

[psycheangel]

@tomekzaw its probably because I`m not building reanimated v3 from the source.
is the command for the building would be /gradlew installArchives ?

I need to clarify, the AAR is used because there is other package library using it (rn-vision-camera)

[tomekzaw]

Hey, I'm not sure whether react-native-vision-camera supports Reanimated 3. cc @mrousavy

[psycheangel]

Yes, it's currently not supporting fabric, I use the AAR to skip compile failure (not for production usage).
the crash is not an issue with reanimated v3 package, I already found out why it crashed.
thanks @tomekzaw

[mrousavy]

Hey! Yea VisionCamera does currently not work with the new React Native Architecture. I didn't have the time to look into this yet, so I would appreciate any help there. It's on my todo list tho, the new arch will bring tons of improvements and new possibilities to the next version of VisionCamera - I'll also make sure to make it compatible with REA v3.

[tomekzaw]

I couldn't find any roadmaps or set of expectations for when V3 will have a stable release with support for Fabric. What are the expectations around this?

The plan is that we will release 3.0.0 stable once we implement Layout Animations for Fabric. Apart from this, we are still working on profiling and optimizing algorithms related to animating layout props.

Currently, Reanimated 3.0.0-rc.x supports Fabric on RN 0.69+. However, due to a number of breaking changes in recent releases of React Native, we are considering dropping support for RN <=0.70 once RN 0.71 rolls out with prefabs which may greatly simplify the build scripts for Android. Right now we have a number of giant chunks of code in for downloading native dependencies (boost, glog, folly, double-conversion), unpacking *.so files from *.aar etc. that we really wish to get rid of. Also, when releasing a new version of Reanimated, we need to test the package against a wide range of RN versions.

Is there a place we can track?

I think that this discussion might be such place 😄

[capezzbr]

However, due to a number of breaking changes in recent releases of React Native, we are considering dropping support for RN <=0.70 once RN 0.71 rolls out with prefabs which may greatly simplify the build scripts for Android.

Does that mean that there is a world where Reanimated 3.0.0 stable will be released with support for RN >= 0.69, and then follow up versions will only be compatible with RN > 0.70 (once RN 0.71 is released), or that Reanimated 3.0.0 stable will only happen for RN 0.71?

I am asking since RN 0.70 was just released and I was hoping that Reanimated 3.0.0 stable will be compatible with that 🙇

[mrousavy]

We also have this cool idea of dropping support for RN <=0.70 on Paper and thus support only RN 0.71+ (Paper & Fabric) once the native dependencies are published as prefabs

I think this is a good idea. As library authors it's really hard to maintain support for every RN version, and I think a jump from RN 0.68 to RN 0.71 isn't too unrealistic for most apps. I am not using the new arch in any of my apps yet, and I doubt a lot of people are.

Using prefabs makes everything way easier and ideally build faster as well, I'll definitely go that path with my libraries 😄

[capezzbr]

I am not using the new arch in any of my apps yet, and I doubt a lot of people are.

That is probably true, but having to be on RN 0.71 in order to have a stable version of Reanimated V3, will make this even worse 😅

[mrousavy]

Well yea, but if you take a look at the CMakeLists.txt / build.gradle files of REA or VisionCamera or MMKV you'll probably understand that this is a fair compromise - it's just really hard for library authors to maintain support for everything, and waiting to enable the new arch until you're on RN 0.71 is also a fair assumption imo.

[fergusmeiklejohn]

I think you should drop support for versions of RN which significantly affect your ability to maintain and improve Reanimatedv3. My reasoning is this: if a project has to use or support an old version of RN then that project can use ReanimatedV2, which already works brilliantly.

[capezzbr]

Given that React Native 0.71 will be released soon, I am in favor of what said above 😃 Especially if that means that Reanimated V3 will be able to receive more support and iterate faster!