{
	"id": "155235",
	"key": "TIMOB-25194",
	"fields": {
		"issuetype": {
			"id": "1",
			"description": "A problem which impairs or prevents the functions of the product.",
			"name": "Bug",
			"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": [],
		"resolution": null,
		"resolutiondate": null,
		"created": "2016-03-01T06:19:36.000+0000",
		"priority": {
			"name": "High",
			"id": "2"
		},
		"labels": [
			"androidlib",
			"cb-tooling"
		],
		"versions": [
			{
				"id": "16997",
				"name": "Release 5.2.0",
				"archived": false,
				"released": true,
				"releaseDate": "2016-02-23"
			}
		],
		"issuelinks": [
			{
				"id": "58149",
				"type": {
					"id": "10003",
					"name": "Relates",
					"inward": "relates to",
					"outward": "relates to"
				},
				"outwardIssue": {
					"id": "170042",
					"key": "TIMOB-25406",
					"fields": {
						"summary": "Android: First run for emulator doesn't see emulator started",
						"status": {
							"description": "The issue is open and ready for the assignee to start work on it.",
							"name": "Open",
							"id": "1",
							"statusCategory": {
								"id": 2,
								"key": "new",
								"colorName": "blue-gray",
								"name": "To Do"
							}
						},
						"issuetype": {
							"id": "1",
							"description": "A problem which impairs or prevents the functions of the product.",
							"name": "Bug",
							"subtask": false
						}
					}
				}
			},
			{
				"id": "58148",
				"type": {
					"id": "10003",
					"name": "Relates",
					"inward": "relates to",
					"outward": "relates to"
				},
				"inwardIssue": {
					"id": "153203",
					"key": "TIMOB-19995",
					"fields": {
						"summary": "CLI: Android build intermittently fails to recognize emulator is ready",
						"status": {
							"description": "The issue is open and ready for the assignee to start work on it.",
							"name": "Open",
							"id": "1",
							"statusCategory": {
								"id": 2,
								"key": "new",
								"colorName": "blue-gray",
								"name": "To Do"
							}
						},
						"priority": {
							"name": "High",
							"id": "2"
						},
						"issuetype": {
							"id": "1",
							"description": "A problem which impairs or prevents the functions of the product.",
							"name": "Bug",
							"subtask": false
						}
					}
				}
			},
			{
				"id": "58174",
				"type": {
					"id": "10003",
					"name": "Relates",
					"inward": "relates to",
					"outward": "relates to"
				},
				"inwardIssue": {
					"id": "170512",
					"key": "DAEMON-199",
					"fields": {
						"summary": "androidlib: Emulator and Device APIs",
						"status": {
							"description": "The issue is open and ready for the assignee to start work on it.",
							"name": "Open",
							"id": "1",
							"statusCategory": {
								"id": 2,
								"key": "new",
								"colorName": "blue-gray",
								"name": "To Do"
							}
						},
						"priority": {
							"name": "Medium",
							"id": "3"
						},
						"issuetype": {
							"id": "4",
							"description": "An improvement or enhancement to an existing feature or task.",
							"name": "Improvement",
							"subtask": false
						}
					}
				}
			}
		],
		"assignee": null,
		"updated": "2020-03-06T21:38:45.000+0000",
		"status": {
			"description": "The issue is open and ready for the assignee to start work on it.",
			"name": "Open",
			"id": "1",
			"statusCategory": {
				"id": 2,
				"key": "new",
				"colorName": "blue-gray",
				"name": "To Do"
			}
		},
		"components": [],
		"description": "When trying to build an Android app using Appc Studio, Studio is always trying to open a new emulator, even if the emulator is already open. In some cases the emulator will open and successfully install, run the application - but this also fails a majority of the time seemingly related to a timeout issue.\r\n\r\nThis is happening using both genymotion and Android emulators.\r\n\r\nI'll try and gather more information from the user.\r\n\r\n",
		"attachment": [],
		"flagged": false,
		"summary": "Android: Studio does not recognize currently running emulators; Always launches new emulator on Windows OS",
		"creator": {
			"name": "bgrantges@appcelerator.com",
			"key": "bgrantges",
			"displayName": "Bert Grantges",
			"active": false,
			"timeZone": "America/Chicago"
		},
		"subtasks": [],
		"reporter": {
			"name": "bgrantges@appcelerator.com",
			"key": "bgrantges",
			"displayName": "Bert Grantges",
			"active": false,
			"timeZone": "America/Chicago"
		},
		"environment": "Studio 4.5.0\r\nWindows 7",
		"comment": {
			"comments": [
				{
					"id": "378235",
					"author": {
						"name": "kkolipaka",
						"key": "kkolipaka",
						"displayName": "Kondal Kolipaka",
						"active": false,
						"timeZone": "America/Los_Angeles"
					},
					"body": "[~ewieber] [~wluu] Are you able to see this behaviour, can you guys add your findings on this with the latest environment.",
					"updateAuthor": {
						"name": "kkolipaka",
						"key": "kkolipaka",
						"displayName": "Kondal Kolipaka",
						"active": false,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2016-03-01T06:38:37.000+0000",
					"updated": "2016-03-01T06:38:37.000+0000"
				},
				{
					"id": "378562",
					"author": {
						"name": "bgrantges@appcelerator.com",
						"key": "bgrantges",
						"displayName": "Bert Grantges",
						"active": false,
						"timeZone": "America/Chicago"
					},
					"body": "Here is more info on the users environment\r\n\r\nC:\\>node --version\r\nv4.2.2\r\n \r\nC:\\>java -version\r\njava version \"1.8.0_71\"\r\nJava(TM) SE Runtime Environment (build 1.8.0_71-b15)\r\nJava HotSpot(TM) 64-Bit Server VM (build 25.71-b15, mixed mode)\r\n \r\nGenymotion Version 2.6.0\r\nRevision 20151127-3674435\r\n \r\nWindows 7 Enterprise, Service Pack 1\r\nCpu i5-3340M\r\nRam 16 GB",
					"updateAuthor": {
						"name": "bgrantges@appcelerator.com",
						"key": "bgrantges",
						"displayName": "Bert Grantges",
						"active": false,
						"timeZone": "America/Chicago"
					},
					"created": "2016-03-03T09:02:58.000+0000",
					"updated": "2016-03-03T09:02:58.000+0000"
				},
				{
					"id": "378563",
					"author": {
						"name": "bgrantges@appcelerator.com",
						"key": "bgrantges",
						"displayName": "Bert Grantges",
						"active": false,
						"timeZone": "America/Chicago"
					},
					"body": "Here is more info on the users environment\r\n\r\nC:\\>node --version\r\nv4.2.2\r\n \r\nC:\\>java -version\r\njava version \"1.8.0_71\"\r\nJava(TM) SE Runtime Environment (build 1.8.0_71-b15)\r\nJava HotSpot(TM) 64-Bit Server VM (build 25.71-b15, mixed mode)\r\n \r\nGenymotion Version 2.6.0\r\nRevision 20151127-3674435\r\n \r\nWindows 7 Enterprise, Service Pack 1\r\nCpu i5-3340M\r\nRam 16 GB",
					"updateAuthor": {
						"name": "bgrantges@appcelerator.com",
						"key": "bgrantges",
						"displayName": "Bert Grantges",
						"active": false,
						"timeZone": "America/Chicago"
					},
					"created": "2016-03-03T09:12:19.000+0000",
					"updated": "2016-03-03T09:12:19.000+0000"
				},
				{
					"id": "378745",
					"author": {
						"name": "kkolipaka",
						"key": "kkolipaka",
						"displayName": "Kondal Kolipaka",
						"active": false,
						"timeZone": "America/Los_Angeles"
					},
					"body": "[~cng]  There are 2 issues here:\r\n1. Timeout during app launch/emulator launch \r\n2. Opening a new emulator for every build\r\n\r\n*Timeout during build:*\r\nThis is happening both in windows and mac os platforms.\r\nAnd this is not consistent - I tried 5 times, only once it was able to launch the emulator and installed the app.\r\n\r\nBelow are the various errors which I encountered during the build, but most of the time it was timeout.\r\n\r\n{code}\r\n[INFO] :   Waiting for emulator to become ready...\r\n[ERROR] :  Emulator failed to start in a timely manner\r\nThe current timeout is set to 120000 ms\r\nYou can increase this timeout by running: titanium.js config android.emulatorStartTimeout <timeout ms>\r\n{code}\r\n\r\n\r\n{code}\r\n[INFO] :   Emulator ready!\r\n[INFO] :   Installing apk: /Users/kondalkolipaka/development/workspaces/runtime-Titanium-360/productionapp/build/android/bin/productionapp.apk\r\n[ERROR] :  Application failed to install\r\nThe current timeout is set to 240000 ms\r\nYou can increase this timeout by running: titanium.js config android.appInstallTimeout <timeout ms>\r\n{code}\r\n\r\n\r\n{code}\r\n[INFO] :   Making sure the adb server is running\r\n[INFO] :   Installing apk: /Users/kondalkolipaka/development/workspaces/runtime-Titanium-360/productionapp/build/android/bin/productionapp.apk\r\n[ERROR] :  Failed to install apk on \"emulator-5554\"\r\n[ERROR] :  Error: INSTALL_FAILED_INVALID_URI\r\n{code}\r\n\r\n*Android emulator issue:*\r\nIn windows os, for every build new android emulator is getting launched. I could see, for every build it's assigning a new port and launching a new emulator. The interesting thing here is, even though it started a new emulator but app is getting launched in the old emulator!\r\nIn mac os, I don't see this issue, same emulator is getting used for everybuild.\r\n\r\n\r\n{code}\r\n Running: C:\\android-sdk-win\\tools\\emulator.exe \"-avd\" \"testNexus5\" \"-port\" \"5558\" \"-no-boot-anim\" \"-partition-size\" \"128\"\r\n{code}\r\n",
					"updateAuthor": {
						"name": "kkolipaka",
						"key": "kkolipaka",
						"displayName": "Kondal Kolipaka",
						"active": false,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2016-03-04T07:08:37.000+0000",
					"updated": "2016-03-04T07:08:37.000+0000"
				}
			],
			"maxResults": 7,
			"total": 7,
			"startAt": 0
		}
	}
}