我的React原生开发环境是在Windows7上;昨天之前运行正常,但加载捆绑包后APK突然报告错误。
错误消息:
Unknown
run
NativeRunnable.java
handleCallback
Handler.java:873
dispatchMessage
Handler.java:99
dispatchMessage
MessageQueueThreadHandler.java:29
loop
Looper.java:193
run
MessageQueueThreadImpl.java:232
run
Thread.java:764
我确实在谷歌上搜索了这个错误,但没有运气。我试着用npm start -- --reset-cache
清除该高速缓存,但错误仍然存在。我找到并尝试了similar posts,但他们的解决方案也不起作用。
错误日志目录:
06-16 14:30:16.144 5885 6735 E unknown:ReactNative: Exception in native call
06-16 14:30:16.144 5885 6735 E unknown:ReactNative: com.facebook.jni.UnknownCppException: Unknown
06-16 14:30:16.144 5885 6735 E unknown:ReactNative: at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
06-16 14:30:16.144 5885 6735 E unknown:ReactNative: at android.os.Handler.handleCallback(Handler.java:873)
06-16 14:30:16.144 5885 6735 E unknown:ReactNative: at android.os.Handler.dispatchMessage(Handler.java:99)
06-16 14:30:16.144 5885 6735 E unknown:ReactNative: at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:29)
06-16 14:30:16.144 5885 6735 E unknown:ReactNative: at android.os.Looper.loop(Looper.java:193)
06-16 14:30:16.144 5885 6735 E unknown:ReactNative: at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:232)
06-16 14:30:16.144 5885 6735 E unknown:ReactNative: at java.lang.Thread.run(Thread.java:764)
06-16 14:30:16.152 5885 6735 E ReactNativeJNI: Attempting to call JS function on a bad application bundle: RCTDeviceEventEmitter.emit()
06-16 14:30:16.155 5885 6735 E unknown:ReactNative: Exception in native call
06-16 14:30:16.155 5885 6735 E unknown:ReactNative: java.lang.RuntimeException: Attempting to call JS function on a bad application bundle: RCTDeviceEventEmitter.emit()
06-16 14:30:16.155 5885 6735 E unknown:ReactNative: at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
06-16 14:30:16.155 5885 6735 E unknown:ReactNative: at android.os.Handler.handleCallback(Handler.java:873)
06-16 14:30:16.155 5885 6735 E unknown:ReactNative: at android.os.Handler.dispatchMessage(Handler.java:99)
06-16 14:30:16.155 5885 6735 E unknown:ReactNative: at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:29)
06-16 14:30:16.155 5885 6735 E unknown:ReactNative: at android.os.Looper.loop(Looper.java:193)
06-16 14:30:16.155 5885 6735 E unknown:ReactNative: at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:232)
06-16 14:30:16.155 5885 6735 E unknown:ReactNative: at java.lang.Thread.run(Thread.java:764)
06-16 14:30:16.155 5885 6735 E ReactNativeJNI: Attempting to call JS function on a bad application bundle: AppRegistry.runApplication()
06-16 14:30:16.156 5885 6735 E unknown:ReactNative: Exception in native call
06-16 14:30:16.156 5885 6735 E unknown:ReactNative: java.lang.RuntimeException: Attempting to call JS function on a bad application bundle: AppRegistry.runApplication()
06-16 14:30:16.156 5885 6735 E unknown:ReactNative: at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
06-16 14:30:16.156 5885 6735 E unknown:ReactNative: at android.os.Handler.handleCallback(Handler.java:873)
06-16 14:30:16.156 5885 6735 E unknown:ReactNative: at android.os.Handler.dispatchMessage(Handler.java:99)
06-16 14:30:16.156 5885 6735 E unknown:ReactNative: at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:29)
06-16 14:30:16.156 5885 6735 E unknown:ReactNative: at android.os.Looper.loop(Looper.java:193)
06-16 14:30:16.156 5885 6735 E unknown:ReactNative: at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:232)
06-16 14:30:16.156 5885 6735 E unknown:ReactNative: at java.lang.Thread.run(Thread.java:764)
06-16 14:30:16.165 5885 5885 D ReactNative: CatalystInstanceImpl.destroy() start
06-16 14:30:16.181 1571 1571 D gralloc_ranchu: gralloc_alloc: Creating ashmem region of size 3936256
06-16 14:30:16.187 1571 1571 D gralloc_ranchu: gralloc_alloc: Creating ashmem region of size 3936256
06-16 14:30:16.189 5885 6734 D ReactNative: CatalystInstanceImpl.destroy() end
06-16 14:30:16.193 1571 1571 D gralloc_ranchu: gralloc_alloc: Creating ashmem region of size 3936256
06-16 14:30:16.224 5885 5885 D ReactNative: CatalystInstanceImpl.destroy() start
06-16 14:30:16.224 5885 5885 D ReactNative: CatalystInstanceImpl.destroy() start
06-16 14:30:16.233 5885 5885 W unknown:ReactNative: Tried to enqueue runnable on already finished thread: 'js... dropping Runnable.
06-16 14:30:16.233 5885 5885 W MessageQueue: Handler (com.facebook.react.bridge.queue.MessageQueueThreadHandler) {ef3c15} sending message to a Handler on a dead thread
06-16 14:30:16.233 5885 5885 W MessageQueue: java.lang.IllegalStateException: Handler (com.facebook.react.bridge.queue.MessageQueueThreadHandler) {ef3c15} sending message to a Handler on a dead thread
06-16 14:30:16.233 5885 5885 W MessageQueue: at android.os.MessageQueue.enqueueMessage(MessageQueue.java:546)
06-16 14:30:16.233 5885 5885 W MessageQueue: at android.os.Handler.enqueueMessage(Handler.java:745)
06-16 14:30:16.233 5885 5885 W MessageQueue: at android.os.Handler.sendMessageAtTime(Handler.java:697)
06-16 14:30:16.233 5885 5885 W MessageQueue: at android.os.Handler.sendMessageDelayed(Handler.java:667)
06-16 14:30:16.233 5885 5885 W MessageQueue: at android.os.Handler.post(Handler.java:395)
06-16 14:30:16.233 5885 5885 W MessageQueue: at com.facebook.react.bridge.queue.MessageQueueThreadImpl.runOnQueue(MessageQueueThreadImpl.java:70)
06-16 14:30:16.233 5885 5885 W MessageQueue: at com.facebook.react.bridge.ReactContext.runOnJSQueueThread(ReactContext.java:306)
06-16 14:30:16.233 5885 5885 W MessageQueue: at com.facebook.react.uimanager.events.EventDispatcher$ScheduleDispatchFrameCallback.doFrame(EventDispatcher.java:302)
06-16 14:30:16.233 5885 5885 W MessageQueue: at com.facebook.react.modules.core.ReactChoreographer$ReactChoreographerDispatcher.doFrame(ReactChoreographer.java:166)
06-16 14:30:16.233 5885 5885 W MessageQueue: at com.facebook.react.modules.core.ChoreographerCompat$FrameCallback$1.doFrame(ChoreographerCompat.java:84)
06-16 14:30:16.233 5885 5885 W MessageQueue: at android.view.Choreographer$CallbackRecord.run(Choreographer.java:947)
06-16 14:30:16.233 5885 5885 W MessageQueue: at android.view.Choreographer.doCallbacks(Choreographer.java:761)
06-16 14:30:16.233 5885 5885 W MessageQueue: at android.view.Choreographer.doFrame(Choreographer.java:693)
06-16 14:30:16.233 5885 5885 W MessageQueue: at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:935)
06-16 14:30:16.233 5885 5885 W MessageQueue: at android.os.Handler.handleCallback(Handler.java:873)
06-16 14:30:16.233 5885 5885 W MessageQueue: at android.os.Handler.dispatchMessage(Handler.java:99)
06-16 14:30:16.233 5885 5885 W MessageQueue: at android.os.Looper.loop(Looper.java:193)
06-16 14:30:16.233 5885 5885 W MessageQueue: at android.app.ActivityThread.main(ActivityThread.java:6669)
06-16 14:30:16.233 5885 5885 W MessageQueue: at java.lang.reflect.Method.invoke(Native Method)
06-16 14:30:16.233 5885 5885 W MessageQueue: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
06-16 14:30:16.233 5885 5885 W MessageQueue: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
06-16 14:30:16.251 2042 2042 I GoogleInputMethod: onFinishInput() : Dummy InputConnection bound
06-16 14:30:16.252 2042 2042 I GoogleInputMethod: onStartInput() : Dummy InputConnection bound
06-16 14:30:16.255 5885 5902 D EGL_emulation: eglMakeCurrent: 0xe5dc78a0: ver 2 0 (tinfo 0xe7055d70)
- 编辑 *:我已从上述日志中排除了与修复错误时相同的部件。
1条答案
按热度按时间wwtsj6pe1#
调试后;禁用
@babel/plugin-transform-arrow-functions
插件(版本7.2.0
),然后清除该高速缓存(如another answer中的建议)为我修复了它:步骤:
1.例如,禁用
@babel/plugin-transform-arrow-functions
插件,我只是在babel.config.js
文件中将其注解掉,如下所示:1.如果打包程序已在运行,请使用进程管理器关闭和/或终止它
1.对于
react-native
init
方法(没有expo
),运行:(使用
expo-cli
的用户应该运行expo start -c
,而不是上面的命令)上面提到的命令对我来说等于删除
%temp%/metro-cache
目录。但仍然,不能伤害删除
~/.babel.json
文件(在Windows%userProfile%/.babel.json
文件)作为建议here,我的意思是,我已经测试和上述命令没有删除和/或更改.babel.json
文件.修复后的Logcat:
为了有一个更干净的日志,我已经从上面排除了与错误出现时相同的部分。