{
	"id": "167619",
	"key": "TIMOB-24694",
	"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": "2017-05-15T12:34:21.000+0000",
		"priority": {
			"name": "None",
			"id": "6"
		},
		"labels": [],
		"versions": [],
		"issuelinks": [],
		"assignee": {
			"name": "eharris",
			"key": "eharris",
			"displayName": "Ewan Harris",
			"active": true,
			"timeZone": "Europe/Dublin"
		},
		"updated": "2018-12-19T15:11:02.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": [
			{
				"id": "13600",
				"name": "LiveView",
				"description": "Live preview of Titanium apps"
			}
		],
		"description": "h5.Description\r\n\r\nWhen passing in a custom IP that does not resolve, LiveView will try to start up and then silently fail with no feedback to the user.\r\n\r\nIt should not silently fail and let the build continue as the app will go on and launch as normal, giving the user the impression that the server launched fine. At the very least it should log a big nasty error\r\n\r\nh5.Steps to reproduce\r\n\r\n# Build a app with {{--liveview --liveview-ip 123.4.5.6}}\r\n# Wait for the app to launch\r\n\r\nh5.Actual\r\n\r\nApp starts up and errors out, console gives no impression of any issues with the server other than the absence of the LiveView\r\n\r\nh5.Expected\r\n\r\nSome sort of representation to the user that the LiveView server failed to start",
		"attachment": [],
		"flagged": false,
		"summary": "LiveView: No errors reported to user if the LiveView server process errors",
		"creator": {
			"name": "eharris",
			"key": "eharris",
			"displayName": "Ewan Harris",
			"active": true,
			"timeZone": "Europe/Dublin"
		},
		"subtasks": [],
		"reporter": {
			"name": "eharris",
			"key": "eharris",
			"displayName": "Ewan Harris",
			"active": true,
			"timeZone": "Europe/Dublin"
		},
		"environment": "LiveView:1.1.12\r\nAppc Studio: 4.9.0.201705121309",
		"comment": {
			"comments": [
				{
					"id": "419671",
					"author": {
						"name": "eharris",
						"key": "eharris",
						"displayName": "Ewan Harris",
						"active": true,
						"timeZone": "Europe/Dublin"
					},
					"body": "Dropping some debug logs in, looks like the console.error call [here|https://github.com/appcelerator/liveview/blob/4de3f39330fcd6de5ca90b406f4b94c4feaf32d1/lib/fserver.js#L31]- is getting clobbered somehow-. Changing it to a .log allows the log from [here|https://github.com/appcelerator/liveview/blob/4de3f39330fcd6de5ca90b406f4b94c4feaf32d1/lib/fserver.js#L480] to get through.\r\n\r\nDuh, the stderr just isn't coming through the to parent process",
					"updateAuthor": {
						"name": "eharris",
						"key": "eharris",
						"displayName": "Ewan Harris",
						"active": true,
						"timeZone": "Europe/Dublin"
					},
					"created": "2017-05-15T12:52:37.000+0000",
					"updated": "2017-05-15T13:20:48.000+0000"
				},
				{
					"id": "419719",
					"author": {
						"name": "eharris",
						"key": "eharris",
						"displayName": "Ewan Harris",
						"active": true,
						"timeZone": "Europe/Dublin"
					},
					"body": "This isnt specific to the LiveView server starting but all errors in that spawned process",
					"updateAuthor": {
						"name": "eharris",
						"key": "eharris",
						"displayName": "Ewan Harris",
						"active": true,
						"timeZone": "Europe/Dublin"
					},
					"created": "2017-05-15T18:37:51.000+0000",
					"updated": "2017-05-15T18:37:51.000+0000"
				},
				{
					"id": "438784",
					"author": {
						"name": "eharris",
						"key": "eharris",
						"displayName": "Ewan Harris",
						"active": true,
						"timeZone": "Europe/Dublin"
					},
					"body": "This may be irrelevant with the changing from spawning the liveview process to using FServer directly",
					"updateAuthor": {
						"name": "eharris",
						"key": "eharris",
						"displayName": "Ewan Harris",
						"active": true,
						"timeZone": "Europe/Dublin"
					},
					"created": "2018-06-27T21:47:34.000+0000",
					"updated": "2018-06-27T21:47:34.000+0000"
				},
				{
					"id": "444739",
					"author": {
						"name": "eharris",
						"key": "eharris",
						"displayName": "Ewan Harris",
						"active": true,
						"timeZone": "Europe/Dublin"
					},
					"body": "This error is still getting squashed because we're running the startServer function in the liveview hook from within a domain, those are deprecated and I don't really understand why we do that anyways. Would be good to fix this",
					"updateAuthor": {
						"name": "eharris",
						"key": "eharris",
						"displayName": "Ewan Harris",
						"active": true,
						"timeZone": "Europe/Dublin"
					},
					"created": "2018-12-19T15:11:02.000+0000",
					"updated": "2018-12-19T15:11:02.000+0000"
				}
			],
			"maxResults": 5,
			"total": 5,
			"startAt": 0
		}
	}
}