1

我面臨着我的反應本機應用程序的問題,我不知道如何進行調試。如何着手調試反應本機應用程序?

我通過我的時間來解決不同版本之間的不匹配:我使用的軟件包,不同的升級/更新(軟件包,反應本機,Android Studio等),依賴關係比實際代碼或更正我的代碼。

這真的令人沮喪,我覺得我做錯了,或者因爲這些問題而陷入困境。

這裏我就我目前的問題的信息:

消息構建搖籃

enter image description here

的logcat的:

            --------- beginning of system 
08-02 14:10:03.784 758-793/? E/BatteryStatsService: no controller energy info supplied 
08-02 14:10:03.784 758-793/? E/BatteryStatsService: no controller energy info supplied 
08-02 14:10:03.813 758-793/? E/BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0} 
08-02 14:12:03.754 758-793/? E/BatteryStatsService: no controller energy info supplied 
08-02 14:12:03.754 758-793/? E/BatteryStatsService: no controller energy info supplied 
08-02 14:12:03.796 758-793/? E/BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0} 
08-02 14:12:13.757 758-793/? E/BatteryStatsService: no controller energy info supplied 
08-02 14:12:13.758 758-793/? E/BatteryStatsService: no controller energy info supplied 
08-02 14:12:13.800 758-793/? E/BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0} 
08-02 14:34:43.308 249-396/? E/qepo: is_quarter_epo_valid: Read QEPO file failed 
08-02 14:34:43.328 249-396/? E/qepo: is_quarter_epo_valid: Read QEPO file failed 
08-02 14:34:43.347 249-396/? E/qepo: is_quarter_epo_valid: Read QEPO file failed 
08-02 14:34:43.947 237-329/? E/agps: [agps] ERR: [AGPS] update_imsi_to_supl_swip IMSI is invalid 
08-02 14:34:43.979 237-344/? E/agps: [agps] ERR: [SUPL_CONN_ADP] is_socket_valid socket_fds[s]=-1 is invalid 
08-02 14:34:43.980 237-344/? E/agps: [agps] ERR: [SUPL_CONN_ADP] soc_close s=0 is invalid 
08-02 14:34:45.481 758-7252/? E/Sensors: handleToDriver handle(0) 
08-02 14:34:45.481 758-7252/? E/Sensors: new setDelay handle(0),ns(66667000)m, error(0), index(2) 
08-02 14:34:52.228 249-395/? E/epo: mtk_gps_epo_file_update: Update EPOHAL.DAT error 
08-02 14:34:58.495 14056-14056/? E/PQ: [PQ][PQWhiteList] libwlparser.so is absent 
08-02 14:35:02.268 249-395/? E/epo: mtk_gps_epo_file_update: Update EPOHAL.DAT error 
08-02 14:35:04.818 249-396/? E/qepo: is_quarter_epo_valid: Read QEPO file failed 
08-02 14:35:04.819 249-405/? E/MNLD: fsm_gps_state_started: fsm_gps_state_started() data1=1,data2=0,data3=0x0 
08-02 14:35:04.819 249-405/? E/MNLD: fsm_gps_state_started: fsm_gps_state_stopping() unexpected event=3 
08-02 14:35:04.846 249-396/? E/qepo: is_quarter_epo_valid: Read QEPO file failed 
08-02 14:35:04.890 249-396/? E/qepo: is_quarter_epo_valid: Read QEPO file failed 
08-02 14:35:04.928 249-396/? E/qepo: is_quarter_epo_valid: Read QEPO file failed 
08-02 14:35:04.957 249-396/? E/qepo: is_quarter_epo_valid: Read QEPO file failed 
08-02 14:35:04.996 249-396/? E/qepo: is_quarter_epo_valid: Read QEPO file failed 
08-02 14:35:05.026 249-396/? E/qepo: is_quarter_epo_valid: Read QEPO file failed 
08-02 14:35:05.051 758-758/? E/PermissionMonitor: can't find permission:android.permission.CHANGE_NETWORK_STATE 
08-02 14:35:05.051 758-758/? E/PermissionMonitor: can't find permission:android.permission.CONNECTIVITY_INTERNAL 
08-02 14:35:05.055 249-396/? E/qepo: is_quarter_epo_valid: Read QEPO file failed 
08-02 14:35:05.081 249-396/? E/qepo: is_quarter_epo_valid: Read QEPO file failed 
08-02 14:35:05.112 249-396/? E/qepo: is_quarter_epo_valid: Read QEPO file failed 
08-02 14:35:05.141 758-1116/? E/CellLocation: create GsmCellLocation 
08-02 14:35:05.145 249-396/? E/qepo: is_quarter_epo_valid: Read QEPO file failed 
08-02 14:35:05.148 758-1116/? E/GnssLocationProvider: Error getting cell location info. 
08-02 14:35:05.530 14127-14127/? E/MPlugin: Unsupported class: com.mediatek.common.telephony.IOnlyOwnerSimSupport 
08-02 14:35:05.647 237-329/? E/agps: [agps] ERR: [AGPS] update_imsi_to_supl_swip IMSI is invalid 
08-02 14:35:05.670 237-344/? E/agps: [agps] ERR: [SUPL_CONN_ADP] is_socket_valid socket_fds[s]=-1 is invalid 
08-02 14:35:05.671 237-344/? E/agps: [agps] ERR: [SUPL_CONN_ADP] soc_close s=0 is invalid 
08-02 14:35:05.768 3794-14020/? E/NetworkScheduler.SR: Invalid parameter app 
08-02 14:35:05.768 3794-14020/? E/NetworkScheduler.SR: Invalid package name : Perhaps you didn't include a PendingIntent in the extras? 
08-02 14:35:05.783 3794-14018/? E/MPlugin: Unsupported class: com.mediatek.common.telephony.IOnlyOwnerSimSupport 
08-02 14:35:05.789 3810-8754/? E/Drive.UninstallOperation: Package still installed com.accessidico 
08-02 14:35:05.977 12587-12587/? E/Finsky: [1] com.google.android.finsky.wear.bl.a(847): onConnectionFailed: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null} 
08-02 14:35:06.296 3794-14020/? E/NetworkScheduler.SR: Invalid parameter app 
08-02 14:35:06.296 3794-14020/? E/NetworkScheduler.SR: Invalid package name : Perhaps you didn't include a PendingIntent in the extras? 
08-02 14:35:11.977 249-405/? E/MNLD: fsm_gps_state_started: fsm_gps_state_started() data1=0,data2=0,data3=0x0 
08-02 14:35:12.026 249-405/? E/MNLD: fsm_gps_state_stopping: fsm_gps_state_stopping() data1=0,data2=0,data3=0x0 
08-02 14:35:12.356 249-395/? E/epo: mtk_gps_epo_file_update: Update EPOHAL.DAT error 
08-02 14:35:16.587 14219-14219/? E/PQ: [PQ][PQWhiteList] libwlparser.so is absent 
08-02 14:35:16.956 9224-13999/? E/AudioRecord-JNI: Error -4 during AudioRecord native read 
08-02 14:35:17.235 758-2532/? E/Sensors: handleToDriver handle(0) 
08-02 14:35:17.236 758-2532/? E/Sensors: new setDelay handle(0),ns(66667000)m, error(0), index(2) 
08-02 14:35:17.470 3794-3794/? E/ActivityThread: Service com.google.android.location.places.service.PlaceDetectionAsyncService has leaked IntentReceiver amt[email protected] that was originally registered here. Are you missing a call to unregisterReceiver()? 
               android.app.IntentReceiverLeaked: Service com.google.android.location.places.service.PlaceDetectionAsyncService has leaked IntentReceiver [email protected] that was originally registered here. Are you missing a call to unregisterReceiver()? 
                at android.app.LoadedApk$ReceiverDispatcher.<init>(LoadedApk.java:1201) 
                at android.app.LoadedApk.getReceiverDispatcher(LoadedApk.java:951) 
                at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1314) 
                at android.app.ContextImpl.registerReceiver(ContextImpl.java:1294) 
                at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:593) 
                at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:593) 
                at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:593) 
                at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:593) 
                at amrb.run(:com.google.android.gms:4414) 
                at android.os.Handler.handleCallback(Handler.java:836) 
                at android.os.Handler.dispatchMessage(Handler.java:103) 
                at android.os.Looper.loop(Looper.java:203) 
                at android.os.HandlerThread.run(HandlerThread.java:61) 
