React-Native: application gets stuck when debugging if screen is not clicked

My Android App consists of two screens: "Login" and "Dashboard". Logging in is working fine, but the dashboard is a troublemaker.

First problem :

On the login screen, I can open the debug menu, and everything works as expected. When I switch to the Dashboard screen, I can no longer open the menu. If I turned on the Inspector on the login screen, and then go to the dashboard screen, the inspector will disappear.

The second problem :

When I launch the application without an attached debugger, I do not receive data in the control panel, but the input works as usual.

When I attach a debugger, the application "gets stuck" a lot. By clicking on the screen (with the debugger attached), when it is "stuck", the view of the application moves one step further. When I often tap the screen, I get all the data that I expected! There are no breakpoints, and I don’t need to use a debugger at all, it just needs to be attached.

It seems like a copy of iOS is working fine.

What could be wrong here?

Update:

Im using React-Native 0.31.0

Just for clarification . My problem is not a debugger in itself. My problem is that I do not receive any data without a debugger, but I receive all the data when the debugger is connected ( only on Android! ).

+4
1

, , .

React-Native Chrome, javascript. ( ...)

:

iOS- , Android JavaScriptCore, JavaScript, . iOS JSC JIT -

iOS. Chrome JavaScript Chrome WebSocket. V8

, for of array.some.

, , ( - ), , .

. ECMAScript

0

Source: https://habr.com/ru/post/1653437/


All Articles