react-native: Unable to find JSIModule for class UIManager

We are working on a fix that’s currently on review.

@ejanzer, @sharifhh, @mikehardy thanks for looking into this.

I agree with @ejanzer that this is caused by views that are not directly managed by React Native. In particular, we are referring to views that are not created by this method:

https://github.com/facebook/react-native/blob/master/ReactAndroid/src/main/java/com/facebook/react/uimanager/ViewManager.java#L140-L141

I’ll analyze what’s the proper solution here and update the issue

Can we get a patch until RN 0.64.2 is released?
This is quite an issue for apps using RN 0.64 in production.

Fixed in 0.64.2

Hi, any update on this issue? Thanks for all!

@efstathiosntonas interesting

It creates a View directly itself: https://github.com/hhunaid/react-native-image-crop-tools/blob/5c3ab05dca20cefe542fd3824a40cef0ae2d2541/android/src/main/java/com/parsempo/ImageCropTools/ImageCropViewManager.kt#L31

going in to here https://github.com/ArthurHub/Android-Image-Cropper/blob/2a4a425668bfff1329dd5bfb1b80b0829bb4cc67/cropper/src/main/java/com/theartofdev/edmodo/cropper/CropImageView.java#L178

Then the id for that View is apparently indigestible: https://github.com/hhunaid/react-native-image-crop-tools/blob/5c3ab05dca20cefe542fd3824a40cef0ae2d2541/android/src/main/java/com/parsempo/ImageCropTools/ImageCropViewManager.kt#L39

So, still seems to be the same case of “JSIModule is making an assumption about View ids that is no longer valid” and I believe we are still waiting for @mdvacca to report any findings as promised above

I’m not using react-native-tab-view or @react-native-picker/picker. I downgraded RN to 0.63.4 until a fix has been found in 0.64.

The problem here is happening because the View getId() function is returning an even number and in react native code if the id is even it will use FABRIC and JSI and UIManager doesn’t support that, so it is breaking, now the question is why it generates even number, I tried to downgrade to react-native 0.63.4 and it worked, after that I upgraded back to 0.64 and did a small trick in the library that is crashing, I did the following findViewById(R.id.ID_OF_THE_ROOT_LAYOUT).setId(10023);

I believe this should be closed, as there is a commit on master and it’s been picked to release-0.65 as well

@Bardiamist I was able to resolve my case. It was caused by the usage of react-native-tab-view (v3.0.0) and @react-native-picker/picker (v1.12.0) on the same screen.

When I downgraded react-native-tab-view to v2.16.0 the error disappeared.

More details here -> https://github.com/satya164/react-native-tab-view/issues/1157

Got the same issue when using react-native-pager-view. For your case, the different between react-native-tab-view v2.16.0 and v3.0.0 is that v3 used pager-view so maybe that’s the root cause?

Normally that will have no effect if I understand correctly as the android code is pre-built and depended on as an aar, running react native from source has its own documentation. It can certainly work though if you follow it through

any progress?

I found that pressing my location button on react-native-maps reproduces the same crash on Android

I think @mdvacca is probably the right person to weigh in on this one! It seems like the JS touch handler assumes it’s only dealing with views that were created by React (in which case an even id == fabric) but that’s clearly… not always the case?

@Bardiamist I was able to resolve my case. It was caused by the usage of react-native-tab-view (v3.0.0) and @react-native-picker/picker (v1.12.0) on the same screen. When I downgraded react-native-tab-view to v2.16.0 the error disappeared.

More details here -> https://github.com/satya164/react-native-tab-view/issues/1157

@mikehardy, it worked, Thanks

It is

On Fri 4 Jun 2021 at 18:01, Juan S. Escobar @.***> wrote:

@mikehardy https://github.com/mikehardy could you tell me if the fix is in v0.64.2? I don’t see it referenced in the change log

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/facebook/react-native/issues/31245#issuecomment-854837212, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOVCFJGACVQT6QDVYZAFFTTRD2HFANCNFSM4Z277OKA .

– Erwan

@ebaynaud web search for building / running react native from source

@mtroskot I think the way it goes is that as soon as that commit lands on master you post a cherry pick request to the RN064.1 and RN0.65 cherry picks conversation - which I have just done 😃

in my case using react-native-image-crop-tools is crashing when trying to move the crop box with the finger, this module is using UIManager directly

I was able to easily reproduce this issue with:

just mount this on some image and try to zoom with two fingers (even clicking into it make a crash)

import React, { Component } from 'react';
import { View, PanResponder, Dimensions } from 'react-native';

class ZoomView extends Component {
  constructor(props) {
    super(props);
    this._panResponder = PanResponder.create({
      onPanResponderMove: (e, { dy }) => {
        const { height: windowHeight } = Dimensions.get(`window`);
        return this.props.onZoomProgress(Math.min(Math.max((dy * -1) / windowHeight, 0), 0.5));
      },
      onMoveShouldSetPanResponder: (ev, { dx }) => {
        return dx !== 0;
      },
      onPanResponderGrant: () => {
        return this.props.onZoomStart();
      },
      onPanResponderRelease: () => {
        return this.props.onZoomEnd();
      },
    });
  }
  render() {
    return (
      <View style={{ flex: 1, width: `100%` }}>
        {this.props.children}
      </View>
    );
  }
}

export default ZoomView;

@sharifhh that’s great digging - if I git blame on there it all seems to point to @mdvacca and possibly @ejanzer (going from this https://github.com/facebook/react-native/commit/0a12f3ea77840c218fd9d67d0e3f2ea068cb8c5f) - I think they might know more about the even/odd partitioning of dispatch event handling and specifically in the last commit how what appears to be a new exception raised affects other modules. Hopefully one of them has time to share their wisdom here on the crash as I think it’s related to that change