-
Notifications
You must be signed in to change notification settings - Fork 100
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
java.lang.NullPointerException Attempt to invoke interface method 'void com.facebook.react.uimanager.UIViewOperationQueue$UIOperation.execute()' on a null object reference #514
Comments
I have confirmed that this issue still happens with Instabug build |
@AndrewMorsillo just so we're on the same page, the snapshot you mentioned wasn't targeted to address the issue in here. |
@AndrewMorsillo we're currently looking into the crashes you've submitted, and we'll update you once we reach any conclusions. Appreciate your patience 🙏 |
@AliAbdelfattah Yep, thanks for the clarification, I assumed that update wouldn't help with this issue but I wanted to make sure you had exact information about what builds I've reproduced the issue with. I hope we can get this figured out quickly, we're seeing about 17% of end user sessions crashing with Instabug enabled and 0% without Instabug... but Instabug is so useful and critical to our beta testing we can't start without it! Please let me know if I can do anything or provide any more information to help you debug. Thanks! |
@AliAbdelfattah I made a new build where I removed all calls to |
Hi @AliAbdelfattah just following up, I still haven't seen this crash since I disabled |
@AndrewMorsillo I've created a snapshot that has a defensive code specifically for |
@AliAbdelfattah I upgraded to that build and re-enabled |
Possible culprit: See RNInstabugReactnativeModule.java: UIManagerModule uiManagerModule = getReactApplicationContext().getNativeModule(UIManagerModule.class);
uiManagerModule.prependUIBlock(new UIBlock() { |
Closing this as we're not able to reproduce and the stack trace doesn't have any references to Instabug. |
This nullPointerException only occurs when Instabug is integrated into my app. If I remove Instabug this issue goes away. This appears to be a thread safety issue where something is accessing react-natives ui operations queue from a thread other than the UI thread. There's more information in these issues:
facebook/react-native#11428
facebook/react-native#27819
This is a very severe issue for us. It crashes ~10% of all sessions which means we cannot use Instabug while this issue is ongoing. We tried a lot of things to track this one down and found out it was Instabug by trial and error.
This only happens in our release build on the play store. We have not been able to reproduce it on demand but it happens for > 10% of all user sessions.
Steps to Reproduce the Problem
Run a release build of a RN 0.63.2 app with Instabug on Android
Expected Behavior
App should not crash
Actual Behavior
App crashes randomly with the above exception for >10% of sessions. If we remove Instabug our app is 100% crash free.
Instabug integration code
package.json
"instabug-reactnative": "^9.1.7",
MainApplication.java
App js code
SDK Version
9.1.7 react native
React Native, iOS and Android Versions
RN 0.63.2
Device Model
Any Android device
[Optional] Project That Reproduces the Issue
Unable to reproduce on demand. Only happens in release build on play store where it appears to happen at random.
The text was updated successfully, but these errors were encountered: