{
	"id": "114835",
	"key": "AC-1892",
	"fields": {
		"issuetype": {
			"id": "1",
			"description": "A problem which impairs or prevents the functions of the product.",
			"name": "Bug",
			"subtask": false
		},
		"project": {
			"id": "12217",
			"key": "AC",
			"name": "Appcelerator - INBOX",
			"projectCategory": {
				"id": "10000",
				"description": "",
				"name": "Customer Service"
			}
		},
		"resolution": {
			"id": "1",
			"description": "A fix for this issue is checked into the tree and tested.",
			"name": "Fixed"
		},
		"resolutiondate": "2013-05-31T21:46:44.000+0000",
		"created": "2013-05-23T04:33:12.000+0000",
		"labels": [],
		"versions": [],
		"issuelinks": [
			{
				"id": "29060",
				"type": {
					"id": "10003",
					"name": "Relates",
					"inward": "relates to",
					"outward": "relates to"
				},
				"outwardIssue": {
					"id": "114690",
					"key": "TIMOB-13944",
					"fields": {
						"summary": "Android: build: TypeError: argument of type 'NoneType' is not iterable",
						"status": {
							"description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.",
							"name": "Closed",
							"id": "6",
							"statusCategory": {
								"id": 3,
								"key": "done",
								"colorName": "green",
								"name": "Done"
							}
						},
						"priority": {
							"name": "Critical",
							"id": "1"
						},
						"issuetype": {
							"id": "1",
							"description": "A problem which impairs or prevents the functions of the product.",
							"name": "Bug",
							"subtask": false
						}
					}
				}
			}
		],
		"assignee": {
			"name": "dsefton",
			"key": "dsefton",
			"displayName": "Daniel Sefton",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"updated": "2016-03-08T07:40:48.000+0000",
		"status": {
			"description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.",
			"name": "Closed",
			"id": "6",
			"statusCategory": {
				"id": 3,
				"key": "done",
				"colorName": "green",
				"name": "Done"
			}
		},
		"components": [
			{
				"id": "14551",
				"name": "Studio",
				"description": "Please enter tickets related to Titanium Studio here."
			}
		],
		"description": "I am trying to build a basic Android application using Titanium Studio using the Single Window application template.\r\n\r\nI am borrowing a Windows 7 machine from Russ McMahon which already had Titanium Studio installed some time ago. I updated his Titanium Studio to the latest stable version as of today. (3.1.0.GA I believe) to the point where no more updates are available.\r\n\r\nI installed the latest Android SDK and NDK (20130514 (installed API 17 and 8), NDK r8e) and setup the paths in Titanium Studio Preferences. \r\n\r\nAfter creating a new Single Window project, I am getting the following error when trying to build for the Android Emulator. (I did create an Emulator image.)\r\n\r\nTitanium Command-Line Interface, CLI version 3.1.0, Titanium SDK version 3.1.0.GA\r\n[ERROR] : \b\b \b\"Missing Java SDK. Please make sure Java SDK is on your PATH\r\nCopyright (c) 2012-2013, Appcelerator, Inc.  All Rights Reserved.\r\n[ERROR] Application Installer abnormal process termination. Process exit value was 1\r\n\r\n\r\n\r\nWhat is particularly strange is when I do a brand new Windows 8 installation in Virtual Box with a fresh Titanium install and the same Android SDK/NDK, I don't get this \"Missing Java SDK\" error. I was asked to report this bug. (You might need to talk to Russ about details of his machine setup.)\r\n\r\n\r\nRuss did confirm his Java is installed and in his path and wanted me to include the below.\r\n\r\n\r\n\r\nC:\\Users\\Russ>java --version\r\nUnrecognized option: --version\r\nError: Could not create the Java Virtual Machine.\r\nError: A fatal exception has occurred. Program will exit.\r\n\r\nC:\\Users\\Russ>path\r\nPATH=C:\\Windows\\system32;C:\\Windows;C:\\Windows\\System32\\Wbem;C:\\Windows\\System32\r\n\\WindowsPowerShell\\v1.0\\;C:\\Program Files (x86)\\Java\\jre7\\bin\\;C:\\Program Files\r\n(x86)\\nodejs\\;C:\\Users\\Russ\\AppData\\Roaming\\npm\\\r\n\r\n\r\n\r\n",
		"attachment": [],
		"flagged": false,
		"summary": "\"Missing Java SDK\" error when upgrading Titanium Studio (instead of fresh install)",
		"creator": {
			"name": "ewing",
			"key": "ewing",
			"displayName": "Eric Wing",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"subtasks": [],
		"reporter": {
			"name": "ewing",
			"key": "ewing",
			"displayName": "Eric Wing",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"environment": "Windows 7",
		"comment": {
			"comments": [
				{
					"id": "253696",
					"author": {
						"name": "dsefton",
						"key": "dsefton",
						"displayName": "Daniel Sefton",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Hi Eric,\n\nBefore I look deeper into this, there's a problem with the command you entered to get the Java version. It should be:\n\n{code}java -version{code}\n\nAlso run:\n\n{code}javac -version{code}\n\nThanks.",
					"updateAuthor": {
						"name": "dsefton",
						"key": "dsefton",
						"displayName": "Daniel Sefton",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-05-23T18:55:36.000+0000",
					"updated": "2013-05-23T18:55:36.000+0000"
				},
				{
					"id": "253729",
					"author": {
						"name": "ewing",
						"key": "ewing",
						"displayName": "Eric Wing",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "java version \"1.7.0_21\"\nJava(TM) SE Runtime Environment (build 1.7.0_21-b11)\nJava HotSpot(TM) Client VM (build 23.21-b01, mixed mode, sharing)\n\n\njavac wasn't found.\n\n------\nOn the fresh install system which doesn't have this problem, it says\njava version \"1.6.0_25\"\nand\njavac 1.6.0_25\n\n\n\n",
					"updateAuthor": {
						"name": "ewing",
						"key": "ewing",
						"displayName": "Eric Wing",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-05-23T21:29:06.000+0000",
					"updated": "2013-05-23T21:29:06.000+0000"
				},
				{
					"id": "253742",
					"author": {
						"name": "dsefton",
						"key": "dsefton",
						"displayName": "Daniel Sefton",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Hi Eric,\n\nYou'll find this guide useful:\n\nhttp://developer.appcelerator.com/doc/mobile/mobile-build-windows\n\nSources say that Java 1.6 is required; I haven't actually tried it with 1.7 myself though. I have a feeling it might work, but it does need to be able to locate javac.\n\nIt also took me a while to get the environment variable paths right for it to be able to locate javac.\n\nAdd this to your \"System variables\" \"Path\":\n\n{code}%JAVA_HOME%\\bin;{code}\n\nAdd this variable to your \"System variables\":\n\n{code}JAVA_HOME{code}\n{code}C:\\Java\\jdk1.7.0_21{code}",
					"updateAuthor": {
						"name": "dsefton",
						"key": "dsefton",
						"displayName": "Daniel Sefton",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-05-23T22:13:45.000+0000",
					"updated": "2013-05-23T22:13:45.000+0000"
				},
				{
					"id": "253752",
					"author": {
						"name": "ewing",
						"key": "ewing",
						"displayName": "Eric Wing",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Okay. This was not my computer. I was trying to diagnose a different install error. They wanted me to try on a direct install instead of a virtual machine. This led me to this error and a completely different set of errors.\n\nFYI, the Android team said at Google I/O they already fixed the 1.7 incompatibility problems and already ships in their tools (r22?).",
					"updateAuthor": {
						"name": "ewing",
						"key": "ewing",
						"displayName": "Eric Wing",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-05-23T22:48:28.000+0000",
					"updated": "2013-05-23T22:48:28.000+0000"
				},
				{
					"id": "253761",
					"author": {
						"name": "dsefton",
						"key": "dsefton",
						"displayName": "Daniel Sefton",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "So are you going to try what I suggested?\n\nBtw, you may also run into a different bug with the new r22 toolset changes, which we fixed in TIMOB-13944. A workaround is included.",
					"updateAuthor": {
						"name": "dsefton",
						"key": "dsefton",
						"displayName": "Daniel Sefton",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-05-23T23:20:30.000+0000",
					"updated": "2013-05-23T23:20:30.000+0000"
				},
				{
					"id": "253800",
					"author": {
						"name": "ewing",
						"key": "ewing",
						"displayName": "Eric Wing",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"updateAuthor": {
						"name": "ewing",
						"key": "ewing",
						"displayName": "Eric Wing",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-05-24T01:55:59.000+0000",
					"updated": "2013-05-24T01:55:59.000+0000"
				},
				{
					"id": "253891",
					"author": {
						"name": "dsefton",
						"key": "dsefton",
						"displayName": "Daniel Sefton",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Hi Eric,\n\nAs you probably saw we fixed the build for Windows in TIMOB-13944.\n\nLet me know if it works.\n\nThanks.",
					"updateAuthor": {
						"name": "dsefton",
						"key": "dsefton",
						"displayName": "Daniel Sefton",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-05-24T18:35:55.000+0000",
					"updated": "2013-05-24T18:35:55.000+0000"
				},
				{
					"id": "255275",
					"author": {
						"name": "dsefton",
						"key": "dsefton",
						"displayName": "Daniel Sefton",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "I'm going to assume this was fixed. Let me know if you continue to have problems related to this. But I think you resolved the \"missing java SDK\" error; and the NodeType error has been resolved on Windows by our team; any new unrelated problems with your installation and you should probably open a new report.\r\n\r\nCheers.",
					"updateAuthor": {
						"name": "dsefton",
						"key": "dsefton",
						"displayName": "Daniel Sefton",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-05-31T21:46:44.000+0000",
					"updated": "2013-05-31T21:46:44.000+0000"
				}
			],
			"maxResults": 8,
			"total": 8,
			"startAt": 0
		}
	}
}