Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
267 views
in Technique[技术] by (71.8m points)

javascript - React-native 0.61.5 release build android crashed after navigation on a specific route

React-native 0.61.5 android release APK is being crashed every time, when I try to navigate to a specific screen. It is working fine on debug mode (react-native run-android) but after building release signed APK the crash occurs. I've tried many stack overflow answers and suggestions but still unable to resolve the issue.

Here is my ADB logcat -

01-25 12:12:00.006   852   852 D KeyguardClockSwitch: Updating clock: 12?12
01-25 12:12:07.029   583   932 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
01-25 12:12:07.030 27970 28043 W audio_hw_generic: Not supplying enough data to HAL, expected position 78493105 , only wrote 78493089
01-25 12:12:07.208 17214 17247 E ReactNativeJS: Invariant Violation: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
01-25 12:12:07.208 17214 17247 E ReactNativeJS: 1. You might have mismatching versions of React and the renderer (such as React DOM)
01-25 12:12:07.208 17214 17247 E ReactNativeJS: 2. You might be breaking the Rules of Hooks
01-25 12:12:07.208 17214 17247 E ReactNativeJS: 3. You might have more than one copy of React in the same app
01-25 12:12:07.208 17214 17247 E ReactNativeJS: See react-invalid-hook-call for tips about how to debug and fix this problem.
01-25 12:12:07.208 17214 17247 E ReactNativeJS:
01-25 12:12:07.208 17214 17247 E ReactNativeJS: This error is located at:
01-25 12:12:07.216 17214 17247 E ReactNativeJS: Invariant Violation: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
01-25 12:12:07.216 17214 17247 E ReactNativeJS: 1. You might have mismatching versions of React and the renderer (such as React DOM)
01-25 12:12:07.216 17214 17247 E ReactNativeJS: 2. You might be breaking the Rules of Hooks
01-25 12:12:07.216 17214 17247 E ReactNativeJS: 3. You might have more than one copy of React in the same app
01-25 12:12:07.216 17214 17247 E ReactNativeJS: See react-invalid-hook-call for tips about how to debug and fix this problem.
01-25 12:12:07.216 17214 17247 E ReactNativeJS:
01-25 12:12:07.216 17214 17247 E ReactNativeJS: This error is located at:
01-25 12:12:07.244   583   932 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: Invariant Violation: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: 1. You might have mismatching versions of React and the renderer (such as React DOM)
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: 2. You might be breaking the Rules of Hooks
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: 3. You might have more than one copy of React in the same app
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: See react-invalid-hook-call for tips about how to debug and fix this problem.
01-25 12:12:07.253 17214 17248 E unknown:ReactNative:
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: This error is located at:
01-25 12:12:07.253 17214 17248 E unknown:ReactNative:     in x, js engine: hermes, stack:
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: Dr (address at@1:140912
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: useState (address at@1:74995
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: anonymous (address at@1:518750
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: anonymous (address at@1:2282783
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: Ii (address at@1:149619
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: jl (address at@1:164534
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: anonymous@-1
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: an (address at@1:130901
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: Ol (address at@1:164362
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: anonymous (address at@1:162086
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: W (address at@1:242129
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: G (address at@1:242741
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: f (address at@1:243091
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: apply@-1
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: anonymous (address at@1:194742
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: y (address at@1:194024
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: callTimers (address at@1:195796
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: apply@-1
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: value (address at@1:87243
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: anonymous (address at@1:85664
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: value (address at@1:86840
01-25 12:12:07.253 17214 17248 E unknown:ReactNative: value (address at@1:85622
01-25 12:12:07.266 17214 17248 E AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
01-25 12:12:07.266 17214 17248 E AndroidRuntime: Process: com.revolerlife, PID: 17214
01-25 12:12:07.266 17214 17248 E AndroidRuntime: com.facebook.react.common.JavascriptException: Invariant Violation: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
01-25 12:12:07.266 17214 17248 E AndroidRuntime: 1. You might have mismatching versions of React and the renderer (such as React DOM)
01-25 12:12:07.266 17214 17248 E AndroidRuntime: 2. You might be breaking the Rules of Hooks
01-25 12:12:07.266 17214 17248 E AndroidRuntime: 3. You might have more than one copy of React in the same app
01-25 12:12:07.266 17214 17248 E AndroidRuntime: See react-invalid-hook-call for tips about how to debug and fix this problem.
01-25 12:12:07.266 17214 17248 E AndroidRuntime:
01-25 12:12:07.266 17214 17248 E AndroidRuntime: This error is located at:
01-25 12:12:07.266 17214 17248 E AndroidRuntime:     in x, js engine: hermes, stack:
01-25 12:12:07.266 17214 17248 E AndroidRuntime: Dr (address at@1:140912
01-25 12:12:07.266 17214 17248 E AndroidRuntime: useState (address at@1:74995
01-25 12:12:07.266 17214 17248 E AndroidRuntime: anonymous (address at@1:518750
01-25 12:12:07.266 17214 17248 E AndroidRuntime: anonymous (address at@1:2282783
01-25 12:12:07.266 17214 17248 E AndroidRuntime: Ii (address at@1:149619
01-25 12:12:07.266 17214 17248 E AndroidRuntime: jl (address at@1:164534
01-25 12:12:07.266 17214 17248 E AndroidRuntime: anonymous@-1
01-25 12:12:07.266 17214 17248 E AndroidRuntime: an (address at@1:130901
01-25 12:12:07.266 17214 17248 E AndroidRuntime: Ol (address at@1:164362
01-25 12:12:07.266 17214 17248 E AndroidRuntime: anonymous (address at@1:162086
01-25 12:12:07.266 17214 17248 E AndroidRuntime: W (address at@1:242129
01-25 12:12:07.266 17214 17248 E AndroidRuntime: G (address at@1:242741
01-25 12:12:07.266 17214 17248 E AndroidRuntime: f (address at@1:243091
01-25 12:12:07.266 17214 17248 E AndroidRuntime: apply@-1
01-25 12:12:07.266 17214 17248 E AndroidRuntime: anonymous (address at@1:194742
01-25 12:12:07.266 17214 17248 E AndroidRuntime: y (address at@1:194024
01-25 12:12:07.266 17214 17248 E AndroidRuntime: callTimers (address at@1:195796
01-25 12:12:07.266 17214 17248 E AndroidRuntime: apply@-1
01-25 12:12:07.266 17214 17248 E AndroidRuntime: value (address at@1:87243
01-25 12:12:07.266 17214 17248 E AndroidRuntime: anonymous (address at@1:85664
01-25 12:12:07.266 17214 17248 E AndroidRuntime: value (address at@1:86840
01-25 12:12:07.266 17214 17248 E AndroidRuntime: value (address at@1:85622
01-25 12:12:07.266 17214 17248 E AndroidRuntime:
01-25 12:12:07.266 17214 17248 E AndroidRuntime:        at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:71)
01-25 12:12:07.266 17214 17248 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
01-25 12:12:07.266 17214 17248 E AndroidRuntime:        at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:371)
01-25 12:12:07.266 17214 17248 E AndroidRuntime:        at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:150)
01-25 12:12:07.266 17214 17248 E AndroidRuntime:        at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
01-25 12:12:07.266 17214 17248 E AndroidRuntime:        at android.os.Handler.handleCallback(Handler.java:938)
01-25 12:12:07.266 17214 17248 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:99)
01-25 12:12:07.266 17214 17248 E AndroidRuntime:        at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:26)
01-25 12:12:07.266 17214 17248 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:223)
01-25 12:12:07.266 17214 17248 E AndroidRuntime:        at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:225)
01-25 12:12:07.266 17214 17248 E AndroidRuntime:        at java.lang.Thread.run(Thread.java:923)
01-25 12:12:07.279   583  1912 W ActivityTaskManager:   Force finishing activity com.revolerlife/.MainActivity
01-25 12:12:07.281   583 17321 I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
01-25 12:12:07.286   367   433 D goldfish-address-space: allocate: Ask for block of size 0x5b2000
01-25 12:12:07.287   367   433 D goldfish-address-space: allocate: ioctl allocate returned offset 0x3f903c000 size 0x5b3000
01-25 12:12:07.340   583   632 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
01-25 12:12:07.340   583   632 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
01-25 12:12:07.350 17214 17248 I Process : Sending signal. PID: 17214 SIG: 9
01-25 12:12:07.357   583  5496 D HostConnection: HostConnection::get() New Host Connection established 0xae7cb830, tid 5496
01-25 12:12:07.363   583  5496 D HostConnection: HostComposition ext ANDROID_EMU_CHECKSUM_HELPER_v1 ANDROID_EMU_native_sync_v2 ANDROID_EMU_native_sync_v3 ANDROID_EMU_native_sync_v4 ANDROID_EMU_dma_v1 ANDROID_EMU_direct_mem ANDROID_EMU_host_composition_v1 ANDROID_EMU_host_composition_v2 ANDROID_EMU_vulkan ANDROID_EMU_deferred_vulkan_commands ANDROID_EMU_vulkan_null_optional_strings ANDROID_EMU_vulkan_create_resources_with_requirements ANDROID_EMU_YUV_Cache ANDROID_EMU_async_unmap_buffer ANDROID_EMU_vulkan_ignored_handles ANDROID_EMU_vulkan_free_memory_sync GL_OES_vertex_array_object GL_KHR_texture_compression_astc_ldr ANDROID_EMU_gles_max_version_2
01-25 12:12:07.365   583  5496 W OpenGLRenderer: Failed to choose config with EGL_SWAP_BEHAVIOR_PRESERVED, retrying without...
01-25 12:12:07.368   583  5496 D EGL_emulation: eglCreateContext: 0xaee133a0: maj 2 min 0 rcv 2
01-25 12:12:07.384   583   625 I DropBoxManagerService: add tag=system_app_strictmode isTagEnabled=true flags=0x2
01-25 12:12:07.394   583  5496 D EGL_emulation: eglMakeCurrent: 0xaee133a0: ver 2 0 (tinfo 0xb1dcb270) (first time)
01-25 12:12:07.404   583  1904 I WindowManager: WIN DEATH: Window{e7ad92a u0 com.revolerlife/com.revolerlife.MainActivity}
01-25 12:12:07.404   583  1904 W InputDispatcher: Attempted to unregister already unregistered input channel 'e7ad92a com.revolerlife/com.revolerlife.MainActivity (server)'
01-25 12:12:07.404   350   350 I Zygote  : Process 17

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Answer

0 votes
by (71.8m points)
Waitting for answers

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

...