How to debug nativescript throwing "NativeScript caught signal 11." error?
nativescript run in browser
cannot find debug adapter for type'': nativescript
nativescript development environment
I have created a plugin for nativescript ios which was working fine until recently I updated the pod version. Now, when I run the plugin, I get this error: NativeScript caught signal 11.
I have already double checked the typings and there was no typo or parameter mismatch there.
In my case, I have used this command to run the app
tns run ios --bundle --no-hmr --clean --log trace
Error Handling, Learn how to debug NativeScript apps on iOS and Android using Chrome DevTools and Safari AppInspector. Take a look at this NativeScript debugging video for a quick look at what you get. We incorporated Google Chrome developer tools in NativeScript 2.5 and will continue to expand on the feature set with each release. More information about NativeScript debugging can be found in the debugging section of the NativeScript documentation.
This may help you:
NativeScript caught signal 11 while using RadSideDrawer.
I've tried to use
drawerContentSize="drawerSize" instead of correct
[drawerContentSize]="drawerSize" (since drawerSize is a getter in my ts file)
So generally I may assume that it may happen if you forget square brackets (sometimes)
Chrome DevTools Debugging, Error thrown when attempting to run build-related operations for iOS Command gradlew.bat failed with exit code 1. tns run android throws Java (javac) error. Start debugging - starts an application with the debugger enabled; Attach/Detach debugger - attach/detach the debugger to a running application; Start an application with the debugger attached. The following command will build, deploy and run the application with the debugger attached: tns debug android
It seems the signal 11 error is a general error that can be caused by many things that others mentioned in comments.
In my case, my IP was blocked by OneSignal's servers.
Troubleshooting, Start an application with the debugger attached. The following command will build, deploy and run the application with the debugger attached: tns debug android. That's all, now you can debug the Java part of the runtime. Just put a break point and hit debug. If you want to debug the c++ part of the runtime, you should point the debug tool to the debug symbols. From Android Studio: Open the "Run" menu -> "Edit Configurations " -> The following screen will open:
Debug, In my case, I have used this command to run the app tns run ios --bundle --no-hmr --clean --log trace. You go to the debug view (the one on the screenshot), and click the cogwheel icon with the little red exclamation mark (means you don't have a default launch configuration), you will be prompted to choose a debug configuration for Node.js, NativeScript Extension, or another language/extension.
How to debug nativescript throwing "NativeScript caught signal 11 , Possible issues with breakpoint debugging #5000 trying to execute tns debug iOS --debug-brk the debugger cannot attach at all and cli throws: NativeScript debugger was not able to get inspector socket port on device Verify that the app you want to debug is currently running on the device. Procedure. Launch NativeScript Sidekick and open your app. From the left toolbar, select Devices. Click on the Start Debugger button (bug icon) next to the respective device. Use the newly opened Developer Tools dialog to debug your app.
Possible issues with breakpoint debugging · Issue #5000 , This makes any errors thrown by the app impossible to debug. for example, here are messages thrown by my app in the terminal: JS: ERROR Debugging typescript-transpiledTo debug your TypeScript plugin based on the sources, and not the transpiled JS, it is enough to edit the respective tsconfig.json to output sources with inlined maps. That will ensure that the TypeScript sources will also show in the Sources pane, and allow you to debug it.
- Take a look at this thread: github.com/NativeScript/NativeScript/issues/7393 It might be something related to
nativescript-plugin-firebase, you could try to update it to the latest version.
- Thank you. Actually in my case the issue was my IP was blocked by OneSignal's servers. I forgot to update this question.