08-02 14:35:17.473 3794-14255/? E/Places: IllegalArgumentException whilst unregistering receiver. Was SignalManager stopped before being started? 
08-02 14:35:19.818 14229-14268/? E/ReactNativeJS: undefined is not an object (evaluating 'NativeReactModule.startApp') 
08-02 14:35:19.877 14229-14268/? E/ReactNativeJS: Application AccessiDico has not been registered. 

                Hint: This error often happens when you're running the packager (local dev server) from a wrong folder. For example you have multiple apps and the packager is still running for the app you were working on before. 
                If this is the case, simply kill the old packager instance (e.g. close the packager terminal window) and start the packager in the correct app folder (e.g. cd into app folder and run 'npm start'). 

                This error can also happen due to a require() error during initialization or failure to call AppRegistry.registerComponent. 



                [ 08-02 14:35:19.878 14229:14280 D/   ] 
                [Posix_connect Debug]Process com.accessidico :8081 
08-02 14:35:22.406 249-395/? E/epo: mtk_gps_epo_file_update: Update EPOHAL.DAT error 

和錯誤我上了我的設備(這是李nked的反應本地導航包:https://wix.github.io/react-native-navigation/#/):

不確定是不是(評估「NativeReactModule.startApp」)

所以我想,超出了我的問題的對象,什麼是「清單「調試類似的東西?

什麼是相關?什麼不是?

我應該在哪裏研究解決方案?

P.S:我已經按照logcat中顯示的提示沒有成功。

在此先感謝。

+0

已刪除並重新安裝了'node_modules'的反應本地導航包後?有時候這有幫助。 –

+0

我剛剛嘗試過,它仍然是相同的 –

+0

我遇到與React本地導航相同的問題 - 也沒有線索從哪裏開始。還有另一個類似的問題出現: [https://stackoverflow.com/questions/45868912/] –

回答

0

這個問題是因爲它無法找到本機模塊,在Android的安裝需要遵循以下steps

相關問題