Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-19234] iOS debugger connection refused with SDKs 3.5.0 and 3.5.1

GitHub Issuen/a
TypeBug
PriorityHigh
StatusClosed
ResolutionFixed
Resolution Date2015-11-03T18:49:51.000+0000
Affected Version/sn/a
Fix Version/sRelease 5.2.0
ComponentsiOS
Labelsdebugger-ios, ios, notable, sdk, studio
ReporterRob Gabbard
AssigneeChee Kiat Ng
Created2015-05-04T10:29:06.000+0000
Updated2016-02-21T19:49:52.000+0000

Description

iOS debugger connection refused with SDKs 3.5.0 and 3.5.1

After upgrading from SDK 3.4.1 to 3.5.0 (and 3.5.1), I can no longer debug under iOS. The iOS emulator starts and my application is loaded and runs ok. However, although Studio switches to the debug perspective, any breakpoints I set are ignored and I have no debugging capabilities. The only symptom indicating any issue are the series of messages like the one shown below in the Studio log file. Reverting to SDK 3.4.1 in my tiapp.xml restores the debugging capabilities.

Logs

!ENTRY com.aptana.js.debug.core 4 4 2015-05-04 05:30:38.465
!MESSAGE 
!STACK 0
java.lang.NullPointerException
	at org.eclipse.core.runtime.Path.fromPortableString(Path.java:103)
	at com.appcelerator.titanium.core.launching.TitaniumAppURIMapper.resolve(TitaniumAppURIMapper.java:71)
	at com.aptana.js.debug.core.internal.model.JSDebugTarget.resolveSourceFile(JSDebugTarget.java:2199)
	at com.aptana.js.debug.core.internal.model.JSDebugTarget.handleScripts(JSDebugTarget.java:730)
	at com.aptana.js.debug.core.internal.model.JSDebugTarget.access$6(JSDebugTarget.java:703)
	at com.aptana.js.debug.core.internal.model.JSDebugTarget$DebugConnectionHandler.handleMessage(JSDebugTarget.java:2355)
	at com.aptana.js.debug.core.internal.model.DebugConnection.handleMessage(DebugConnection.java:228)
	at com.aptana.js.debug.core.internal.model.DebugConnection.access$3(DebugConnection.java:223)
	at com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:155)

Discussions

Here is a Q&A discussion where several other developers are reporting a similar issue... [http://developer.appcelerator.com/question/181417/debug-connection-refused-with-sdk-35-and-ios]

Attachments

FileDateSize
2015-Jun-07-iosdebugger.log2015-06-07T11:42:00.000+000015191
2015-Jun-07-StudioLogFile.log2015-06-07T11:42:00.000+000035225
DiagTest.txt2015-05-19T17:58:01.000+000039649
logfile.txt2015-05-19T17:58:19.000+00005220213
ti-info.txt2015-05-04T10:14:55.000+00008651
TiInfo-Config.txt2015-05-19T17:58:14.000+000028066

Comments

  1. Marco Cota 2015-05-19

    Softerware is getting the same issue, as a note this is only happening for them in one of their apps (their main app) im including the logs and tiConfig files from their enviroment
  2. Ingo Muschenetz 2015-06-01

    Let's start by fixing the NPE. Can we reproduce this in-house?
  3. Praveen Innamuri 2015-06-03

    [~kkolipaka] Can you take a look into this ?
  4. Kondal Kolipaka 2015-06-04

    https://github.com/aptana/studio3/pull/328
  5. Praveen Innamuri 2015-06-06

    [~egomez] We capture the debug protocol communication in the logs at the file <workspace>/.metadata/.plugins/com.appcelerator.titanium.ios.core/logs/iosdebugger.log. Default workspace for Appcelerator Studio is /Users/<user>/Documents/Appcelerator_Studio_Workspace. Can you ask the customer to send this file after recreating the problem ? As we were unable to reproduce the problem here, it will give us insight to understand why we were not receiving the correct path of the file from SDK debugger.
  6. Rob Gabbard 2015-06-07

    I have attached both the Studio log file and the iosdebugger.log from a session exhibiting the problem. Before running the iOS emulator, I cleaned the project and cleared both log files. This is with the Titanium SDK set to 3.5.1.GA. In this particular instance, I had a breakpoint set at line 318 of the source controller app/alloy/controllers/map.js which mapped to line 358 in it's generated counterpart at Resources/iphone/alloy/controllers/map.js.
  7. Kondal Kolipaka 2015-06-08

    Space in the project name is causing this issue. I could reproduce the issue If I create a project with a space in it.
       [28:16.520] Recv: >log*out*[DEBUG] Loading: /Users/rob/Library/Developer/CoreSimulator/Devices/AAC8D00D-62F1-49DD-9814-24C691E2753C/data/Containers/Bundle/Application/E6CFD2F4-E3C6-4738-9166-231397890EAA/Riverbend Music Center.app/app.js, Resource: app_js<
       [28:16.532] Recv: >scripts*created*1|app:.app/app.js||1|9<
       
    _/Riverbend Music Center.app/app.js_ converted as _app:.app/app.js_ rather than _app:/app.js_ [~pinnamuri] Looks like iOS team has to look into it.
  8. Praveen Innamuri 2015-06-08

    [~robgabbard] Thanks for providing the logs. Until we address this issue, as a workaround, would it be possible to rename the project to remove spaces in order to debug the app ?
  9. Rob Trueman 2015-06-08

    That's not the case with our app, DPMobile. There are no spaces in the name. I believe Marco sent all my information, but if you need anything else I'm happy to send it along. Rob Trueman SofterWare, Inc.
  10. Praveen Innamuri 2015-06-08

  11. Rob Trueman 2015-06-10

    I give up... how do I attach/upload the file? Also, my project is a classic app. I set a breakpoint at line 2516 of the app.js file (this project was mostly all app.js when I got it) and ran it in the simulator as an iPhone 6 (v. 8.3). It never stopped. Project is set to 3.5.1 GA.
  12. Rob Trueman 2015-06-11

    While publishing our latest demo to the app store yesterday and showing another developer the build directory, I was shocked to see the Xcode project named "DP Mobile", not "DPMobile" as I had expected from the Appcelerator project. This morning I renamed to DPMobile and tested debugging. It worked successfully. For me, I can rename the project until the permanent solution is available. Thanks for all the support, folks! Rob
  13. Kondal Kolipaka 2015-07-16

    [~cng][~penrique] Issue is still there with 4.0 GA builds If project is having a space between the project name. The resource uri is returned wrongly from iOS debugger to studio. Could you please take a look at it ? Attached logs and error reported still valid even today with GA builds. Do let us know If we have to do something from studio.
  14. Chee Kiat Ng 2015-10-26

    Debugger PR: https://github.com/appcelerator/titanium_debugger/pull/38 TIMOB Master PR: https://github.com/appcelerator/titanium_mobile/pull/7345
  15. Eric Wieber 2016-02-21

    Verified fixed, using: MacOS 10.11.3 (15D21) Studio 4.5.0.201602170821 Ti SDK 5.2.0.v20160220080449 Appc NPM 4.2.3-2 Appc CLI 5.2.0-269 Alloy 1.7.33 Xcode 7.2 (7C68) Was able to successfully debug multiple Alloy and Classic apps with and without spaces in the name across iOS simulators and devices and the QE test suite.

JSON Source