The application suffers a hard crash (Fatal Signal 6 / SIGABRT) due to an unhandled NullPointerException in the JNI bridge (libHttpClient.Android.so). The native C++ HTTP client attempts to invoke CallVoidMethodV on a destroyed or null Java object when handling network delays on IPv6/NAT64 mobile connections.
Steps to reproduce the problem:
Connect the Android device to a Mobile Data network restricted to IPv6 routing.
Disable Wi-Fi.
Launch Minecraft Bedrock Edition in a completely unmodified vanilla environment.
Attempt to join a Multiplayer Server or Realm.
Expected result:
The game's HTTP client should gracefully handle the connection delay or failure, validate if the Java object still exists, and safely cancel the request by showing an in-game "Connection Timed Out" message.
Real result:
The Android OS aborts the process immediately because libHttpClient.Android.so attempts to use CallVoidMethodV on a null object, throwing a fatal JNI error and crashing the game entirely. Error log: JNI DETECTED ERROR IN APPLICATION: obj == null in call to CallVoidMethodV.
Linked issues
duplicates 1
Attachments
Comments 2
We're tracking this issue at MCPE-239705, so I will resolve and link this report as a duplicate.
If you have new information to share, please leave a comment on the linked report. If not, add a vote to the report to show that you are affected.
If you haven't already, please make sure to search before creating a report to see if the issue has already been reported. See the Bug Tracker Guidelines for tips on searching for issues.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for helping us improve Minecraft! We saved your files: