{ "id": "145025", "key": "TIMOB-18600", "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": "2015-02-20T21:38:13.000+0000", "priority": { "name": "High", "id": "2" }, "labels": [ "cb-tooling", "engTriage", "qe-3.5.1" ], "versions": [ { "id": "16711", "description": "Release 3.5.1", "name": "Release 3.5.1", "archived": false, "released": true, "releaseDate": "2015-03-06" } ], "issuelinks": [ { "id": "47324", "type": { "id": "10002", "name": "Duplicate", "inward": "is duplicated by", "outward": "duplicates" }, "inwardIssue": { "id": "146601", "key": "TISTUD-7385", "fields": { "summary": "LiveView sees (dot)files as languages", "status": { "description": "A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.", "name": "Resolved", "id": "5", "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 } } } }, { "id": "46182", "type": { "id": "10003", "name": "Relates", "inward": "relates to", "outward": "relates to" }, "inwardIssue": { "id": "126971", "key": "TIMOB-16519", "fields": { "summary": "Liveview : On genymotion android throws 'File Server unavailable. Host Unreachable' error", "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": "Low", "id": "4" }, "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false } } } } ], "assignee": null, "updated": "2020-01-08T19:03:45.000+0000", "status": { "description": "This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.", "name": "Reopened", "id": "4", "statusCategory": { "id": 2, "key": "new", "colorName": "blue-gray", "name": "To Do" } }, "components": [ { "id": "10202", "name": "Android", "description": "Android Platform" }, { "id": "13600", "name": "LiveView", "description": "Live preview of Titanium apps" } ], "description": "h5.Description\r\n\r\nWhen attempting to build to an Android emulator the build fails with.\r\n\r\n{code}\r\n [ERROR] : TiExceptionHandler: (main) [9499,9499] ----- Titanium Javascript Runtime Error -----\r\n [ERROR] : TiExceptionHandler: (main) [1,9500] - In app.js:567,13\r\n [ERROR] : TiExceptionHandler: (main) [1,9501] - Message: Uncaught Error: [LiveView] File Server unavailable. Host Unreachable @ 172.16.0.216:8324\r\n [ERROR] : TiExceptionHandler: [LiveView] Please ensure your device and computer are on the same network and the port is not blocked.\r\n{code}\r\n\r\nI *do not believe this is a regression* as it has been reported in previous versions of LiveView\r\n\r\nTo workaround just disable LiveView and the build will be fine\r\n \r\nBuilding to device with LiveView works fine and I am able to make changes with no errors\r\nChecking the log output shows that the LiveView server has started \r\n\r\n{code}\r\n[LiveView] version 1.0.7\r\n[LiveView] File Server Started on Port 8324\r\n[LiveView] Alloy project monitor started\r\n[LiveView] Event Server Started on Port 8323\r\n{code}\r\n\r\n\r\nThis issue is not reliant on a node version, it occurs in node 0.12 as well as 0.10.32\r\nh5.Steps To Reproduce\r\n\r\n1. Build to an Android emulator from Studio with LiveView enabled\r\n\r\nh5.Actual Result\r\n\r\nThe build fails with the error above\r\n\r\nh5.Expected Result\r\n\r\nThe build should not fail and LiveView should be working as expected", "attachment": [], "flagged": false, "summary": "LiveView: Building to an Android emulator fails with [LiveView] File Server unavailable. Host Unreachable", "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": "Mac OSX 10.10.2\r\nAppcelerator Studio, build: 3.4.2.201502181619\r\nTitanium SDK build: 3.5.1.v20150219140555\r\nTitanium CLI, build: 3.4.2-alpha\r\nAlloy: 1.5.1\r\nAndroid Emulator 5.0.1\r\nLiveView 1.0.7", "closedSprints": [ { "id": 339, "state": "closed", "name": "2015 Sprint 04 Tooling", "startDate": "2015-02-14T02:34:21.061Z", "endDate": "2015-02-28T02:34:00.000Z", "completeDate": "2015-02-28T15:51:32.596Z", "originBoardId": 121 } ], "comment": { "comments": [ { "id": "344074", "author": { "name": "pinnamuri", "key": "pinnamuri", "displayName": "Praveen Innamuri", "active": false, "timeZone": "America/Los_Angeles" }, "body": "When I tried to reproduce on my machine, the app launches successfully with liveview on Android emulator (with 5.0.1). The issue seems to happen only on Android AVD with v4.4", "updateAuthor": { "name": "pinnamuri", "key": "pinnamuri", "displayName": "Praveen Innamuri", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2015-02-21T00:17:57.000+0000", "updated": "2015-02-21T00:17:57.000+0000" }, { "id": "344222", "author": { "name": "pinnamuri", "key": "pinnamuri", "displayName": "Praveen Innamuri", "active": false, "timeZone": "America/Los_Angeles" }, "body": "I am unable to reproduce the app/simulator crash when I attempt to run app with liveview enabled on Android 5.x and 4.4 emulator.", "updateAuthor": { "name": "pinnamuri", "key": "pinnamuri", "displayName": "Praveen Innamuri", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2015-02-24T18:23:50.000+0000", "updated": "2015-02-24T18:23:50.000+0000" }, { "id": "344261", "author": { "name": "pinnamuri", "key": "pinnamuri", "displayName": "Praveen Innamuri", "active": false, "timeZone": "America/Los_Angeles" }, "body": "This turns out to be happening randomly even on the previous Titanium stable release with Node 0.10.x.", "updateAuthor": { "name": "pinnamuri", "key": "pinnamuri", "displayName": "Praveen Innamuri", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2015-02-24T23:46:44.000+0000", "updated": "2015-02-24T23:46:44.000+0000" }, { "id": "355470", "author": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "body": "What's the latest thoughts on this?", "updateAuthor": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2015-06-18T15:46:50.000+0000", "updated": "2015-06-18T15:46:50.000+0000" }, { "id": "355478", "author": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "body": "We are going to defer this in favor of working on refactoring the debugger to work with the built-in JS Core.", "updateAuthor": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2015-06-18T16:43:17.000+0000", "updated": "2015-06-18T16:43:17.000+0000" }, { "id": "356869", "author": { "name": "fokkezb", "key": "fokke", "displayName": "Fokke Zandbergen", "active": true, "timeZone": "Europe/Amsterdam" }, "body": "This is not just Android. I can reproduce this with:\r\n\r\n* Mac OS X 10.10.4\r\n* NodeJS v0.12.0, v0.12.6\r\n* iOS Simulator 8.4, XCode 6.4\r\n* SDK 4.1.0.v20150701131146\r\n\r\nIt works when I switch back to NodeJS v0.10.39 so it seems like its related to NodeJS?", "updateAuthor": { "name": "fokkezb", "key": "fokke", "displayName": "Fokke Zandbergen", "active": true, "timeZone": "Europe/Amsterdam" }, "created": "2015-07-03T06:52:54.000+0000", "updated": "2015-07-03T06:52:54.000+0000" }, { "id": "378186", "author": { "name": "mkellogg91@gmail.com", "key": "mkellogg91@gmail.com", "displayName": "Michael Kellogg", "active": true, "timeZone": "America/New_York" }, "body": "Hello Everyone!\r\n\r\nThis issue is still open? I was looking online for a solution to this issue and found an interesting consistency. It seems that on all of my Android 6.0 SDK emulators the liveview functionality doesn't work, BUT when I tried liveview with android 5.0.1 sdk emulators it worked. Please let me know if you guys can replicate this behavior.\r\n\r\nHere is some sytem info from my end:\r\nHost OS: Mac OS X\r\nOS Version: 10.10.5\r\nOS Arch: x86_64\r\nJRE Version: 1.8.0_72\r\nAppcelerator Studio Version: 4.5.0.201602170821\r\nXCode Version: 7.2.1\r\nAndroid SDK: I have both 6.0 and 5.0.1\r\nNode.JS Version: v4.3.1\r\n[LiveView] version 1.0.9\r\n\r\nalso not sure if this matters, but I made some minor changes as specified in this link and wanted to make sure you could keep that in mind: \r\nhttp://www.jasonified.com/post/62705976173/fix-for-appcelerator-platform-liveview-connection\r\n", "updateAuthor": { "name": "mkellogg91@gmail.com", "key": "mkellogg91@gmail.com", "displayName": "Michael Kellogg", "active": true, "timeZone": "America/New_York" }, "created": "2016-02-29T20:12:36.000+0000", "updated": "2016-02-29T20:33:29.000+0000" }, { "id": "378418", "author": { "name": "cng", "key": "cng", "displayName": "Chee Kiat Ng", "active": false, "timeZone": "America/Los_Angeles" }, "body": "[~mkellogg91@gmail.com] Thanks for the feedback. That's an interesting find, I'll get someone to take a look at it. We haven't addressed, or actually updated this ticket because we haven't been seeing this issue in the latest versions. ", "updateAuthor": { "name": "cng", "key": "cng", "displayName": "Chee Kiat Ng", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2016-03-02T03:56:32.000+0000", "updated": "2016-03-02T03:56:32.000+0000" }, { "id": "378420", "author": { "name": "msamah", "key": "msamah", "displayName": "Ashraf Abu", "active": false, "timeZone": "Asia/Singapore" }, "body": "Tried this with Android 6.0 on a Nexus 6 with 5.2.0.GA with an Alloy application. Using Mac OS X. No issues for me.\r\n(If it matters, my node is v0.10.37)", "updateAuthor": { "name": "msamah", "key": "msamah", "displayName": "Ashraf Abu", "active": false, "timeZone": "Asia/Singapore" }, "created": "2016-03-02T04:11:05.000+0000", "updated": "2016-03-02T04:21:48.000+0000" }, { "id": "378424", "author": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "body": "I didn't think we still officially supported Node 0.10.73. I thought we mandated 0.12.X and above?", "updateAuthor": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2016-03-02T04:35:23.000+0000", "updated": "2016-03-02T04:35:23.000+0000" }, { "id": "378425", "author": { "name": "msamah", "key": "msamah", "displayName": "Ashraf Abu", "active": false, "timeZone": "Asia/Singapore" }, "body": "Will get my Node updated and check to see if this occurs.", "updateAuthor": { "name": "msamah", "key": "msamah", "displayName": "Ashraf Abu", "active": false, "timeZone": "Asia/Singapore" }, "created": "2016-03-02T04:40:23.000+0000", "updated": "2016-03-02T04:40:23.000+0000" }, { "id": "378435", "author": { "name": "msamah", "key": "msamah", "displayName": "Ashraf Abu", "active": false, "timeZone": "Asia/Singapore" }, "body": "Updated node.\r\nTried this with:-\r\nNode.js\r\n Node.js Version = 0.12.10\r\n npm Version = 2.14.9\r\nTitanium CLI\r\n CLI Version = 5.0.6\r\nTitanium SDK\r\n SDK Version = 5.2.0.GA\r\n\r\nNo issues. Works correctly.", "updateAuthor": { "name": "msamah", "key": "msamah", "displayName": "Ashraf Abu", "active": false, "timeZone": "Asia/Singapore" }, "created": "2016-03-02T05:21:28.000+0000", "updated": "2016-03-02T05:21:28.000+0000" }, { "id": "378471", "author": { "name": "mkellogg91@gmail.com", "key": "mkellogg91@gmail.com", "displayName": "Michael Kellogg", "active": true, "timeZone": "America/New_York" }, "body": "I was using one of the Nodejs LTS installations hence the nodejs version: 4.3.1 I'm not sure if this would change my experience, but my suspicion is that it would. I've since gone out and installed nodejs 0.12.10 since I saw that others were using that instead. Also, since writing my previous post I am using Genymotion for Android emulators and they only support up to android build 22 (sdk 6.0 is build 23 and build 23 was what I was previously having trouble with). At any rate I have my liveview working now.", "updateAuthor": { "name": "mkellogg91@gmail.com", "key": "mkellogg91@gmail.com", "displayName": "Michael Kellogg", "active": true, "timeZone": "America/New_York" }, "created": "2016-03-02T14:27:00.000+0000", "updated": "2016-03-02T14:29:29.000+0000" }, { "id": "453420", "author": { "name": "icecandyent", "key": "icecandyent", "displayName": "Simon Buckingham", "active": true, "timeZone": "Europe/London" }, "body": "This is still a problem. There is more than 1 ticket for this problem so not sure which one is the most up to date. It mainly happens when switching between using LiveView on the iOS simulator and then trying Android in Genymotion (or vice-versa as iOS can stop working too). Try Android using Genymotion and get:\r\n[ERROR] TiExceptionHandler: Error: [LiveView] File Server unavailable. Host Unreachable @ 192.168.0.12:8324\r\n[ERROR] TiExceptionHandler: [LiveView] Please ensure your device and computer are on the same network and the port is not blocked.\r\nI have tried:\r\n- resetting and closing the iOS simulator (which sometimes seems to work, but can't see any pattern)\r\n- $ killall node\r\n- Restarting Genymotion\r\n- Running the Android project for the first time without the --liveview flag\r\n- Quitting the terminal\r\n\r\nPS Using Ti SDK 8.3.0\r\nPPS If I start afresh in the morning after a computer startup it seems to work on the first platform that I test on eg Android or iOS. So there is obviously something that has to be reset for this to work. \r\n\r\nIs this a node problem? I have node version 8.16.2", "updateAuthor": { "name": "icecandyent", "key": "icecandyent", "displayName": "Simon Buckingham", "active": true, "timeZone": "Europe/London" }, "created": "2020-01-02T14:31:56.000+0000", "updated": "2020-01-02T14:36:17.000+0000" } ], "maxResults": 16, "total": 16, "startAt": 0 } } }