Is Chrome Debugger / DevTools compatible with NativeScript Angular


#1

When using Chrome DevTools my app crashes as soon it makes an API call using NativeScriptHttpClientModule.

Error log

System.err: com.tns.NativeScriptException: 
System.err: Calling js method onComplete failed
System.err: 
System.err: Error: Response not found for requestId = 0
System.err: File: "file:///data/data/com.magpi.nsapp/files/app/tns_modules/tns-core-modules/debugger/debugger.js, line: 71, column: 27
System.err: 
System.err: StackTrace: 
System.err: 	Frame: function:'responseReceived', file:'', line: 71, column: 28
System.err: 	Frame: function:'onRequestComplete', file:'', line: 60, column: 33
System.err: 	Frame: function:'onComplete', file:'', line: 37, column: 13
System.err: 
System.err: 	at com.tns.Runtime.callJSMethodNative(Native Method)
System.err: 	at com.tns.Runtime.dispatchCallJSMethodNative(Runtime.java:1088)
System.err: 	at com.tns.Runtime.callJSMethodImpl(Runtime.java:970)
System.err: 	at com.tns.Runtime.callJSMethod(Runtime.java:957)
System.err: 	at com.tns.Runtime.callJSMethod(Runtime.java:941)
System.err: 	at com.tns.Runtime.callJSMethod(Runtime.java:933)
System.err: 	at com.tns.gen.org.nativescript.widgets.Async_CompleteCallback.onComplete(Async_CompleteCallback.java:12)
System.err: 	at org.nativescript.widgets.Async$Http$HttpRequestTask.onPostExecute(Async.java:585)
System.err: 	at org.nativescript.widgets.Async$Http$1$1.run(Async.java:486)
System.err: 	at android.os.Handler.handleCallback(Handler.java:751)
System.err: 	at android.os.Handler.dispatchMessage(Handler.java:95)
System.err: 	at android.os.Looper.loop(Looper.java:154)
System.err: 	at android.app.ActivityThread.main(ActivityThread.java:6123)
System.err: 	at java.lang.reflect.Method.invoke(Native Method)
System.err: 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:867)
System.err: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:757)
ActivityManager: Process com.magpi.nsapp (pid 8035) has died
ActivityManager: cleanUpApplicationRecord -- 8035

#2

@manojdcoder That seems like a bug we introduced in 3.3, but fixed in 3.4. Could you please get the 3.4 android runtime?


#3

Sure, I will try 3.4 once. Thank you :slight_smile:


#4

Issue seems fixed with {N} 3.4