When debugging is enabled, the application crashes without errors
See original GitHub issueafter upgrading from version 1.13.2 to 2.3.1, the application began to break as soon as you turn on debugging
I added the plugin to babel.config.js added changes to the MainApplication.java but it didn’t help
I have completely cleaned all the caches
rd %localappdata%\Temp\metro-cache /s /q
del %localappdata%\Temp\haste-map*
gradlew clean
rd node_modules /q /s
npm cache clean --force
npm start -- --reset-cache
But nothing helps
here’s what it looks like - https://gyazo.com/3ef2d1377993b55ecd6a27549eb21267
My package.json
{
"name": "svyaznoy-travel",
"version": "9.7.0",
"private": false,
"scripts": {
"android": "react-native run-android",
"ios": "react-native run-ios",
"start": "react-native start",
"test": "jest",
"lint": "eslint src -c .eslintrc.json --ext js,jsx",
"lint-fix": "eslint src -c .eslintrc.json --ext js,jsx --fix",
"debug": "open 'rndebugger://set-debugger-loc?host=localhost&port=8081'"
},
"dependencies": {
"@babel/plugin-transform-runtime": "^7.13.10",
"@ptomasroos/react-native-multi-slider": "^2.2.2",
"@react-native-community/async-storage": "^1.11.0",
"@react-native-community/masked-view": "^0.1.10",
"@react-native-community/netinfo": "^6.0.0",
"@react-native-community/progress-bar-android": "^1.0.4",
"@react-native-community/progress-view": "^1.2.4",
"@react-native-community/push-notification-ios": "^1.8.0",
"@react-native-firebase/app": "^12.1.0",
"@react-native-firebase/crashlytics": "^12.1.0",
"@react-native-firebase/messaging": "^12.1.0",
"@react-navigation/drawer": "^5.12.5",
"@react-navigation/native": "^5.9.4",
"@react-navigation/stack": "^5.14.4",
"@types/lodash": "^4.14.168",
"@types/ptomasroos__react-native-multi-slider": "0.0.2",
"@types/react-redux": "^7.1.16",
"axios": "^0.21.1",
"babel-plugin-module-resolver": "^4.1.0",
"babel-plugin-transform-remove-console": "^6.9.4",
"immutability-helper": "^3.1.1",
"lodash": "^4.17.21",
"moment": "^2.29.1",
"qs": "^6.10.1",
"react": "17.0.2",
"react-native": "0.67.1",
"react-native-add-calendar-event": "^4.0.0",
"react-native-apay": "git+ssh://git@bitbucket.org:svyaznoy-travel/react-native-apay",
"react-native-appsflyer": "^6.3.20",
"react-native-background-timer": "^2.4.1",
"react-native-debugger": "^1.1.0",
"react-native-device-info": "^8.0.8",
"react-native-flash-message": "^0.1.23",
"react-native-gesture-handler": "^1.10.3",
"react-native-google-pay": "^2.1.0",
"react-native-image-picker": "^2.3.3",
"react-native-linear-gradient": "^2.5.6",
"react-native-masked-text": "^1.13.0",
"react-native-pdf": "6.3.0",
"react-native-push-notification": "^7.3.1",
"react-native-reanimated": "^2.3.1",
"react-native-safe-area-context": "^3.2.0",
"react-native-screens": "^3.0.0",
"react-native-sensors": "^7.2.0",
"react-native-svg": "^12.1.0",
"react-native-webview": "^11.3.2",
"react-redux": "^7.2.3",
"redux": "^4.0.5",
"redux-devtools-extension": "^2.13.9",
"redux-thunk": "^2.3.0",
"reselect": "^4.0.0",
"rn-fetch-blob": "^0.12.0",
"sp-react-native-in-app-updates": "^1.1.5",
"tslint": "^6.1.2",
"typescript": "^4.2.3"
},
"devDependencies": {
"@babel/core": "^7.12.9",
"@babel/runtime": "^7.12.5",
"@react-native-community/eslint-config": "^2.0.0",
"@types/react": "^17.0.3",
"@types/react-native": "^0.64.2",
"babel-eslint": "^10.1.0",
"babel-jest": "^26.6.3",
"eslint": "7.14.0",
"eslint-config-airbnb": "^18.2.1",
"eslint-config-prettier": "^8.1.0",
"eslint-plugin-import": "^2.22.1",
"eslint-plugin-jsx-a11y": "^6.4.1",
"eslint-plugin-prettier": "^3.3.1",
"eslint-plugin-react": "^7.23.1",
"jest": "^26.6.3",
"lint-staged": "^10.5.4",
"metro-react-native-babel-preset": "^0.66.2",
"prettier": "2.2.1",
"react-native-typescript-transformer": "^1.2.13",
"react-test-renderer": "17.0.2"
},
"jest": {
"preset": "react-native"
},
"lint-staged": {
"*.{js,jsx}": [
"eslint --fix",
"git add"
]
}
}
Issue Analytics
- State:
- Created 2 years ago
- Comments:23 (3 by maintainers)
Top Results From Across the Web
Basic Debugging of an Application Crash
First, let's discuss terminology. A crash is when something experiences a fault and has no choice but to exit. In the case of...
Read more >debugging crashes app, yet running without debugging doesn't
I have both 2017 and 2019 visual studio. a few days ago a programme i was writing crashed it came up with the...
Read more >c# - How to identify problem when program crashes without ...
If you can reproduce the error, run in debug in Visual Studio and follow the steps to cause the crash. Visual studio will...
Read more >5 Troubleshoot System Crashes
If the fatal error log indicates that the crash occurred in a compiler thread, then it is possible (but not always the case)...
Read more >How to capture and debug .NET application crash dumps in ...
This post aims to be a starting point for a very common situation: debugging a crash dump for a .NET application running on...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
still crashes in 2.8.0
It is crashing for me tooo