issuekey
stringlengths 8
11
| title
stringlengths 16
187
| description
stringlengths 10
20k
⌀ | storypoint
int64 1
40
| split_mark
stringclasses 1
value |
|---|---|---|---|---|
TISTUD-1431
|
Studio: Launching debugger successfully produces unexpected log entries.
|
Description: After a debugger session launch I noted that the log contained an entry repeated many times that was unexpected. This occurs when the debugger launch is working as expected and in cases where the debugger fails to connect. The log from a good debugger launch: {code:title=.log} !ENTRY com.aptana.js.debug.core 1 0 2012-03-26 13:55:51.772 !MESSAGE Extension version: 3.0.0.1329178773; protocol v1 !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:55:54.394 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:55:55.395 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:55:56.397 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:55:57.398 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:55:58.400 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:55:59.401 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:00.403 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:01.405 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:02.406 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:03.407 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:04.408 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:05.410 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:06.411 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:07.412 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:08.413 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:09.414 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:10.416 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:11.417 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:12.418 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:13.420 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:14.421 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:15.423 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:16.424 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:17.425 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read timed out java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107) sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93) java.io.InputStreamReader.read(InputStreamReader.java:151) com.aptana.js.debug.core.internal.model.DebugConnection.readMessage(DebugConnection.java:271) com.aptana.js.debug.core.internal.model.DebugConnection$1.run(DebugConnection.java:94) !ENTRY com.aptana.js.debug.core 4 4 2012-03-26 13:56:18.427 !MESSAGE Read timed out !STACK 0 java.net.SocketTimeoutException: Read ti...
| 8 |
train
|
TISTUD-1432
|
Titanium Studio: Preferences: Titanium: cannot save Titanium SDK home path
|
When editing the titanium sdk home path, cannot save changes. The workaround is to click 'restore defaults', make the changes, then save. Steps to Reproduce: 1. Copy Application Support/Titanium (the sdk super-folder) to another location. 2. In studio, preferences, change the titanium sdk home to this new location. Expected Result: Should be able to save changes. Actual Result: Cannot save changes. Must restore defaults, then edit and save changes.
| 5 |
train
|
TISTUD-1435
|
Android module projects should have better validation for name and id
|
When creating a mobile module project, we should be more strict about the name validation and the module-id validation. * Names should not contain any hyphens (and other special characters that can 'kill' the generated JavaScript example, or the packaging). Suggest we use the javascript identifier rules here. * module-id should follow the Java conventions for package names (just like we do with Android).
| 8 |
train
|
TISTUD-1436
|
Packaging of Android module fails to copy built module to destination
|
# Create a new Android mobile module project # Attempt to package it for a project or a folder on disk (it probably also fails for the Titanium SDK) # It appears to work, but fails to copy the file to the destination, with the following error: {code} (Build 1.0.0.qualifier) [ERROR] Could not move: /Users/ingo/Documents/Aptana_Studio_3_Workspace/asdasd/dist/app.bapp-android-0.1.zip. org.eclipse.core.runtime.CoreException: Could not move: /Users/ingo/Documents/Aptana_Studio_3_Workspace/asdasd/dist/app.bapp-android-0.1.zip. org.eclipse.core.internal.filesystem.Policy.error(Policy.java:55) org.eclipse.core.filesystem.provider.FileStore.move(FileStore.java:415) org.eclipse.core.internal.filesystem.local.LocalFile.move(LocalFile.java:352) com.appcelerator.titanium.mobile.module.launching.ModulePackagerUtil.processModule(ModulePackagerUtil.java:75) com.appcelerator.titanium.mobile.module.launching.AndroidModulePackageLaunchConfigurationDelegate$1.run(AndroidModulePackageLaunchConfigurationDelegate.java:104) java.lang.Thread.run(Thread.java:680) Caused by: org.eclipse.core.runtime.CoreException: Could not write file: /Users/ingo/Documents/Aptana_Studio_3_Workspace/testMobile/dist/app.bapp-android-0.1.zip. org.eclipse.core.internal.filesystem.Policy.error(Policy.java:55) org.eclipse.core.internal.filesystem.local.LocalFile.openOutputStream(LocalFile.java:391) org.eclipse.core.filesystem.provider.FileStore.copyFile(FileStore.java:221) org.eclipse.core.filesystem.provider.FileStore.copy(FileStore.java:143) org.eclipse.core.internal.filesystem.local.LocalFile.copy(LocalFile.java:111) org.eclipse.core.filesystem.provider.FileStore.move(FileStore.java:410) ... 4 more Caused by: java.io.FileNotFoundException: /Users/ingo/Documents/Aptana_Studio_3_Workspace/testMobile/dist/app.bapp-android-0.1.zip (No such file or directory) java.io.FileOutputStream.open(Native Method) java.io.FileOutputStream.<init>(FileOutputStream.java:194) org.eclipse.core.internal.filesystem.local.LocalFile.openOutputStream(LocalFile.java:382) ... 8 more {code} The issue appears to be the fact it's copying it from inside /dest, but that it attempts to copy it into a /dest subfolder as well, which doesn't exist.
| 5 |
train
|
TISTUD-1442
|
Prevent an Android Mobile Module project creation when JDT is not installed
|
Android mobile-module project should not be created unless the JDT plugins (feature) are installed. Right now, a created project on an environment without JDT is not usable.
| 5 |
train
|
TISTUD-1443
|
Studio: Build Participation: Windows does not update content assist for new class methods in Javascript
|
Failed test case BP1009. Javascript: New class methods do not appear in content assist before saving. Steps to reproduce: 1. Define a class. 2. Add a method to the class definition. 3. Create a new instance of the variable. 4. On a new line type the name of the instance identifier with the member selection operator. Expected result: The declared class method will appear in the content assist list. Actual result: The new method does not show up in content assist.
| 5 |
train
|
TISTUD-1445
|
Project fails to build, launch emulator with Android R17 tools & Ti2.0
|
h5. Actual Behavior All projects fail to build to the emulator under the environment listed above. I get the error shown in the attached screen. Eventually, I get the message that the build script has timed out waiting for the emulator to launch -- restarting ADB has no effect. Via twitter, some have suggested that you need to disable FastDev with the R17 tools & Titanium. You can see from the attached screen that I tried that. But it had no effect. Neither did specifying an older Android tool level. h5. Work around I can reset the project to use the Titanium 1.8.2 SDK. The project will build & the emulator will launch as expected. Then, I can rebuild the project using any of the 2.0x CI builds I have on my system and they'll all work just fine. h5. Expected behavior I can build with Ti2.0 and the R17 tools without implementing the Work around.
| 8 |
train
|
TISTUD-1447
|
Run preference page platform loading using a job
|
Currently when the preference page is opened, it takes some time for the dialog to appear, resulting in a wait cursor to appear. This is very confusing for users. The proposed solution is: -When the preference page is opened, run the loading of platform information in a background job -While the platform information is loaded, the corresponding platform UI is disabled and the value of "Loading..." is displayed. We should do this for the two main platforms, iOS and Android, since they require the most processing time.
| 13 |
train
|
TISTUD-1450
|
Studio: Updated modules delivered via CI builds are not replacing existing modules if they share the same name
|
While evaluating ACS features, we encountered an Android issue that was supposed to have been fixed in the latest ti.cloud module. Upon further investigation we determined that the module was in fact included with the latest CI build. We conducted a few experiments and determined that although the module was updated, the name was the same so during the unzipping process, the module was not replacing the existing older module. Steps to reproduce: 1) Delete your existing common JS module folder from the Titanium folder 2) install a CI build from 3/24 or before 3) Check the contents of the module folder 4) install a CI build from 3/27 or later 5) Check the contents of the module folder Results: The ti.cloud module is the older broken module, not the newer fixed module Expected: The module is overwritten by the newer module with the same name. Note: There is no relevant content in the log
| 8 |
train
|
TISTUD-1452
|
Simplify initial Studio UI and perspective
|
An exercise in simplifying the new user experience: * Rename Web perspective to "Studio (extended)" * Create new "Studio" perspective ** remove top level toolbar ** add keyboard shortcuts commands for "occurrences", "block selection", "show whitespace characters" ** remove samples view ** remove outline view ** remove snippets view ** remove servers, problems, terminal, console view ** keep console view hidden unless an error comes up
| 13 |
train
|
TISTUD-1456
|
Add default UI configuration options to dashboard
|
* Remove Welcome page * Replace with accordion. Initially open a section to configure TISTUD-1456 ** Light/dark theme ** Simple/advanced perspective ** See APSTUD-4798 and APSTUD-4799 for actions to call The bottom half of the accordion is similar to what we have currently If we reduce or remove the top toolbar, we may wish to surface some common initial configuration options to the first tab of the dashboard--something equivalent to an initial questionnaire. It could be perhaps in some normally "hidden" area for "advanced configuration" if we determine it's useful but is confusing on first run.
| 20 |
train
|
TISTUD-1464
|
Inform users they need to switch to a workspace without spaces if doing Android Module development
|
When using the Android NDK, if you have spaces in your path (i.e. /Users/username/Documents/Titanium Studio Workspace), Studio will fail to be able to build an Android module project. Suggest putting up a warning when creating a mobile module project warning users about the issue and informing them how to solve it (direct them to the wiki page on how to move/switch their workspace: http://docs.appcelerator.com/titanium/2.0/index.html#!/guide/Switching_your_Workspace).
| 5 |
train
|
TISTUD-1466
|
Use built-in ANT when packaging Android modules
|
# Created a new Android mobile module project # Attempt to package the project # Run into this error: {code} Caused by: java.lang.NullPointerException com.appcelerator.titanium.mobile.module.launching.AndroidModulePackageLaunchConfigurationDelegate.launch(AndroidModulePackageLaunchConfigurationDelegate.java:83) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937) org.eclipse.debug.internal.ui.DebugUIPlugin$7.run(DebugUIPlugin.java:1023) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Root exception: java.lang.NullPointerException com.appcelerator.titanium.mobile.module.launching.AndroidModulePackageLaunchConfigurationDelegate.launch(AndroidModulePackageLaunchConfigurationDelegate.java:83) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937) org.eclipse.debug.internal.ui.DebugUIPlugin$7.run(DebugUIPlugin.java:1023) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) {code} snippet of code: final Process osProcess = ProcessUtil.run(antPath.toOSString(), project.getLocation()); It appears it can't find ANT. We package ANT as part of Studio, so we should instead use the built-in ANT rather than calling it on the command line. Workaround: Right-click on build.xml. Click *Run As* > *Ant Build* (the first option)
| 5 |
train
|
TISTUD-1468
|
Add Titanium Project GUID to ACS application creation call
|
When creating an application in ACS, we need to pass the GUID along with the call. The format will be: ti_guid=<Project GUID>, passed to the create.json call.
| 3 |
train
|
TISTUD-1469
|
Studio: HTML Template selection does not load correctly.
|
After first loading Titanium Studio the template selection for the New from template > HTML has the wrong selection (see screen shot). If I load a template for HTML this fixes the template selection found in the menu. Steps to reproduce: 1. Open Titanium Studio. 2. Click File > New From Template > HTML Expected results: Should see a list of all available templates for HTML files. Actual results: Only a strange entry and the HTML 5 template appear.
| 8 |
train
|
TISTUD-1474
|
Titanium Studio: Installer - On Windows 7, when installing Titanium Studio, the License Agreement has a bad refresh screen
|
Steps to reproduce: 1. Get Titanium Studio 2.0.0 installer for Windows 2. Hit next until you see the License Agreement screen Actual: The License Agreement has a bad refresh screen. See attachment Expected: Should be able to see the License Agreement. Note: Does not occur with the Titanium Studio 1.0.9 installer.
| 5 |
train
|
TISTUD-1476
|
NPE in TitaniumUpdateStartup.run()
|
Found in my log file. To replicate (my be intermittent), try shutting down Studio right in the middle of the "log in" process {code} !ENTRY org.eclipse.core.jobs 4 2 2012-03-31 07:44:07.268 !MESSAGE An internal error occurred during: "Checking for new Titanium SDK Updates...". !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.update.TitaniumUpdateStartup$1.run(TitaniumUpdateStartup.java:79) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 3 |
train
|
TISTUD-1477
|
Make Titanium SDK release-notes grabbing more robust
|
If the current set of release notes is from a full HTML page that _does not_ contain a <div class="apidoc">, the release noes will launch in a new browser window. # Allow for override of TitaniumSDKReleaseNotesDialog.RELEASE_NOTES_URL as a command-line option to make testing this easier. # First try to grab apidiv. # Then try to grab interior of body node, or if no body node, then whole content. If either work then replace release_notes template with new content. # If all else fails, use whole content and don't use the template. Notes: * Be careful of nulls * Anchor links didn't appear to work (might need to be munged?)
| 8 |
train
|
TISTUD-1479
|
Allow selecting a non-existing directory as the Titanium SDK directory
|
When a user selects a Titanium SDK path in the preference page, we don't allow a path that has no Titanium SDK in it. A better behavior would be: # Allow an arbitrary directory selection. # Prompt the user that the Titanium SDK will be downloaded into the new location (in case it's missing an SDK). # In case a directory creation is needed, we'll do that *before* the preference dialog is closed (on apply/ok). This will clear any permission issues with the selected path before the SDK is downloaded. # If everything is OK with the new location, start the SDK update process into the new path.
| 8 |
train
|
TISTUD-1481
|
Studio: Install site will not allow for software to be installed.
|
When trying to install the TestFlight software plugin following the steps below I found that I can not proceed to the licence page in the installation. Steps to reproduce: 1. From the Help menu, select Install New Software... to open an Install pop-up window. 2. In the Work with: text box of the Install window, type the URL http://ec2-50-16-19-245.compute-1.amazonaws.com/appcelerator/studio/testflight/update/release/ for the update site, and hit the Enter key. 3. In the populated table below, check the box next to the name of the plug-in, and click the Next button. 4. Click the Next button to go to the license page. Expected result: The licence page is displayed and the installation can be completed. Actual result: The next button does not become active and there is no way to continue to the next part of the installation.
| 5 |
train
|
TISTUD-1488
|
ACS Keys not copy-able
|
I enabled ACS for one of my apps using early access 2.0 Studio, and it shows the production and development keys, but you can't copy it, if we need to use HTTP access or test using other software - we would have to manually type this out, or go to the ACS website, can the keys in Studio be copy-able?
| 5 |
train
|
TISTUD-1482
|
NPE in Log when Studio is shutdown
|
Found in my log file. To replicate (my be intermittent): 1. Start up Studio 2. Open the Progress View 3. Restart Studio 4. When Studio is started, take note of the items in the Progress view 5. When there are items running int he progress view, close Studio I repeated this 4 times, with different tasks in the progress view running, and saw the NPE twice !MESSAGE Errors running builder 'Studio Unified Builder' on project 'testMe'. !STACK 0 java.lang.NullPointerException com.aptana.core.build.UnifiedBuilder.getIndexManager(UnifiedBuilder.java:367) com.aptana.core.build.UnifiedBuilder.filterFiles(UnifiedBuilder.java:471) com.aptana.core.build.UnifiedBuilder.buildFiles(UnifiedBuilder.java:400) com.aptana.core.build.UnifiedBuilder.fullBuild(UnifiedBuilder.java:302) com.aptana.core.build.UnifiedBuilder.build(UnifiedBuilder.java:148) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
| 3 |
train
|
TISTUD-1485
|
Update sites for Openshift/TestFlight should not contain both plugin and feature node
|
When we install from an update site using the result from the TestFlight and Openshift builds, the categorized nodes are the plugin and the feature nodes. Typically it should just contain the Feature install, which would pull in the plugin as part of it. In this case, if we check just the feature and not the plugin, the install is an invalid one, resulting in an invalid install.
| 8 |
train
|
TISTUD-1489
|
Update IPublishType.publish() method to explicitly pass in PlatformType, output location and publish target
|
For clarity, we should pass in the parameters we know about explicitly - Publish target, platform type, and output location.
| 5 |
train
|
TISTUD-1490
|
Titanium Studio: SDK: updating to readonly sdk folder gives no such directory error
|
When updating SDK to an SDK folder with readonly access, a directory not found error is presented (instead of invalid permissions). Steps to Reproduce: 1. Change the permissions of the Titanium SDK folder to readonly (e.g., folder right click -> properties -> permissions, etc.). 2. Update the SDK to a different version. Update Option 1: Go to http://builds.appcelerator.com.s3.amazonaws.com/index.html, copy an SDK location. Go to Studio: Help -> Install Titanium SDK From URL, paste the link, update. Update Option 2: Remove the last live version of the SDK from the SDK folder. Go to Studio: Help -> Check For Titanium SDK Updates. Expected Result: There should be an error indicating the SDK folder does not have write permissions. Actual Result: Directory not found error.
| 5 |
train
|
TISTUD-1494
|
Building for iOS device in Studio 2.0 against SDK 2.0.0GA (Ad-Hoc certs and PUSH issues)
|
when I build for an iOS Device Xcode bounces in the dock for nearly a minute before it will unlock beachball and allow me to make a selection, it happens once before the first window shows and then once again before build. If I select Manage option - this whole Xcode bouncing in the dock repeatedly (like its loading and quitting again and again) happens ... its very slow. Compared to 1.x Studio which is much faster. The preselected provisioning profiles is not clear, and somehow I managed to build against an ad-hoc certificate, i did not consciously choose this) but it caused my Push Notification Process to throw up errors. I tried 2 possible certs that were available to me and both times it must have used an ad-hoc certificate. I went back to 1.x and rebuilt it. I preferred the ability to remove and add certificates manually at this stage. Always avoided confusion for me.
| 8 |
train
|
TISTUD-1496
|
Trailing semicolon after curly brace in conditional causes error in JS formatting
|
Steps to reproduce: 1. Create a new .js file in a project 2. Copy the following code and paste it into the .js file {code} if ( i == _i) {} else {}; {code} 3. Press command+shift+f on mac to format the pasted code Actual result: The following error is generated in the log file: !ENTRY com.aptana.formatter.epl 4 0 2012-04-05 11:14:39.664 !MESSAGE (Build 3.0.0.1332346356) [ERROR] com.aptana.formatter.epl/debug Error while formatting the code in your editor. Please submit a bug report through Studio's support and include the relevant code which triggered this error. Expected result: The code is formatted correctly. It appears to be that last trailing semicolon. Delete that, and it works.
| 5 |
train
|
TISTUD-1497
|
Studio displays iOS ad hoc provisioning profiles as "development" when it should be "distribution"
|
Studio displays Ad hoc provisioning profiles incorrectly as "development". This causes confusion in the following areas: -Preferences displays the displays the type incorrectly -The iOS distribution wizard displays Apple iTunes, Ad hoc, and development profiles (should only display Apple iTunes and Ad hoc profiles) -The iOS Run on device wizard displays Apple iTunes, Ad hoc, and development profiles (should only display development profiles) Special attention must be made to the way we cache provisioning profiles, since a fix to the SDK will not update the "type" of the cached provisioning profiles. We have to trigger a flush of the cache if there is a presence of SDK 2.2.0, where previously there wasn't. This is blocked by an SDK bug
| 8 |
train
|
TISTUD-1503
|
Fix padding on release notes dialog
|
The current release notes template is very specific about what content it expects to style. However, this can lead to release notes not having any padding around the edge of the content. Recommend adjusting the styling slightly to accommodate.
| 3 |
train
|
TISTUD-1506
|
Titanium Studio: Configuration: Preferences > Titanium Studio > Titanium freezes studio
|
Navigating to Preferences > Titanium Studio > Titanium freezes studio. This does not occur in the last studio build. Regression. Steps to Reproduce: 1. Open Studio. 2. Navigate to Preferences > Titanium Studio > Titanium. Expected Result: Titanium Preferences should open. Actual Result: Studio freezes, need to force-close.
| 8 |
train
|
TISTUD-1507
|
Error opening the Titanium preferences when the Desktop SDK is incomplete
|
An attached log to TISTUD-1506 revealed this problem. {code} !ENTRY org.eclipse.jface 4 2 2012-04-10 12:55:28.904\ !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".\ !STACK 0\ java.lang.NullPointerException\ com.appcelerator.titanium.desktop.DesktopSDKEntity.setModules(DesktopSDKEntity.java:54)\ com.appcelerator.titanium.desktop.DesktopSDKEntity.<init>(DesktopSDKEntity.java:39)\ com.appcelerator.titanium.desktop.TitaniumDesktopSDKLocator.initialize(TitaniumDesktopSDKLocator.java:169)\ com.appcelerator.titanium.desktop.TitaniumDesktopSDKLocator.<init>(TitaniumDesktopSDKLocator.java:52)\ com.appcelerator.titanium.ui.preferences.TitaniumSDKDirectoryFieldEditor.doCheckState(TitaniumSDKDirectoryFieldEditor.java:94)\ org.eclipse.jface.preference.StringFieldEditor.checkState(StringFieldEditor.java:193)\ org.eclipse.jface.preference.StringFieldEditor.refreshValidState(StringFieldEditor.java:409)\ org.eclipse.jface.preference.FieldEditor.load(FieldEditor.java:501)\ org.eclipse.jface.preference.FieldEditorPreferencePage.initialize(FieldEditorPreferencePage.java:307)\ org.eclipse.jface.preference.FieldEditorPreferencePage.createContents(FieldEditorPreferencePage.java:233)\ org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:232)\ org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1501)\ org.eclipse.jface.preference.PreferenceDialog$14.run(PreferenceDialog.java:1258)\ org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)\ org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)\ org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)\ org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1252)\ org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:674)\ org.eclipse.jface.preference.PreferenceDialog$10.run(PreferenceDialog.java:708)\ org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)\ org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:704)\ org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:888)\ org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)\ org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)\ org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)\ org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:886)\ org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1226)\ org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1251)\ org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:262)\ org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:256)\ org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:433)\ org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)\ org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)\ org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938)\ org.eclipse.swt.widgets.Display.observerProc(Display.java:3525)\ org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)\ org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4879)\ org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226)\ org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)\ org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220)\ org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1092)\ org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2052)\ org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1084)\ org.eclipse.swt.widgets.Control.mouseDown(Control.java:2528)\ org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2007)\ org.eclipse.swt.widgets.Display.windowProc(Display.java:5471)\ org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)\ org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220)\ org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2095)\ org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2253)\ org.eclipse.swt.widgets.Display.windowProc(Display.java:5535)\ org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)\ org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4989)\ org.eclipse.swt.widgets.Display.applicationProc(Display.java:5138)\ org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)\ org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)\ org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3610)\ org.eclipse.jface.window.Window.runEventLoop(Window.java:825)\ org.eclipse.jface.window.Window.open(Window.java:801)\ org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215)\ org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:54)\ org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)\ org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)\ org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:178)\ org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.runCommand(CocoaUIEnhancer.java:393)\ org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:535)\ org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:520)\ org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)\ org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4879)\ org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226)\ org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)\ org.eclipse.swt.internal.cocoa.NSApplication.nextEventMatchingMask(NSApplication.java:94)\ org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3607)\ org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)\ org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)\ org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)\ org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)\ org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)\ org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)\ org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)\ com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125)\ org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)\ org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)\ org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)\ org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)\ org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)\ sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\ sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)\ sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)\ java.lang.reflect.Method.invoke(Method.java:597)\ org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)\ org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)\ org.eclipse.equinox.launcher.Main.run(Main.java:1410)\ {code}
| 3 |
train
|
TISTUD-1510
|
Run iOS preference page loading in the background
|
See parent
| 8 |
train
|
TISTUD-1511
|
Run Android preference page loading in the background
| null | 8 |
train
|
TISTUD-1513
|
TiStudio: Mobile Projects - When creating mobile projects offline, two projects with same guid will sporadically be created in my.appcelerator.com/apps site
|
Steps to reproduce: 1. Launch Studio with internet connection disabled 2. Create a TiMobile project 3. Relaunch Studio with internet connection enabled 4. Check https://my.appcelerator.com/apps *May need to repeat steps 1 - 4 a couple of times* Actual: Two projects with the same guid are created in my.appcelerator.com/apps site. See attachments. Expected: One project should be created at my.appcelerator.com/apps site *Note:* * Bug not reproducible on Titanium Studio, build: 2.0.0 and 1.0.9 * Bug not reproducible on Windows 7 machine * Bug not reproducible when working from home
| 8 |
train
|
TISTUD-1514
|
TiStud: Workspace - When switching workspaces from within TiStudio, TiStudio will not launch
|
Steps to reproduce: 1. Launch TiStudio 2. Go to File > Switch Workspace 3. Select a different workspace Actual: TiStudio will stay stuck at the log in/splash screen. See attachments. Expected: Should be able to launch TiStudio after switching to different workspace Note: Bug does *not* occur on Windows 7 and Lion (10.7.3)
| 13 |
train
|
TISTUD-1515
|
Blocker: Android : Templates : SingleWindow - After creating an Android only single window template a null pointer exception occurred when launching to the emulator
|
Steps to reproduce: 1. Create a Android only single window application 2. Launch on the Emulator Actual result: A null pointer error occurs *Note* This occurred consistently, then I cleared out my avds and sdcards and the issue went away Here is the output to the log {code} !ENTRY org.eclipse.core.jobs 4 2 2012-04-11 16:45:17.583 !MESSAGE An internal error occurred during: "Launching Titanium Android Emulator - singleAnd". !STACK 0 java.lang.NullPointerException com.appcelerator.titanium.mobile.launching.FastDevLaunchConfigurationDelegate$1.terminate(FastDevLaunchConfigurationDelegate.java:56) org.eclipse.debug.core.Launch.terminate(Launch.java:252) com.appcelerator.titanium.core.launching.AbstractSharedProcessLaunch.findOrLaunch(AbstractSharedProcessLaunch.java:170) com.appcelerator.titanium.core.launching.AbstractSharedProcessLaunch.launch(AbstractSharedProcessLaunch.java:92) com.appcelerator.titanium.mobile.android.launching.AndroidSimulatorLaunchConfigurationDelegate.launch(AndroidSimulatorLaunchConfigurationDelegate.java:182) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937) org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1141) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} *Screenshot attached* Expected result: The app is launched to the simulator
| 5 |
train
|
TISTUD-1516
|
Titanium Studio RCP contains JDT plugins
|
I was trying to verify TISTUD-1442 and found out that I do have JDT plugins in my standalone by default. This is almost a clone of APSTUD-1378 (but this is for Titanium standalone).
| 13 |
train
|
TISTUD-1517
|
ClassCastException when opening the index.html of a packaged mobile web project
|
Running from a dev workspace with latest code in the release branch: 1. Created a Titanium Mobile project with Mobile Web selected as one of the deployment targets; 2. Run Publish > Package Mobile Web and select to create a new project for the Mobile Web app; 3. Open the index.html file from the packaged mobile web project. Actual result: the following exception is generated in the console: {code} Exception in thread "com.aptana.editor.common.text.reconciler.CommonReconciler" java.lang.ClassCastException: com.aptana.editor.js.parsing.ast.JSAssignmentNode cannot be cast to com.aptana.editor.html.parsing.ast.HTMLElementNode com.aptana.editor.html.validator.HTMLTidyValidator.handleNode(HTMLTidyValidator.java:400) com.aptana.editor.html.validator.HTMLTidyValidator.access$0(HTMLTidyValidator.java:394) com.aptana.editor.html.validator.HTMLTidyValidator$1.include(HTMLTidyValidator.java:386) com.aptana.editor.html.validator.HTMLTidyValidator$1.include(HTMLTidyValidator.java:1) com.aptana.parsing.util.ParseUtil.treeApply(ParseUtil.java:155) com.aptana.parsing.util.ParseUtil.treeApply(ParseUtil.java:121) com.aptana.editor.html.validator.HTMLTidyValidator.validateAST(HTMLTidyValidator.java:382) com.aptana.editor.html.validator.HTMLTidyValidator.buildFile(HTMLTidyValidator.java:164) com.aptana.core.internal.build.LazyBuildParticipant.buildFile(LazyBuildParticipant.java:72) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.runParticipants(CommonReconcilingStrategy.java:277) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.reconcile(CommonReconcilingStrategy.java:238) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.reconcile(CommonReconcilingStrategy.java:205) com.aptana.editor.common.text.reconciler.CommonReconcilingStrategy.initialReconcile(CommonReconcilingStrategy.java:137) com.aptana.editor.common.text.reconciler.CompositeReconcilingStrategy.initialReconcile(CompositeReconcilingStrategy.java:113) com.aptana.editor.common.text.reconciler.CommonReconciler.initialProcess(CommonReconciler.java:188) org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:173) {code} Expected result: no exception occurs.
| 3 |
train
|
TISTUD-1518
|
TiStudio: Dashboard - Drop down does not refresh properly when trying to "Create new project" template
|
Steps to reproduce: 1. Launch TiStudio 2. In Dashboard, go to Develop tab 3. Under Templates, find *Create new project* 4. Hover above drop down Actual: Drop down does not appear. Need to move mouse down to refresh properly. See no_drop_down.png Expected: Drop down should immediately display *Desktop* and *Mobile*. See drop_down.png Notes: Bug does *not* appear on Lion (10.7.3) and Windows 7
| 8 |
train
|
TISTUD-1522
|
Android and iOS module packagers have launch configuration types but no tab group defined
|
When opening "Run Configuration..." dialog, we see Android Module Packager and iOS Module Packager in the list, but double-clicking on them causes an error showing there is no corresponding tab group defined.
| 13 |
train
|
TISTUD-1523
|
Fail Jenkins build if Studio contains JDT plugins
|
As a way of keeping ourselves from accidentally releasing JDT into the wild as part of Studio, we need to fail the Aptana Studio and Titanium Studio builds if either the plugin or standalone versions come packaged with the JDT plugins. This prevents half-baked JDT installs which hen keep a user from later installing the whole JDT proper for module development.
| 8 |
train
|
TISTUD-1525
|
Unable to click on anchor links in release notes
|
# Delete SDK 2.0.1.GA. # Prompt for SDK updates # When the release notes pop up, click on an anchor # View the log file. You'll see a set of errors like: {code} !ENTRY com.aptana.ui 4 0 2012-04-16 23:23:49.344 !MESSAGE (Build 3.0.3.1331579821) [ERROR] unknown protocol: about !STACK 0 java.net.MalformedURLException: unknown protocol: about java.net.URL.<init>(URL.java:574) java.net.URL.<init>(URL.java:464) java.net.URL.<init>(URL.java:413) com.aptana.ui.util.WorkbenchBrowserUtil.launchExternalBrowser(WorkbenchBrowserUtil.java:35) com.appcelerator.titanium.update.ui.TitaniumSDKReleaseNotesDialog$2.changing(TitaniumSDKReleaseNotesDialog.java:191) org.eclipse.swt.browser.WebKit.webView_decidePolicyForNavigationAction_request_frame_decisionListener(WebKit.java:1493) org.eclipse.swt.browser.WebKit.browserProc(WebKit.java:423) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2095) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2253) org.eclipse.swt.widgets.Display.windowProc(Display.java:5535) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4989) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5138) org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3610) org.eclipse.jface.window.Window.runEventLoop(Window.java:825) org.eclipse.jface.window.Window.open(Window.java:801) org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:334) com.appcelerator.titanium.update.handler.TitaniumUpdateHandler.execute(TitaniumUpdateHandler.java:30) org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:829) org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:815) org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:805) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) {code} It appears that the anchors are showing as file:///#viewtypes
| 5 |
train
|
TISTUD-1528
|
TiStudio: Preview Site - At Titanium Studio preview site, the builds are skewed to the right
|
Environment: FireFox, Chrome, and Safari Steps to reproduce: 1. Go to http://preview.appcelerator.com/studio/ Actual: Notice the Studio builds are skewed to the right. See attachment. Expected: The Studio builds should be properly aligned.
| 3 |
train
|
TISTUD-1527
|
Titanium Studio: Dashboard: Search and Top Ad open in generic browser with no controls
|
Using the dashboard search bar or the top ad link ("Reach 1.5 Million Appcelerator Developers") launches in a generic browser with no controls, providing difficult navigation. To address this, we'll need to switch the code that launches the browser in this case to be the same as the other cases on the dashboard (all other links open an external browser, and that appears to work correctly). it's a matter of triggering a portal action instead of using target="_new" as part of the href.
| 8 |
train
|
TISTUD-1529
|
Studio will start updating the SDK automatically upon launch without showing there is an update available first
|
To reproduce: 1. Remove the latest SDK from the mobile SDK directory if it is already downloaded; 2. Start Studio. Expected result: Studio will show a popup on the lower right corner indicating there is an update available, and clicking on it will show a release note dialog and then start downloading the latest SDK. Actual result: Studio will start downloading the latest SDK right away after launching without any user interaction, and no release note dialog is shown.
| 8 |
train
|
TISTUD-1530
|
Success dialog closes immediately after Titanium SDK update
|
Steps to repro: 1. Launch studio, and update to the latest sdk (remove the latest sdk if necessary first) 2. Wait for the sdk to download and unzip. Expected result: There should be a success dialog at the end of the unzip process which stays on the screen until the user presses OK Actual result: The success dialog quickly appears and then disappears with the progress bar.
| 3 |
train
|
TISTUD-1534
|
Titanium Studio: Configuration: Preferences > Titanium Studio > Titanium > Default Android SDK inconsistently sorted
|
The Android APIs listed in the preferences are not sorted as they are in the run configurations. Screenshots attached. Steps to Reproduce: 1. In Studio, navigate to Preferences > Titanium Studio > Titanium > Default Android SDK. 2. View the sorting of the Android APIs. Expected: The APIs in the preferences are expected to look as they do in the run configurations, as the run configuration sorting looks more orderly. Actual: The preferences APIs are sorted in a way that is inconsistent with the run configurations and is visually confusing.
| 3 |
train
|
TISTUD-1537
|
Every time you click 'Enable' for 'Enable Cloud Services' a new app gets created
|
In TiStudio open the tiapp.xml file of an app with the 2.0.1 GA, and click 'Enable'. An app is created in the cloud services. Click it again and another app is created... Suggested fix: # Check to see if the file is dirty. If yes, alert the user that enabling cloud services will save the file. They can then choose to proceed, or click cancel. # Enable cloud services. # Save the file.
| 5 |
train
|
TISTUD-1539
|
Dashboard's "Develop" tab missing content
|
After upgrading to version 2.0.2.201204171552 from version 2.0.1.201204132053 the develop tab on the dashboard no longer has any samples listed and only one template option. This does not occur in 2.0.1. Regression. Steps to reproduce: 1. Load Titanium Studio. 2. Load the Dashboard. 3. Click the develop tab. Expected Result: The develop page of the dashboard should contain links to samples and templates for developers. Actual Results: The develop page contains only a single template and no samples.
| 8 |
train
|
TISTUD-1540
|
Titanium API not showing up at all in CA of a newly created project if "Build Automatically" is turned off
|
If I create a new mobile project, I don't get Titanium or Ti in my CA at all. I need to right-click on project, go to Prioperties > Project Build Path, change the Titanium API, then change back to the original one I wanted (say from 2.0.1GA2 to 1.8.2, click Ok, then go back and change back to 2.0.1GA2).
| 8 |
train
|
TISTUD-1541
|
CA popup shifts between proposals
|
See the attached images # Open a new JS file # Type 'a'. See popup for alert # arrow down to "Array" # Note the popup shift Neither is correct. I believe it should have the horizontal spacing of the "alert()" case, but the vertical alignment of the "Array" case
| 8 |
train
|
TISTUD-1543
|
TiStudio: Dashboard - "API Docs" does not take you to the API documentation site
|
Steps to reproduce: 1. Open TiStudio 2. In the dashboard, click on *API Docs* Actual: Link takes you to http://docs.appcelerator.com/titanium/2.0/index.html Expected: Link should take you to http://docs.appcelerator.com/titanium/2.0/index.html#!/api Note: Not a regression.
| 8 |
train
|
TISTUD-1545
|
Fail Titanium Studio build if titanium.core plugin is missing rubles
|
based on TISTUD-1539, we should fail the build if the Titanium Rubles fail to package. One suggested approach is to copy the plugin, unzip it and manually check for the bundles and fail if they're not there.
| 8 |
train
|
TISTUD-1546
|
Installer: The link to the software licence agreement does not work.
|
The link to the Software licence agreement does not open the licence agreement when clicked. This did not happen in the 2.0.0 installer. Not regression as this functionality is new. Steps to reproduce: 1. Download and run the installer. 2. When prompted for the licence agreement click the link. Expected Results: The licence agreement will open in another window for reading. Actual Results: Nothing happens.
| 8 |
train
|
TISTUD-1549
|
Titanium Studio: Content Assist - content assist menu persistent in the OS if popup info has focus
|
Content Assist menu is persistent in the OS if the assist popup info menu has focus (i.e., by clicking on it). Other OS program windows are now obfuscated by the content assist menu until the focus is shifted back to Titanium Studio proper or the regular content assist menu. Screenshot attached. Note: This is a lesser behavior of the fixed TISTUD-913. Steps to Reproduce: 1. Open Studio and create a new project (or open an existing project). 2. Click in the text editor of app.js (or any .js file). 3. Press control + space to bring up the content assist menu. 4. Select any item from the suggestion list by clicking on it. 5. Click on the secondary popup that appears for that particular content assist item. 6. Open any other program (such as Chrome) and move the other program window over the content assist menu. Expected Result: The content assist menu should disappear behind the other program window, as it should have the same OS hierarchy as Titanium Studio. Actual Result: The content assist menu persists and obfuscates the other program window until the focus shifts back to Studio or a regular content assist item.
| 8 |
train
|
TISTUD-1550
|
Titanium Studio: Content Assist: assist menu intermittently fails to change focus
|
The content assist menu will not close at all if the user clicks away. This is intermittent. This is a lesser behavior of TISTUD-1268, which is fixed. Summary of TISTUD-1268: Content assist would intermittently stay open as a stand-alone window until studio was restarted. The TISTUD-1268 fix: If the content assist menu is up, and studio minimizes, the content assist menu will minimize as well. Current Issue: Steps to Reproduce: 1. Open studio, create a new project, or open an existing javascript file. 2. Open content assist. 3. Click away from content assist. Expected Result: Content assist should close. Actual Result: Content assist intermittently stays open and will not close. This window is also persistent in the OS, though that related issue was fixed (TISTUD-913). When studio is minimized, content assist will minimize as well. When studio is maximized, the content assist menu is still there. The only way I could close content assist window was by opening a new content assist window (cntrl + space), which would close the old one, and open a new one which behaves properly.
| 13 |
train
|
TISTUD-1551
|
CLONE - Unable to correctly parse git version
|
Found in Eric's log file. I though this was a duplicate of another ticket, but I can't find the first version. {code} !ENTRY com.aptana.git.core 4 0 2012-03-30 11:52:03.083 !MESSAGE (Build 3.0.0.1332346356) [ERROR] com.aptana.git.core/debug Unable to correctly parse git version 1.7.7.5 (Apple Git-26) !STACK 0 java.lang.IllegalArgumentException: invalid qualifier: 5 (Apple Git-26) at org.osgi.framework.Version.validate(Version.java:195) at org.osgi.framework.Version.<init>(Version.java:161) at org.osgi.framework.Version.parseVersion(Version.java:225) at com.aptana.git.core.model.GitExecutable.version(GitExecutable.java:399) at com.aptana.git.core.model.GitExecutable.clone(GitExecutable.java:431) at com.aptana.git.ui.CloneJob.run(CloneJob.java:86) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code}
| 5 |
train
|
TISTUD-1572
|
Unable to format titanium.js file generated by Titanium Mobile Web project
|
The file is generated when you package a Titanium mobile web project as a new project in the workspace. The generated project should have a titanium.js file. When I try to format the file I get the following error: !ENTRY com.aptana.editor.js.formatter 4 0 2012-04-19 15:36:03.866 !MESSAGE (Build 3.0.3.1334796284) [ERROR] com.aptana.formatter.epl/debug Cannot recover from the syntax error !STACK 0 beaver.Parser$Exception: Cannot recover from the syntax error beaver.Parser.recoverFromError(Parser.java:697) com.aptana.editor.js.parsing.JSParser.recoverFromError(JSParser.java:623) beaver.Parser.parse(Parser.java:498) beaver.Parser.parse(Parser.java:439) com.aptana.editor.js.parsing.JSParser.parse(JSParser.java:447) com.aptana.editor.js.formatter.JSFormatter.equalContent(JSFormatter.java:295) com.aptana.editor.js.formatter.JSFormatter.format(JSFormatter.java:246) com.aptana.formatter.ScriptFormattingStrategy.doFormat(ScriptFormattingStrategy.java:185) com.aptana.formatter.ScriptFormattingStrategy$1.run(ScriptFormattingStrategy.java:115) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) com.aptana.formatter.ScriptFormattingStrategy.format(ScriptFormattingStrategy.java:111) org.eclipse.jface.text.formatter.MultiPassContentFormatter.formatMaster(MultiPassContentFormatter.java:193) org.eclipse.jface.text.formatter.MultiPassContentFormatter.format(MultiPassContentFormatter.java:135) !ENTRY com.aptana.formatter.epl 4 0 2012-04-19 15:36:03.870 !MESSAGE (Build 3.0.0.1332346421) [ERROR] com.aptana.formatter.epl/debug Error while formatting the code in your editor. Please submit a bug report through Studio's support and include the relevant code which triggered this error.
| 8 |
train
|
TISTUD-1556
|
Titanium Studio: Cloud: enabling app cloud services when offline causes partially blank and inconsistent error messages
|
If the user enables cloud services for an app while offline, one of the error messages is blank, and the others does not explicitly notify that studio is offline. There is also an inconsistency between popup errors generated by the tiapp.xml, and the new project wizard. However, the log messages are (correctly) the same for both enablement methods (tiapp.xml and new project wizard). Screenshots attached. Log attached. Steps to Reproduce: 1. Go offline. 2. Create a new project with cloud services enabled. Expected Result: A standard popup should appear indicating studio is offline and cloud services could not be activated. An error should be logged. Actual Result: A new-project-wizard-specific error popup appears indicating cloud services could not be activated. There is no mention of being offline. An error message is (correctly) logged to the console indicating an http failure. 3. Dismiss the popup and enable cloud services using the tiapp.xml overview. Expected Result: A standard popup should appear indicating studio is offline and cloud services could not be activated. An error should be logged. Actual Result: A different error popup appears with blank text in the "Reason" section. The same console error from before is (correctly) logged.
| 8 |
train
|
TISTUD-1557
|
Editor: JavaScript Comment Auto-Complete indentation is inconsistent
|
If a javascript comment is auto-completed from a closed pair of parenthesis or a closed pair of curly braces, the indentation of the cursor is farther than usual. Screenshots attached. This is a new fail case, as this feature was not implemented in 2.0.1. Steps to Reproduce: 1. Enter javascript code below in editor. {code} function(){} {code} 2. Insert the cursor between the parenthesis and type "/*" and press "enter". For example: {code} function(/*){} {code} Expected Result: Cursor indentation should be one space away from the asterisk to the left. Actual Result: Cursor indentation is a few spaces away from the asterisk.
| 8 |
train
|
TISTUD-1558
|
Titanium Studio: JavaScript Comment Auto-Complete fails if on same line as end of previous comment
|
If a javascript comment is auto-completed from a line that contains the end of another auto-completed comment, the new completion will fail to complete the comment. Screenshots attached. Steps to Reproduce: 1. Enter javascript code in editor: {code} function(){} {code} 2. Insert cursor at the beginning of the line, type "/*", and press enter. For example: {code} /* * */function(){} {code} 3. Insert cursor at the end of the line, type "/*", and press enter. For example: {code} /* * */function(){}/* {code} Expected Result: Auto-completion should succeed, for example: {code} /* * */function(){}/* * */ {code} Actual Result: Auto-complete fails, for example: {code} /* * */function(){}/* * {code}
| 5 |
train
|
TISTUD-1559
|
Titanium Studio: Snow Leopard: Toggle Full Screen menu item exists but is not supported
|
In Titanium Studio, the top menu, Window > Toggle Full Screen exists, but is grey-ed out and non-selectable. Full Screen is not supported on Snow Leopard, only on Lion. Steps to Reproduce: 1. Open Titanium Studio. 2. In the top menu, navigate to the Window drop-down menu. Expected Result: Window > Toggle Full Screen should not exist in the menu on Snow Leopard. Actual Result: Window > Toggle Full Screen exists and is grey/not selectable. Full Screen is not supported on Snow Leopard at this time.
| 3 |
train
|
TISTUD-1571
|
Titanium Studio: Dashboard: Generic External Browser Crashes Studio on Close
|
In the dashboard, when the ad link at the top is clicked ("Forging Titanium"), and the generic external browser is closed, studio will crash. Log attached. Also occurs in 2.0.1. This has only occurred using the "Forging Titanium" ad. You must refresh the dashboard until this ad appears. This issue is consistently reproducible. This issue affects Windows and Ubuntu, but I could not reproduce on OS X Snow Leopard. Steps to Reproduce: 1. Open Studio. 2. Open the dashboard. 3. Refresh the dashboard (red appcelerator logo) until the "Forging Titanium" ad appears at the top of the dashboard. 4. Click on the link to open a new generic browser with the ad content. 5. Close the browser. Expected Result: The browser should close. Actual Result: Studio hard crashes.
| 13 |
train
|
TISTUD-1574
|
Titanium Studio: Configuration: Ubuntu 11.10: top menu items intermittenly have random order
|
The top menu (File, Edit, Window, etc.) has randomly ordered elements on Ubuntu 11.10 intermittently. This does not occur on Ubuntu 10.04, Snow Leopard, or Windows 7. Screenshots attached. No log. Steps to Reproduce: 1. Open studio. 2. Look at the top menu. Expected Result: Menu items should be consistent. Actual Result: Intermittently, menu items are random, but do change to the correct configuration on a second check.
| 3 |
train
|
TISTUD-1576
|
Unable to package Android module on OSX
|
Prereqs Install Android SDK Install Android NDK Update settings in Titanium preferences Steps: 1. Create an android module project 2. Package the module Expected results Module is packaged Actual results: NPE in the AntRunner and this following error (Build 1.0.0.qualifier) [ERROR] /Users/nle/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.v20120410131722/module/android/build.xml:228: exec returned: 2 org.eclipse.core.runtime.CoreException: /Users/nle/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.v20120410131722/module/android/build.xml:228: exec returned: 2 org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:452) org.eclipse.ant.core.AntRunner.run(AntRunner.java:384) com.appcelerator.titanium.mobile.module.launching.AndroidModulePackageLaunchConfigurationDelegate$PackagingProcess$1.run(AndroidModulePackageLaunchConfigurationDelegate.java:241) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: /Users/nle/Library/Application Support/Titanium/mobilesdk/osx/2.0.1.v20120410131722/module/android/build.xml:228: exec returned: 2 org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:636) org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:662) org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:487) org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) org.apache.tools.ant.Task.perform(Task.java:348) org.apache.tools.ant.Target.execute(Target.java:357) org.apache.tools.ant.Target.performTasks(Target.java:385) org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337) org.apache.tools.ant.Project.executeTarget(Project.java:1306) org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32) org.apache.tools.ant.Project.executeTargets(Project.java:1189) org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:662) org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:495) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.ant.core.AntRunner.run(AntRunner.java:378)
| 13 |
train
|
TISTUD-1579
|
Given a URL to a module ZIP file, install the newer version
|
Add a dashboard controller when given the URL to a module .zip file, installs the module to the SDK location on disk. * Allow the user to choose either a global install, or a per-project install. * If for a specific project, update the tiapp.xml file (equivalent to what we do now when packaging a module for local distribution)
| 13 |
train
|
TISTUD-1581
|
Add support for launching BlackBerry debugger
|
The new Blackberry simulator utilizes a VMWare appliance. We'll need to launch against that. Improvements: # Add IP address override to launch configuration (see TISTUD-1597 for root IP specification) # Add password override to launch configuration (see TISTUD-1597 as well) Steps to use the integration: # Launch VMWare Device # Find out IP of device. User enters this in the main preference page, or in the launch configuration # Run launch script, passing in IP address, password as arguments: {panel} --ip_address=<address> # required --device_password=<password> # optional, for password-protected devices {panel}
| 20 |
train
|
TISTUD-1588
|
Create Mockup of new Studio Dashboard
|
This incorporates the new configuration tab, allowing users to choose between a "simple" and "advanced" perspective.
| 8 |
train
|
TISTUD-1590
|
Split titanium mobile plugin into ui and core plugins
| null | 8 |
train
|
TISTUD-1594
|
Upgrade Module wizard to support BlackBerry projects
|
Similar to other platforms, support the creation of BlackBerry modules. We don't yet know exactly the steps involved.
| 8 |
train
|
TISTUD-1605
|
Javascript preview code doesn't include "other parentheses" example code
|
1. Open Preferences > Studio > Formatter 2. Select javascript on the left of the pref page 3. Click the pencil icon to edit the profile 4. Select the "Spaces" tab The preview block of code doesn't seem to have any examples of the "Other parentheses" code, since changing those values don't seem to have any effect.
| 2 |
train
|
TISTUD-1610
|
Add a Preference page to manage Keystore certificates
|
We should adopt the Adobe AIR certificate management UI. See attached for Adobe AIR cert. management UI in Studio 1.5 (we can probably reuse this code) There should be a new Android preference page (similar to iOS), that contains a table of current keystore certificates, and an Add and Remove buttons
| 13 |
train
|
TISTUD-1611
|
Update the existing keystore dialog to allow users to either specify an existing keystore or create a new one
|
Add radio buttons to the dialog that allows the user to specify either an existing keystore from the disk or adding a new one. If an existing one is selected, we need to have a password field but not others.
| 8 |
train
|
TISTUD-1612
|
Update the Android distribution wizard/launch configuration to allow user to pick from the existing list of certificates (combo box), or to create a new one
|
-Replace the textbox with a combo box that contains the list of keystore certificates -The certificate added from the Browse button should automatically add the certificate to the list -New button will trigger the same keystore dialog as before
| 8 |
train
|
TISTUD-1613
|
Allow user to register their GitHub account inside Studio
|
I would like to be able to log in to my Github account and save my account information, possibly in our new "Accounts" preference page. Store: * Username * Password Additional buttons/links: * Test (to test the login credentials) * Sign up (to sign up for Github, which directs to the website)
| 13 |
train
|
TISTUD-1614
|
When importing a Git project, add available GitHub repos to the options
|
Update the Git import dialog: # Add a radio button in front of the existing URI option # Add another radio button with "Github" below. When the radio button is selected, it shows a list of repos in a dropdown via the Github REST API http://developer.github.com/v3/repos/ ## The destination field is shared between the two fields # If I have not logged into Github, show a message with "Add Github Account". Clicking on the link either pops up a u/p field in place, or directs me to the preference page to add the items # Once I've added the u/p, the page refreshes to show my repos. # If I select a Github repo, it then clones it into my local workspace
| 13 |
train
|
TISTUD-1615
|
Allow a user to upload a new project to GitHub
|
This assumes that the project has not created a local repo or the local repo has no remote. # Right click on a project # Team > Create on GitHub... ## Name of repo ## Description of repo ## Organization you wish to publish to ## Public/Private radio button See http://developer.github.com/v3/repos/ for information on publishing a new repo We should be proactive about seeing if we can test if a user has rights to create a repo within an organization, and if they have rights to make a repo private so we can alert them before the creation process.
| 13 |
train
|
TISTUD-1616
|
Add ability to log out of Jira account for "Submit a ticket"
|
Once logged into Jira inside Titanium Studio you cannot seem to log out and your name is retained between user logins. Steps to reproduce: 1. Log into Titanium Studio using one account. 2. Open Jira through the Help > Titanium Studio > Submit a ticket 3. Log into Jira via the top of the form and the validate button. 4. Log out of Titanium Studio. 5. Log into Titanium Studio using a second account. 6. Open Jira through the Help > Titanium Studio > Submit a ticket. Expected Result: Previous users Jira account should be cleared and the user should be prompted for username and password. Actual Result: The first user is still logged in with no way to log out.
| 8 |
train
|
TISTUD-1617
|
Submit a ticket wizard only submits the first line of the "Steps to reproduce" field.
|
When a user submits a ticket using the Submit a ticket Jira wizard only the first line of the steps to reproduce is passed into the Jira. Steps to reproduce: 1. Submit a ticket with multiple lines in the steps to reproduce field. Expected results: All lines will appear in the Jira ticket on the web site. Actual results: Only the first line is passed into the Jira.
| 5 |
train
|
TISTUD-1622
|
Need to be able to configure ACS url for staging testing purpose
|
Right now studio has hard coded api.cloud.appcelerator.com, in order to test in staging environment, we need to be able to change it to point to api.staging.cloud.appcelerator.com instead
| 5 |
train
|
TISTUD-1626
|
CLONE - Need to be able to select javascript modules from TiStudio Modules panel
|
With support for JavaScript (commonJS and MobileWeb) modules being added, we now need the ability to display and select javascript modules in the TiStudio Modules panel. # Show the (currently-hidden) modules # In the popup to select per-platform versions, for commonjs modules, only show a single drop down for selecting a version which will apply across all platforms.
| 8 |
train
|
TISTUD-1627
|
Add support for creating javascript modules to TiStudio
|
Add the ability to create a javascript module (commonJS or MobileWeb, depending on implementation of MOD-701).
| 8 |
train
|
TISTUD-1630
|
"Aptana" is shown under the main Help menu on Titanium Studio standalone installation
|
Not necessarily reproduceble, but on a brand new Titanium Studio installation on a Mac 10.7.2 machine, "Aptana" instead of "Titanium Studio" is displayed under Help. Also the preference page node has Aptana Studio instead Titanium Studio as well, so look like one or more overriding plugins didn't get loaded. Here is how I got into this state: 1. Download Titanium Studio 2.0.1 Mac zip from preview.appcelerator.com/studio; 2. Add http://preview.appcelerator.com/appcelerator/studio/standalone/update/beta/ update site and update to the latest 2.0.2 beta.
| 8 |
train
|
TISTUD-1631
|
File JIRA tickets for Titanium Studio in the "Titanium Community" project
|
When filing a ticket inside Titanium Studio using the new JIRA integration (APSTUD-2916), we need to file the ticket in APSTUD if it came from Aptana Studio, and TC if it came from Titanium community
| 8 |
train
|
TISTUD-1632
|
Re-configure JIRA ticket submission fields to better match current ticket guidelines
|
When filing a ticket in JIRA, we need to reconfigure the current fields ever so slightly. Instead of a single "Steps to Reproduce" we need three fields: * Steps to Reproduce* * Actual Result* * Expected Result (*d fields are required) From a space perspective, "Steps" should be 2X the height of the other two. When the ticket is filed, replace any empty fields with "N/A", and use the following template: {code} h3. Steps to Reproduce [Steps] h3. Actual Result [Actual] h3. Expected Result [Expected/N/A] {code}
| 8 |
train
|
TISTUD-1633
|
Titanium Studio: android module fails to create with internal error
|
When creating a module in studio, the creation fails with internal error: could not move file. Screenshot and log attached. This only occurs with android modules. However, android modules can be created from the command line. Steps to Reproduce: 1. Create new android module from studio. Expected Result: Module creates. Actual Result: Module fails to create.
| 8 |
train
|
TISTUD-1640
|
Titanium Studio: MobileWeb: preview in emulator/browser fails with NPE
|
When a mobileweb project is previewed in emulator or browser, there is a silent failure in the UI, and an NPE error in the log. Log attached. This does not occur in Studio 2.0.1. Steps to Reproduce: 1. Create a new mobileweb project. 2. Preview in Browser and Preview in Emulator. Expected Result: App should preview in browser or emulator. Actual Result: Silent UI failure (no popup, no visual response), null pointer exception logged to studio log.
| 5 |
train
|
TISTUD-1642
|
Titanium Studio: Login: studio does not auto-login on Linux
|
When studio launches, the user always has to enter login information (i.e., the auto-login never occurs). Steps to Reproduce: 1. Run studio on Linux. 2. Enter appcelerator login information. 3. Close and relaunch studio. Expected Result: Studio should auto-login. Actual Result: The user is prompted to enter studio login information every time.
| 13 |
train
|
TISTUD-1643
|
Remove the text in Windows installer about restarting the machine after uninstallation since it is not necessary
|
When studio is installed using the installer and the machine is rebooted after prompt, the installer does not relaunch on machine reboot. The installer must be manually run to continue the installation. Steps to Reproduce: 1. Run the studio installer on Windows. 2. Reboot the machine on prompt. Expected Result: Installer should relaunch after machine reboot. Actual Result: Installer does not relaunch. It must be manually relaunched to continue installation.
| 8 |
train
|
TISTUD-1645
|
Titanium Studio: Titanium Preferences: Default Android SDK changed if not saved and sdk path is reloaded
|
In Preferences > Titanium Studio > Titanium, if the Default Android SDK is changed and the user clicks on the Android SDK Home text field, then clicks in a different text field (e.g., Android NDK Home), the Default Android SDK change will be undone if it was not previously saved. This is a usability issue because the user's edits are automatically undone. Steps to Reproduce: 1. Go to Preferences > Titanium Studio > Titanium. 2. In the Default Android SDK drop-menu, change the SDK to a different version (but do not save the changes). 3. Click in the Android SDK Home text field. 4. Click in the Android NDK Home text field. Expected Result: The changes made to the Default Android SDK should remain. Actual Result: The old Default Android SDK is automatically selected.
| 5 |
train
|
TISTUD-1664
|
TiStudio: Encoding problem with Git Commit Message
|
Same problem on Ti Studio. https://jira.appcelerator.org/browse/APSTUD-4043 (Aptana bug) -------- The problem is that when i git commit with comments in Japanese(or Korean), i get unreadable by git log on terminal(utf-8). (I can read in Titanium studio history window. but unreadable by other tools) by the way, One repository that was make another machine (ex:ubuntsu) and it has commit message in UTF-8(Japanese). I Pull to Titanium Studio. The history is unreadable.
| 8 |
train
|
TISTUD-1647
|
Titanium Studio: MobileWeb: preview in android emulator initially fails with server errors when AVD is first created
|
When deploying from studio, or manually running a mobileweb app in the android emulator browser, the app will not run and server related errors log to the console when a new AVD is created. Logs attached. This is not a regression, as it does occur in Studio 2.0.1. Steps to Reproduce: 1. Delete .android/avd/ 2. Create a default mobileweb project. 3. MobileWeb Preview in Emulator. Expected Result: Emulator should launch, emulator browser should load, app should run. Actual Result: Emulator launches, emulator browser does not load. Manually opening the browser and navigating to the app url results in a failed app load.
| 8 |
train
|
TISTUD-1648
|
Titanium Studio: Modules: android modules created on command line cannot be packaged in studio
|
Android modules created from command line cannot be packaged in studio. There is no package option in the UI. Note: Android modules created in studio, and iPhone modules created from the command line, work as expected. Steps to Reproduce: 1. Create an android module from the command line. 2. Import the module into studio. 3. Attempt to package the module (i.e., box icon > Package Android Module). Expected Result: Package option should be available. Actual Result: Package option is not available. h3. Suggested solution When importing an existing Titanium project, check for the existence of a timodule.xml file, and set the builders/natures appropriately.
| 8 |
train
|
TISTUD-1649
|
Titanium Studio: MobileWeb: no option to package mobileweb modules
|
MobileWeb modules do not have the option to package from studio. Note: MobileWeb modules cannot be created in studio 2.0.1, so this feature cannot be tested in studio 2.0.1. This is a new fail case. Steps to Reproduce: 1. Create a mobileweb module. 2. Attempt to package the module (box icon > Package MobileWeb Module). Expected Result: The package option should be available in the packaging drop-down menu. Actual Result: There is no mobileweb module packaging option. MobileWeb projects can be created in studio, but not packaged.
| 13 |
train
|
TISTUD-1650
|
Titanium Studio: change default workspace to one without spaces to support module development
|
Currently, the default studio workspace is Titanium Studio Workspace. Because the workspace contains spaces, Android modules cannot be packaged. One suggestion is to change the default workspace to one without spaces to facilitate module development. As per discussion, it was suggested to use: Titanium_Studio_Workspace
| 5 |
train
|
TISTUD-1666
|
Restart of Titanium Studio Required for the tiapp editor to display modules added after Studio was launched
|
h3.Experience Currently, the list of modules appears to only be loaded into Titanium Studio at startup. Modules added to the Library folder after Titanium Studio has launched are not seen in the Modules pane of the tiapp editor. This requires a restart of Titanium Studio. h3.Expectation When the tiapp editor is opened that all modules are available for inclusion. h3. Solution Modules folder(s) needs to be rescanned when the tiapp editor is opened.
| 8 |
train
|
TISTUD-1656
|
App is created with NULL creator_user_id.
|
h4. Problem Description I published an App to the App Store and Google Play but the app never appeared on "My Apps". The original guid was: 2c9e1129-86d4-4f9d-9f0d-4d7bd0cd764a Because I noticed new projects showed up on "My Apps" I've created a new project and transplanted the guid to the tiapp.xml of my app. Released it to the Play Store and this enabled the app to show on "My Apps" where it says "122 analytics events were processed for this application since May 1, 2012" but it still shows 0 users, 0 sessions and "There were no events logged during between 5/7 and 5/13." The new guid is: 473b9203-836a-4d48-ac13-2993873efa2c I wrote more about this in http://developer.appcelerator.com/question/136456/my-app-doesnt-show-in-analytics but haven't received any feedback. Can you take a look?
| 5 |
train
|
TISTUD-1662
|
Editor: JavaScript Comment Auto-Complete initially fails to recognize preexisting blocks and cursor is incorrectly positioned
|
JavaScript Comment Auto-Complete initially fails to recognize preexisting blocks and cursor is incorrectly positioned. I am marking this as a bug because the auto-comment partially works, and I can get into this bad state. Screenshot attached. The auto-complete kicks in after pressing enter twice, but the cursor is on the wrong line. Steps to Reproduce: 1. Enter code in JS file: {code} /**/ {code} 2. Insert cursor between the two asterisks (in the middle of the block comment) and press enter. Note: A vertical bar character is used to simulate the resulting position of the cursor. Expected Result: {code} /* * | * */ {code} Actual Result: {code} /* |*/ {code} 3. Press enter again. Expected Result: {code} /* * * | */ {code} Actual Result: {code} /* *|*/ {code} 4. Press enter again. Expected Result: {code} /* * * * | */ {code} Actual Result: {code} /* * *|*/ {code}
| 8 |
train
|
TISTUD-1669
|
Titanium Studio: Preferences: cannot edit or leave titanium preferences menu with invalid values error
|
If the titanium preferences menu is opened, the user cannot navigate to a different menu. There is a pop-up with an invalid values error. Screenshot attached. Also, if individual titanium preferences are edited, the changes cannot be applied. The only way to leave the menu is to press cancel or close the entire preferences window. Screenshot attached. There are no log entries. This does not occur in 2.0.1 (regression). I do not believe this occurred in yesterday's build. Steps to Reproduce: 1. Open studio, navigate to the titanium preferences menu (Preferences > Titanium Studio > Titanium). 2. Attempt to navigate to a different menu (e.g., press General). Expected Result: The menu should change. Actual Result: Pop-up error indicating invalid values. Menu does not change. 3. Change the Android SDK version (or any setting in the titanium preferences menu). 4. Apply the changes (press Apply). Expected Result: The changes should be saved. Actual Result: Apply is not selectable. Note: The titanium preferences menu can only be exited by pressing Cancel or closing the entire preferences menu (press the window X).
| 5 |
train
|
TISTUD-1671
|
Titanium Studio: Multiline Search: enter newline keyboard shortcuts edit the wrong text area
|
When the multiline search box is up, and the enter new line keyboard shortcuts are used, the characters are entered in the active .js file instead of the search field. Screenshot attached. No log files. Not testable in studio 2.0.1 (new fail case). Command + Enter will add new lines to the .js file. Control + Enter will add visible '\n' characters to the end of the first line in the .js file. Steps to Reproduce: 1. Open studio, open a .js file (create a new project if necessary). 2. Open multiline search (Command + f in osx). 3. Click in the search box to give it focus and place the cursor inside the search box. 4. Press Command + Enter a few times (on osx only). 5. Press Control + Enter a few times. Expected Result: New lines should be added to the search box. Actual Result: New lines and visible '\n' characters are added to the active .js file.
| 8 |
train
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.