react-native icon indicating copy to clipboard operation
react-native copied to clipboard

Could not get BatchedBridge, make sure your bundle is packaged correctly

Open RuthlessPotato opened this issue 3 years ago • 13 comments

We are now using react-native version 0.62 when we ran this app under dev model. The virtual environment of the mobile can run this app successfully. However, if when we ran this app under released model, the app will flash back. By using adb to check the log, which is as followings:

07-20 09:04:55.728 28992 29016 E AndroidRuntime: FATAL EXCEPTION: mqt_js 07-20 09:04:55.728 28992 29016 E AndroidRuntime: Process: com.github, PID: 28992 07-20 09:04:55.728 28992 29016 E AndroidRuntime: com.facebook.jni.CppException: Could not get BatchedBridge, make sure your bundle is packaged correctly 07-20 09:04:55.728 28992 29016 E AndroidRuntime: at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method) 07-20 09:04:55.728 28992 29016 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:883) 07-20 09:04:55.728 28992 29016 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:100) 07-20 09:04:55.728 28992 29016 E AndroidRuntime: at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:26) 07-20 09:04:55.728 28992 29016 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214) 07-20 09:04:55.728 28992 29016 E AndroidRuntime: at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:225) 07-20 09:04:55.728 28992 29016 E AndroidRuntime: at java.lang.Thread.run(Thread.java:919)

RuthlessPotato avatar Jul 22 '20 03:07 RuthlessPotato

:warning: Missing Environment Information
:information_source: Your issue may be missing information about your development environment. You can obtain the missing information by running react-native info in a console.

github-actions[bot] avatar Jul 22 '20 03:07 github-actions[bot]

⚠️ Missing Environment Information ℹ️ Your issue may be missing information about your development environment. You can obtain the missing information by running react-native info in a console.

System: OS: Windows 10 10.0.17134 CPU: (8) x64 Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz Memory: 4.68 GB / 15.86 GB Binaries: Node: 10.20.1 - D:\Program Files\nodejs\node.EXE Yarn: 1.22.4 - ~\AppData\Roaming\npm\yarn.CMD npm: 6.14.5 - D:\Program Files\nodejs\npm.CMD SDKs: Android SDK: API Levels: 27, 28, 29 Build Tools: 28.0.3 System Images: android-25 | Google APIs ARM 64 v8a, android-25 | Google APIs Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-Q | Google APIs Intel x86 Atom npmPackages: react: 16.9.0 => 16.9.0 react-native: 0.61.5 => 0.61.5 npmGlobalPackages: react-native-cli: 2.0.1

RuthlessPotato avatar Jul 22 '20 05:07 RuthlessPotato

Same issue goes for me. Android release build crashes when using react-native 0.62.

JB-CHAUVIN avatar Aug 19 '20 14:08 JB-CHAUVIN

:warning: Missing Required Fields
:information_source: It looks like your issue may be missing some necessary information. GitHub provides an example template whenever a new issue is created. Could you go back and make sure to fill out the template? You may edit this issue, or close it and open a new one.

github-actions[bot] avatar Aug 19 '20 15:08 github-actions[bot]

This seems to be related to Hermes. If I disable it, this error goes away. Unfortunately, I have no idea why.

Does disabling Hermes work for you also @RuthlessPotato ?

zentrails avatar Oct 08 '20 12:10 zentrails

I was facing a similar issue with 0.63.2. Then I tried upgrading to 0.64.0. Still no luck in resolving this issue 😢

abhaynpai avatar Mar 17 '21 18:03 abhaynpai

Anyone find any info on this? I've recently hit this updating to 0.64, I cant disable hermes due to react-native-reanimated requiring it..

kyle-ssg avatar Apr 07 '21 12:04 kyle-ssg

Started getting this after updating to RN 0.65.1: I've disabled hermes for now to be able to build. Any updates on why this is happening?

mansdahlstrom1 avatar Sep 15 '21 08:09 mansdahlstrom1

My app has the same issue running on iOS. After upgrading to 0.65.1, I decided to try Hermes. It works fine in dev mode (and does seem to improve performance), but I get the above error when trying to run a release build. I disabled Hermes and the problem went away, so this isn't blocking me for now, but I would like to be able to use Hermes in production.

abram avatar Sep 17 '21 21:09 abram

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

stale[bot] avatar Jan 09 '22 10:01 stale[bot]

这是来自QQ邮箱的假期自动回复邮件。   您好,我最近正在休假中,无法亲自回复您的邮件。我将在假期结束后,尽快给您回复。

RuthlessPotato avatar Jan 09 '22 10:01 RuthlessPotato

any idea ? bug is opening.

hokimtam avatar Aug 24 '22 06:08 hokimtam

这是来自QQ邮箱的假期自动回复邮件。   您好,我最近正在休假中,无法亲自回复您的邮件。我将在假期结束后,尽快给您回复。

RuthlessPotato avatar Aug 24 '22 06:08 RuthlessPotato

same here

samih-sghier avatar Oct 06 '22 05:10 samih-sghier

这是来自QQ邮箱的假期自动回复邮件。   您好,我最近正在休假中,无法亲自回复您的邮件。我将在假期结束后,尽快给您回复。

RuthlessPotato avatar Oct 11 '22 09:10 RuthlessPotato