Solvednativescript cli Android tns debug, crashing when there is a response from server

From @shiv19 on October 27, 2017 17:6

System.err: Calling js method onComplete failed
System.err: Error: Response not found for requestId = 2
System.err: File: "file:///data/data/com.anygofitness.anygopartner/files/app/tns_modules/tns-core-modules/debugger/debugger.js, line: 71, column: 27
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: 	at com.tns.Runtime.callJSMethodNative(Native Method)
System.err: 	at com.tns.Runtime.dispatchCallJSMethodNative(
System.err: 	at com.tns.Runtime.callJSMethodImpl(
System.err: 	at com.tns.Runtime.callJSMethod(
System.err: 	at com.tns.Runtime.callJSMethod(
System.err: 	at com.tns.Runtime.callJSMethod(
System.err: 	at
System.err: 	at org.nativescript.widgets.Async$Http$HttpRequestTask.onPostExecute(
System.err: 	at org.nativescript.widgets.Async$Http$1$
System.err: 	at android.os.Handler.handleCallback(
System.err: 	at android.os.Handler.dispatchMessage(
System.err: 	at android.os.Looper.loop(
System.err: 	at
System.err: 	at java.lang.reflect.Method.invoke(Native Method)
System.err: 	at$
System.err: 	at
ActivityManager: Process com.anygofitness.anygopartner (pid 5414) has died
ActivityManager: cleanUpApplicationRecord -- 5414
^CExecuting after-watch hook from /Users/shiv19/Work/AnyGo/apps/partner/hooks/after-watch/nativescript-dev-sass.js
Stopping sass watch

This part of the app works totally fine when not running in debug mode.
This could be an issue with the debugger

Copied from original issue: NativeScript/NativeScript#4996

13 Answers

✔️Accepted Answer

Marking this as resolved, as per #3187 (comment)

To get the latest android runtime changes run tns platform add android@3.4.0-2017-10-31-1 in your nativescript project.

cc @TheOnlyMatt, @tbsf, @chernov-stas, @yclau

Other Answers:

We found the problem, and prepared a fix which should become available in @3.4.0-2017-10-31-1of the Android runtime later today.


More Issues: