{
	"id": "124580",
	"key": "ALOY-922",
	"fields": {
		"issuetype": {
			"id": "1",
			"description": "A problem which impairs or prevents the functions of the product.",
			"name": "Bug",
			"subtask": false
		},
		"project": {
			"id": "11113",
			"key": "ALOY",
			"name": "Alloy",
			"projectCategory": {
				"id": "10400",
				"description": "Tools for developing applications",
				"name": "Tooling"
			}
		},
		"fixVersions": [
			{
				"id": "15758",
				"description": "Alloy 1.4.0",
				"name": "Alloy 1.4.0",
				"archived": false,
				"released": true,
				"releaseDate": "2014-07-17"
			},
			{
				"id": "15759",
				"description": "Alloy 1.3.1",
				"name": "Alloy 1.3.1",
				"archived": false,
				"released": true,
				"releaseDate": "2014-02-10"
			},
			{
				"id": "15815",
				"description": "2014 Sprint 01",
				"name": "2014 Sprint 01",
				"archived": true,
				"released": true,
				"releaseDate": "2014-01-17"
			}
		],
		"resolution": {
			"id": "1",
			"description": "A fix for this issue is checked into the tree and tested.",
			"name": "Fixed"
		},
		"resolutiondate": "2014-11-26T22:42:36.000+0000",
		"created": "2014-01-09T02:41:18.000+0000",
		"priority": {
			"name": "High",
			"id": "2"
		},
		"labels": [
			"qe-manualtest",
			"regression"
		],
		"versions": [
			{
				"id": "15403",
				"description": "Alloy 1.3.0",
				"name": "Alloy 1.3.0",
				"archived": false,
				"released": true,
				"releaseDate": "2013-12-20"
			}
		],
		"issuelinks": [],
		"assignee": {
			"name": "tlukasavage",
			"key": "tlukasavage",
			"displayName": "Tony Lukasavage",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"updated": "2014-11-26T22:42:36.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": "12326",
				"name": "XML",
				"description": "View XML and parsing"
			}
		],
		"description": "I looked in the release notes and didn't see anything that should cause this crash\r\n\r\nThis Alloy XML\r\n\r\n{code:xml}\r\n<Alloy>\r\n\t<Window id=\"settingsWin\" title=\"Settings\" class=\"container\" tabBarHidden=\"true\">\r\n        <ListView id=\"listView\" defaultItemTemplate=\"template\" allowsSelection=\"false\">\r\n            <Templates>\r\n                <ItemTemplate id=\"inputTemplate\" name=\"inputTemplate\">\r\n                \t<TextField bindId=\"textfield\" id=\"tf_username\" onChange=\"TFUpdate\" autocorrect=\"false\" keyboardType=\"TI.Ui.KEYBOARD_EMAIL\" hintText=\"User name / e-mail address\"></TextField>\r\n                </ItemTemplate>\r\n            </Templates>\r\n\r\n            <ListSection headerTitle=\"Login Id\" id=\"idSection\">\r\n                <ListItem template=\"inputTemplate\" textfield:value=\"\"/>\r\n            </ListSection>\r\n        </ListView>\r\n\t</Window>\r\n</Alloy>\r\n{code}\r\n\r\nGenerates JS code that crashes on\r\n\r\n{code}\r\n    TFUpdate ? $.__views.tf_username.addEventListener(\"change\", TFUpdate) : __defers[\"$.__views.tf_username!change!TFUpdate\"] = true;\r\n{code}\r\n\r\nbecause $.__views.tf_username is undefined\r\n\r\nThis used to work and now it crashes\r\n\r\nI don't believe that the definition of TFUpdate in the .js file is a factor. An empty definition should do.\r\n\r\n{code:javascript}\r\n    function TFUpdate(e) {\r\n    }\r\n{code}",
		"attachment": [],
		"flagged": false,
		"summary": "Alloy: Previously working code crashes with Alloy 1.3.0 + Titanium SDK 3.2.0",
		"creator": {
			"name": "dspells",
			"key": "dspells",
			"displayName": "Henry David Spells III",
			"active": true,
			"timeZone": "America/Chicago"
		},
		"subtasks": [],
		"reporter": {
			"name": "dspells",
			"key": "dspells",
			"displayName": "Henry David Spells III",
			"active": true,
			"timeZone": "America/Chicago"
		},
		"environment": "Mac OS X 10.9.1 build environment; Android or iOS device or emulator; 3.2.0 CLI; 3.2.0.GA SDK\r\n",
		"comment": {
			"comments": [
				{
					"id": "287847",
					"author": {
						"name": "ragrawal",
						"key": "ragrawal",
						"displayName": "Ritu Agrawal",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Moving this ticket to engineering for further evaluation as we can reproduce the issue with the provided test case on iOS simulator.",
					"updateAuthor": {
						"name": "ragrawal",
						"key": "ragrawal",
						"displayName": "Ritu Agrawal",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2014-01-12T04:00:58.000+0000",
					"updated": "2014-01-12T04:00:58.000+0000"
				},
				{
					"id": "288016",
					"author": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "commit: https://github.com/appcelerator/alloy/commit/6ae53d611ae7b5bfc719b86a1d9a65e7ec11e4b1\r\ntest app: https://github.com/appcelerator/alloy/tree/master/test/apps/testing/ALOY-922\r\n\r\nmerged to both master and 1_3_X\r\n\r\nFunctional test involves simply running the test app and asserting that the runtime error noted in the description does not occur. This requires no app interaction. If the error was still present it would occur immediately after the app loaded.",
					"updateAuthor": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2014-01-13T21:19:59.000+0000",
					"updated": "2014-01-13T21:19:59.000+0000"
				},
				{
					"id": "288083",
					"author": {
						"name": "dspells",
						"key": "dspells",
						"displayName": "Henry David Spells III",
						"active": true,
						"timeZone": "America/Chicago"
					},
					"body": "That's wonderful! Is there a way that I can find out when updates are scheduled without bothering you guys? I may need to put out an update of my app soon.",
					"updateAuthor": {
						"name": "dspells",
						"key": "dspells",
						"displayName": "Henry David Spells III",
						"active": true,
						"timeZone": "America/Chicago"
					},
					"created": "2014-01-14T08:12:46.000+0000",
					"updated": "2014-01-14T08:12:46.000+0000"
				},
				{
					"id": "288091",
					"author": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "[~dspells] this will be part of the official 1.3.1 Alloy release, but you can also get the beta right now.\n\n{code}\nnpm install -g alloy@1.3.1-beta3\n{code}",
					"updateAuthor": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2014-01-14T13:48:25.000+0000",
					"updated": "2014-01-14T13:48:25.000+0000"
				},
				{
					"id": "288097",
					"author": {
						"name": "dspells",
						"key": "dspells",
						"displayName": "Henry David Spells III",
						"active": true,
						"timeZone": "America/Chicago"
					},
					"body": "Thanks! That's very helpful.\r\n\r\nI did a \"sudo npm install -g alloy@1.3.1-beta3\" with titanium studio closed\r\nI verified that beta 3 was installed using npm -g list\r\nI opened titanium studio\r\nI did a clean\r\nI ran my project\r\nIt still gets the same error\r\nIs it possible that the changes aren't in beta3?",
					"updateAuthor": {
						"name": "dspells",
						"key": "dspells",
						"displayName": "Henry David Spells III",
						"active": true,
						"timeZone": "America/Chicago"
					},
					"created": "2014-01-14T15:42:55.000+0000",
					"updated": "2014-01-15T14:57:40.000+0000"
				},
				{
					"id": "288256",
					"author": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "[~dspells] Nope, just verified again and it is definitely in alloy@1.3.1-beta3. Run {{alloy --version}} to make sure your PATH is picking up the right version. Also, do the following to assert that there's nothing wrong with your npm setup:\n\n{code}\nsudo npm cache clean\nsudo npm uninstall -g alloy\nsudo npm install -g alloy@1.3.1-beta3\n{code}\n\nIf you are still getting the error in your app after this, try the test app I linked above to rule out any issues with your own code.",
					"updateAuthor": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2014-01-15T14:57:27.000+0000",
					"updated": "2014-01-15T14:57:27.000+0000"
				},
				{
					"id": "288263",
					"author": {
						"name": "dspells",
						"key": "dspells",
						"displayName": "Henry David Spells III",
						"active": true,
						"timeZone": "America/Chicago"
					},
					"body": "Thanks for the clue on what to look for! For some reason when I uninstalled alloy, Version 1.3.0 was still left on the hard drive. Installing 1.3.1-beta3 got installed but it still found 1.3.0 first in the path. I ended up uninstalling beta3, manually deleting the alloy folders for 1.3.0 that nom had lost track of and then re-installing beta3. This worked. I guess I should have uninstalled alloy before installing beta 3 in the first place.",
					"updateAuthor": {
						"name": "dspells",
						"key": "dspells",
						"displayName": "Henry David Spells III",
						"active": true,
						"timeZone": "America/Chicago"
					},
					"created": "2014-01-15T16:30:26.000+0000",
					"updated": "2014-01-15T16:30:26.000+0000"
				},
				{
					"id": "291304",
					"author": {
						"name": "fcasali",
						"key": "fcasali",
						"displayName": "Federico Casali",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Verified as fixed. \n\nTiSDK 3.2.1.v20140203174850\nAlloy 1.3.1-cr2\nCLI 3.2.1-beta3\nAppcelerator Studio 3.2.1.201402041206\t\niPhone 5 iOS 7\nAndroid Google Nexus Galaxy 4.3\n\nClosing",
					"updateAuthor": {
						"name": "fcasali",
						"key": "fcasali",
						"displayName": "Federico Casali",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2014-02-05T01:38:01.000+0000",
					"updated": "2014-02-05T01:38:01.000+0000"
				}
			],
			"maxResults": 11,
			"total": 11,
			"startAt": 0
		}
	}
}