Trying to resolve view with tag 1978 which doesn't exist at com.facebook.react.uimanager.RNCustomKeyboardModule.getEdiyById (RNCustomKeyboardModule.java:48)

[singhlovey]

Hi,

I am getting very strange crash. When I opened keyboard on text input on any of the pages of my app and switch to another page, my app get crashed.

I have attached one screen shot of bug. Please help!!

Thanks

[scottaglia]

I'm getting the same error.

"react-native": "0.54.3",
"react-native-custom-keyboard": "^1.0.4",

For now I'm avoiding the crash with a try catch in android (I'm not building for iOs), even though this won't activate the custom keyboard.

private ReactEditText getEditById(int id) {
		try {
			UIViewOperationQueue uii = this.getReactApplicationContext().getNativeModule(UIManagerModule.class).getUIImplementation().getUIViewOperationQueue();
			return (ReactEditText) uii.getNativeViewHierarchyManager().resolveView(id);
		} catch(IllegalViewOperationException e) {
			return null;
		}
}

[singhlovey]

@markainick

Can you please test the same on different devices. I have also made the same changes and not getting crash but now getting different crash.

this crash comes on android 7.1

[scottaglia]

@singhlovey can you please paste the full error stack?
Btw it looks like I'm getting the error only in Remote JS Debugging

[singhlovey]

@markainick

I am not getting any crash in debug mode. After testing release apk on multiple device, I got the above in one of the devices.

I have only this screen shot for now.

Thanks

[singhlovey]

@markainick

Please help for the above issue. I am stuck.

Thanks

[scottaglia]

I don't really have a solution. For now I'm getting around it by manually installing the custom keyboard when i know for certain that the custom input is on screen.

[singhlovey]

@markainick

Can you please provide me sample e.g of how you are installing the custom keyboard when needed.

Thanks

[laurentS]

@markainick we've been experiencing this issue as well, but it's been inconsistent. As you can see in my PR, I've pushed what you did above a step further, and kept looping until it finds the input. This seems to cause apps to hang in some cases, that we haven't quite identified yet. (see the comments on the PR thread)
Can you share how you "know for certain that the custom input is on screen"?

[scottaglia]

@laurentS I added the same method (with name installKeyboard) in the CustomTextInput inside index.js (just like you did in you PR), and I'm calling that method from the onLayout callback of the custom input wrapper through a ref.

[singhlovey]

@markainick

Can you please provide sample example of the above you did to get more clarification. It would be really helpful.

Thanks