java.lang.NullPointerException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • h2. 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. h2. Logs {code:lang=none|title=~/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) {code} h2. 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]
    via by Rob Gabbard,
  • When trying to debug an iOS project, I am not seeing any breakpoints hit in Alloy or Classic projects. I see this on devices and simulators *Steps to reproduce issue* 1. Create a new project 2. Add a breakpoint 3. Debug the project *Expected Results* The breakpoints are hit *Actual Results* The breakpoints are not hit and the below appears in the Studio log *Notes* I see this in the Studio log: {code} !ENTRY com.aptana.js.debug.core 1 0 2016-01-12 14:24:48.254 !MESSAGE Extension version: 5.1.2; protocol v2 !ENTRY com.aptana.js.debug.core 4 4 2016-01-12 14:24:48.268 !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) {code}
    via by Eric Wieber,
  • h2. 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. h2. Logs {code:lang=none|title=~/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) {code} h2. 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]
    via by Rob Gabbard,
  • When trying to debug an iOS project, I am not seeing any breakpoints hit in Alloy or Classic projects. I see this on devices and simulators *Steps to reproduce issue* 1. Create a new project 2. Add a breakpoint 3. Debug the project *Expected Results* The breakpoints are hit *Actual Results* The breakpoints are not hit and the below appears in the Studio log *Notes* I see this in the Studio log: {code} !ENTRY com.aptana.js.debug.core 1 0 2016-01-12 14:24:48.254 !MESSAGE Extension version: 5.1.2; protocol v2 !ENTRY com.aptana.js.debug.core 4 4 2016-01-12 14:24:48.268 !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) {code}
    via by Eric Wieber,
    • 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)
    No Bugmate found.