I have found the same issue on release APK alse see #10795

@akzhou I solved this by using the InteractionManager runAfterInteractions in a ComponentDidMount, see below for further details:

https://github.com/brentvatne/run-after-interactions-exp/blob/master/index.js

@ettysekhon it seem that you use renderPlaceholder replace modal view.at last,I fix it by compile the react-native source code with modify ReactModalHostView.java onSizeChanged method
protected void onSizeChanged(final int w, final int h, int oldw, int oldh) { super.onSizeChanged(w, h, oldw, oldh); return }
i don't know how the code work,at least no crash

@akzhou can you push an PR to facebook？

+1

This fix looks like it removes some important functionality.

FWIW I have this reproducible using redux and saga. I have a bool state variable mapped to a Modal component's 'visible" property. I change the state from false to true at the start of the saga. If I change the state back to false in the same saga I get this error consistently.

It seems like a safer band-aid would be to put a null test at line 151 (RN 0.37) in UIImplementation.java:

public void updateNodeSize(
      int nodeViewTag,
      int newWidth,
      int newHeight) {
    ReactShadowNode cssNode = mShadowNodeRegistry.getNode(nodeViewTag);
      if( cssNode != null ) {  // <-- right here
        cssNode.setStyleWidth(newWidth);
        cssNode.setStyleHeight(newHeight);
      }

    // If we're in the middle of a batch, the change will automatically be dispatched at the end of
    // the batch. As all batches are executed as a single runnable on the event queue this should
    // always be empty, but that calling architecture is an implementation detail.
    if (mOperationsQueue.isEmpty()) {
      dispatchViewUpdates(-1); // -1 = no associated batch id
    }
  }

@Proberts can you create an app that reproduces this issue on https://rnplay.org and then attach it to #10795?

@idris Trying but it looks like I can't import redux-saga. Not sure how to implement it without as I'm new to RN. I can try to make a minimal app that shows the problem and stick it on github. Would that help?

@Proberts yeah that would probably be useful for react-native devs to have a way to reproduce it.

+1

FWIW I can't get it to reproduce in a minimal setup with the way I thought it was getting triggered in my code. I had it go away for a while after I moved some code being called from an onPress event handler into a saga. But it came back after I added to async calls to the saga - so at least I have a place to start looking.

This problem is fresh. +1

We're also encountering this crash on Google Android emulators API 23, RN 0.35 with automated runs via Calabash. We haven't seen it (yet thankfully?) on physical devices, but it's pretty annoying to have our automation fail so randomly. It also happens around the time of a modal display.

I am having the same issue. I have modal (fullscreen) and android keyboard on. It happens when I close it with enter key (onSubmitEditing). I've tried to close modal in InteractionManager.runAfterInteractions callback, but it didn't help.
However It seems to be working when I postpone it with setTimeout(..., 300)

I have the same question on React Native
Version: 0.30.0
Platform: Android (Coolpad A8-930)

+1

Any updates?

Yeah this bug is pretty nasty, i've got 2 bad reviews in play store because of it ...
I've used this fix

const CustomModal = ({ visible = false, children }) => {
  if (!visible) {
    return <View/>
  }
  return (
    <Modal
      style={styles.modalWrapper}
      animationType='slide'
      onRequestClose={() => {}}
      visible={true}
      transparent >
      {children}
    </Modal>
  )
}

Nothing fancy, but works okay

I have the same question on React Native
Version: 0.39.0
Platform: Android

+1

I haven't seen this problem since I upgraded to 0.39.2 It might have been fixed by this commit

I've just seen it with 0.41-rc

+1 the same problem in RN 0.39 Android 4.4.4. Also cause with the Modal. I am a little upset.

Experiencing this randomly on startup as well. 0.4.0

+1 with version 0.40

@grabbou This should be pretty safe to merge, what release can we get this into do you think?

Yeah, I'll include it in next RC tomorrow.

I am using RN 0.42.3, but I am still getting this error randomly on application start.

@itcurves give a try with v0.43.0-rc.4. I think that this release contains necessary patch as @grabbou stated.

I added a delay of 1 second before showing the infected view page, which solved the issue temporarily

I think it is related to react-native-router-flux

@cemo

I have not been able to run this release. I followed the documentation located here to upgrade to this release version you mentioned in your post, but when I try to do 'react-native run-android', this is what I get (see below). Is there any documentation for how to install one of these release versions?

• What went wrong:
  A problem occurred configuring project ':app'.

Could not resolve all dependencies for configuration ':app:_debugApkCopy'.
Could not resolve com.facebook.fresco:fresco:1.0.1.
Required by:
OrderEntry:app:unspecified > com.facebook.react:react-native:0.43.0-rc.
4
> Could not resolve com.facebook.fresco:fresco:1.0.1.
> Could not get resource 'https://jcenter.bintray.com/com/facebook/fres
co/fresco/1.0.1/fresco-1.0.1.pom'.
> Could not GET 'https://jcenter.bintray.com/com/facebook/fresco/fre
sco/1.0.1/fresco-1.0.1.pom'.
> jcenter.bintray.com
Could not resolve com.facebook.fresco:imagepipeline-okhttp3:1.0.1.
Required by:
OrderEntry:app:unspecified > com.facebook.react:react-native:0.43.0-rc.
4
> Could not resolve com.facebook.fresco:imagepipeline-okhttp3:1.0.1.
> Could not get resource 'https://jcenter.bintray.com/com/facebook/fres
co/imagepipeline-okhttp3/1.0.1/imagepipeline-okhttp3-1.0.1.pom'.
> Could not GET 'https://jcenter.bintray.com/com/facebook/fresco/ima
gepipeline-okhttp3/1.0.1/imagepipeline-okhttp3-1.0.1.pom'.
> jcenter.bintray.com

@itcurves Do you have resolved this problem?

Is this issue already fixed in the latest release? Because I just checked my crashlytics and this issue seems to appear quite often.

So this commit is not in RN 0.43?

anyone confirm that this is fixed for RN 0.44?

Any update? We have the same issue with RN 0.41.2
RN 0.44 is ok?

Yes, .44 should be fine as it's listed in the release notes: https://github.com/facebook/react-native/releases/tag/v0.44.0

Still happening on my side, without using any Modal (I am using react native navigation and its built-in Modal).

platform: Android (min api 21)
react-native: 0.48.3

+1

@astreet not sure if you have any input on this. I have the same issue as @39otrebla described.
It's really random on our end and almost never happens, but when it does it's when transitioning to a screen.
We're running react-native: 0.48.4 and react-native-navigation: ^1.1.300.

Still happening in 0.49.5

The issue is still here, unfortunately.
React Native 0.55.4, 0.56.0
Android 8