Details
-
Type:
Bug
-
Status: Closed
-
Priority:
High
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: Release 5.2.0
-
Component/s: iOS
-
Labels:
-
Environment:
Here is a subset of the ti info output. The remainder of the output has been attached ti-info.txt
.Operating SystemName = Mac OS XVersion = 10.10.3Architecture = 64bit# CPUs = 4Memory = 8.0GBNode.jsNode.js Version = 0.10.35npm Version = 1.4.28Titanium CLICLI Version = 3.4.2node-appc Version = 0.2.25Titanium SDKs3.5.1.GAVersion = 3.5.1Install Location = /Users/rob/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GAPlatforms = iphone, mobileweb, android, blackberrygit Hash = 96875c9git Timestamp = 03/05/15 10:08node-appc Version = 0.2.24Here is a subset of the ti info output. The remainder of the output has been attached ti-info.txt . Operating System Name = Mac OS X Version = 10.10.3 Architecture = 64bit # CPUs = 4 Memory = 8.0GB Node.js Node.js Version = 0.10.35 npm Version = 1.4.28 Titanium CLI CLI Version = 3.4.2 node-appc Version = 0.2.25 Titanium SDKs 3.5.1.GA Version = 3.5.1 Install Location = /Users/rob/Library/Application Support/Titanium/mobilesdk/osx/3.5.1.GA Platforms = iphone, mobileweb, android, blackberry git Hash = 96875c9 git Timestamp = 03/05/15 10:08 node-appc Version = 0.2.24
-
Story Points:8
-
Sprint:2015 Sprint 14 Studio, 2015 Sprint 22 SDK
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
|
~/Documents/Titanium_Studio_Workspace/.metadata/.log |
!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
Issue Links
- is duplicated by
-
-
- Closed
-
- links to