{
	"id": "124446",
	"key": "TIMOB-16132",
	"fields": {
		"issuetype": {
			"id": "2",
			"description": "A new feature of the product, which has yet to be developed.",
			"name": "New Feature",
			"subtask": false
		},
		"project": {
			"id": "10153",
			"key": "TIMOB",
			"name": "Titanium SDK/CLI",
			"projectCategory": {
				"id": "10100",
				"description": "Titanium and related SDKs used in application development",
				"name": "Client"
			}
		},
		"fixVersions": [
			{
				"id": "16092",
				"description": "2014 Sprint 08",
				"name": "2014 Sprint 08",
				"archived": true,
				"released": true,
				"releaseDate": "2014-04-24"
			},
			{
				"id": "16095",
				"description": "2014 Sprint 08 Tooling",
				"name": "2014 Sprint 08 Tooling",
				"archived": true,
				"released": true,
				"releaseDate": "2014-04-24"
			},
			{
				"id": "15422",
				"description": "Release 3.3.0",
				"name": "Release 3.3.0",
				"archived": false,
				"released": true,
				"releaseDate": "2014-07-16"
			}
		],
		"resolution": {
			"id": "1",
			"description": "A fix for this issue is checked into the tree and tested.",
			"name": "Fixed"
		},
		"resolutiondate": "2015-04-13T16:27:28.000+0000",
		"created": "2014-01-07T00:38:56.000+0000",
		"priority": {
			"name": "High",
			"id": "2"
		},
		"labels": [
			"module_debugger",
			"qe-testadded"
		],
		"versions": [
			{
				"id": "14982",
				"description": "Release 3.2.0",
				"name": "Release 3.2.0",
				"archived": false,
				"released": true,
				"releaseDate": "2013-12-19"
			}
		],
		"issuelinks": [
			{
				"id": "36968",
				"type": {
					"id": "10002",
					"name": "Duplicate",
					"inward": "is duplicated by",
					"outward": "duplicates"
				},
				"inwardIssue": {
					"id": "125326",
					"key": "TIMOB-16305",
					"fields": {
						"summary": "Android: Alloy Projects Stuck at Splash screen (Samsung Note 10.1)",
						"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": "Medium",
							"id": "3"
						},
						"issuetype": {
							"id": "1",
							"description": "A problem which impairs or prevents the functions of the product.",
							"name": "Bug",
							"subtask": false
						}
					}
				}
			}
		],
		"assignee": {
			"name": "cbarber",
			"key": "cbarber",
			"displayName": "Chris Barber",
			"active": true,
			"timeZone": "America/Chicago"
		},
		"updated": "2015-04-13T16:27:31.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": "10202",
				"name": "Android",
				"description": "Android Platform"
			},
			{
				"id": "13103",
				"name": "CLI",
				"description": "Node-based command line interface"
			}
		],
		"description": "Android debug builds places a deploy.json file in the /sdcard/<app id>/ directory that contains the debug server information. It's possible in certain circumstances that this file is not properly removed for non-debug builds. This is a problem since the presence of the deploy.json means you are debugging or profiling and the app appears to hang.\r\n\r\nIt would be better if we bake the deploy.json into the packaged APK file. This has several benefits:\r\n\r\n1. Ties debug sessions to debug builds\r\n2. Installing non-debug apps will cause the debug settings to be wiped\r\n3. Wouldn't need to wait for the device/emulator SD card to mount\r\n4. Wouldn't require a device/emulator to have an SD card\r\n5. Wouldn't require the WRITE_EXTERNAL_STORAGE permission",
		"attachment": [],
		"flagged": false,
		"summary": "CLI: Android: Bake deploy.json into built apk",
		"creator": {
			"name": "cbarber",
			"key": "cbarber",
			"displayName": "Chris Barber",
			"active": true,
			"timeZone": "America/Chicago"
		},
		"subtasks": [],
		"reporter": {
			"name": "cbarber",
			"key": "cbarber",
			"displayName": "Chris Barber",
			"active": true,
			"timeZone": "America/Chicago"
		},
		"environment": null,
		"comment": {
			"comments": [
				{
					"id": "289677",
					"author": {
						"name": "ingo",
						"key": "ingo",
						"displayName": "Ingo Muschenetz",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Note: We need a separate ticket for the Android SDK pieces.",
					"updateAuthor": {
						"name": "ingo",
						"key": "ingo",
						"displayName": "Ingo Muschenetz",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2014-01-25T00:25:29.000+0000",
					"updated": "2014-01-25T00:25:29.000+0000"
				},
				{
					"id": "293572",
					"author": {
						"name": "ffabreti",
						"key": "ffabreti",
						"displayName": "f",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Today, I've installed VERSION 3.3.0.2014 02 12 1458 BUILD 2014 02 12 1458 and had no lucky running emulator after stopping a debug built from STUDIO. App keeps stuck on the splash screen.\r\nInside adb shell I see the culprit:\r\n\r\n# ls -l /mnt/sdcard/com.fabreti.test4\r\n----rwxr-x system   sdcard_rw       87 2014-02-18 15:41 deploy.json\r\n#  rm /mnt/sdcard/com.fabreti.test4/deploy.json\r\n\r\nAfter removing it, I can 'run' app with success on emulator.\r\n\r\n=== EDIT ====\r\nI'd like to add that above problem does NOT occur with android API 17, but with API 15 and 16.\r\n\r\n*Meanwhile, Is there any workaround for this?*\r\n\r\nI don't know if its related, but since 3.2.1 GA could not get debug to work, same problem: App keeps stuck on the splash screen when loading debug session. I'm talking about fresh new barebone app. (this occurs with android APIs 15, 16 and 17)\r\n\r\n=== EDIT2 ===\r\nDebugging session freezing at splash screen was because this error:\r\n(Build 3.3.0.201402121458) [ERROR] spock: spock: Name or service unknown\r\n\"spock\" is node name for my Linux machine (uname -n) and it was NOT defined in /etc/hosts\r\nafter inserting \"127.0.0.1 spock\" at end of /etc/hosts it worked.\r\nsorry for that one.\r\n\r\n",
					"updateAuthor": {
						"name": "ffabreti",
						"key": "ffabreti",
						"displayName": "f",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2014-02-18T19:00:58.000+0000",
					"updated": "2014-02-19T10:49:29.000+0000"
				},
				{
					"id": "301623",
					"author": {
						"name": "cbarber",
						"key": "cbarber",
						"displayName": "Chris Barber",
						"active": true,
						"timeZone": "America/Chicago"
					},
					"body": "Master pull request: https://github.com/appcelerator/titanium_mobile/pull/5632\r\n\r\nTo test, run an Android app in the emulator and device. Then debug the app on emulator and device. For fun, test using an emulator that doesn't have an SD card.",
					"updateAuthor": {
						"name": "cbarber",
						"key": "cbarber",
						"displayName": "Chris Barber",
						"active": true,
						"timeZone": "America/Chicago"
					},
					"created": "2014-04-20T21:18:28.000+0000",
					"updated": "2014-04-20T21:18:28.000+0000"
				}
			],
			"maxResults": 3,
			"total": 3,
			"startAt": 0
		}
	}
}