Titanium JIRA Archive
Appcelerator Community (AC)

[AC-6393] Debugger Issue on the latest Titanium SDK 8

GitHub Issuen/a
TypeBug
Priorityn/a
StatusOpen
ResolutionUnresolved
Affected Version/sn/a
Fix Version/sn/a
Componentsn/a
Labelsn/a
ReporterKai Lu
AssigneeFazlul Haque
Created2019-10-04T02:58:37.000+0000
Updated2019-12-23T14:47:25.000+0000

Description

We are using the debugger tool for android and iOS as recommended from the guide docs: https://docs.appcelerator.com/platform/latest/?mobile=/guide/Debugging_iOS_Apps_with_3rd-party_Tools-section-src-49160781_DebuggingiOSAppswith3rd-partyTools-Enableuse-jscore-framework https://docs.appcelerator.com/platform/latest/?mobile=/guide/Debugging_Android_Apps_with_3rd-party_Tools They were working fine on the SDK 7.4.1 for the iOS and 7.5.0 for the android but once we updated to the latest SDK 8 it stopped working and got stuck at the splash screen while debugging to my Samsung device. I was wondering if you could help fix this issue asap since our development team is highly relying on this feature/tool to debug and we are also hoping to support the latest the greatest Titanium SDK as well. Thanks!

Comments

  1. Rakhi Mitro 2019-10-04

    Hello, Thanks for letting us know. Are you experiencing this issue also in 8.2.0.GA? Can you please verify this and let us know?
  2. Kai Lu 2019-10-04

    Hi Rakhi, Yes, I am having the issue on the 8.2.0.GA when debugging the app on the device, the simulators work fine though. Here is the console log: -- Start application log ----------------------------------------------------- [INFO] :   Forwarding host port 12345 to device for debugging [INFO] :   Project built successfully in 58s 766ms [ERROR] :  Zygote: isWhitelistProcess - Process is Whitelisted [WARN] :   SELinux: SELinux selinux_android_compute_policy_index : Policy Index[2], Con:u:r:zygote:s0 RAM:SEPF_SM-G930F_8.0.0_0018, [-1 -1 -1 -1 0 1] [INFO] :   SELinux: SELinux: seapp_context_lookup: seinfo=untrusted, level=s0:c512,c768, pkgname=com.trimble.workzone [INFO] :   zygote64: no shared libraies, dex_files: 1 [INFO] :   TiApplication: (main) [0,0] checkpoint, app created. [INFO] :   MultiDex: VM with version 2.1.0 has multidex support [INFO] :   MultiDex: Installing application [INFO] :   MultiDex: VM has multidex support, MultiDex support library is disabled. [INFO] :   TiApplication: (main) [128,128] Analytics have been disabled [WARN] :   JSDebugger: (main) [209,337] Debugger listening on ws://127.0.0.1:12345/5486aee4-0a97-423d-bc52-db636ebb1b0e [WARN] :   JSDebugger: (main) [1,338] To connect Chrome DevTools, open Chrome to chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:12345/5486aee4-0a97-423d-bc52-db636ebb1b0e [WARN] :   JSDebugger: (main) [0,338] Waiting for debugger to connect for next 60 seconds... [WARN] :   JSDebugger: (WebSocketWorker-40980) [1078,1416] Debugger client connected [WARN] :   JSDebugger: (WebSocketWorker-40981) [44479,45895] Debugger client connected [WARN] :   W/System.err: Uncaught exception in thread "WebSocketWorker-40981":java.lang.InternalError: Thread starting during runtime shutdown [WARN] :   W/System.err: at java.lang.Thread.nativeCreate(Native Method) [WARN] :   W/System.err: at java.lang.Thread.start(Thread.java:733) [WARN] :   W/System.err: at org.appcelerator.kroll.runtime.v8.JSDebugger$InspectorAgent.onOpen(JSDebugger.java:172) [WARN] :   W/System.err: at org.java_websocket.server.WebSocketServer.onWebsocketOpen(WebSocketServer.java:541) [WARN] :   W/System.err: at org.java_websocket.WebSocketImpl.open(WebSocketImpl.java:701) [WARN] :   W/System.err: at org.java_websocket.WebSocketImpl.decodeHandshake(WebSocketImpl.java:240) [WARN] :   W/System.err: at org.java_websocket.WebSocketImpl.decode(WebSocketImpl.java:161) [WARN] :   W/System.err: at org.java_websocket.server.WebSocketServer$WebSocketWorker.run(WebSocketServer.java:781)
  3. Kai Lu 2019-10-04

    When debugging on the iOS device, the app gets successfully deployed but when I tap on the app to launch it there is an error pop up in the vs code studio: [titanium-extension] Error processing "launch": Unable to discover app
  4. Kai Lu 2019-10-04

    OK, so it seems like after I updating my Xcode to 11 and reinstalled all the required node packages then the above error disappeared. Now that iOS device debugging starts working it leaves the problem only on the Android.
  5. Fazlul Haque 2019-12-23

    [~kenjorai], Thanks for your feedback. Would you please share us details about the android issue or you can raise a different ticket for it by which we track that ticket properly? Thanks

JSON Source