{ "id": "171161", "key": "TIMOB-25872", "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": { "id": "10000", "description": "", "name": "Done" }, "resolutiondate": "2018-08-01T16:16:22.000+0000", "created": "2018-02-22T15:49:05.000+0000", "priority": { "name": "Critical", "id": "1" }, "labels": [ "cb-tooling", "ios" ], "versions": [ { "id": "19957", "description": "", "name": "Release 7.1.0", "archived": false, "released": true, "releaseDate": "2018-03-14" }, { "id": "20060", "description": "", "name": "Release 7.0.2", "archived": false, "released": true, "releaseDate": "2018-02-09" } ], "issuelinks": [], "assignee": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "updated": "2018-08-01T22:17:55.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": "10206", "name": "iOS", "description": "iOS Platform" } ], "description": "*Description*\r\n\r\nWhen building an iOS app and there is an issue connecting to the iOS log-server, it always output \"Another process is currently bound to port xxxxx\" even if there is another server connection issue such as the port not existing.\r\n\r\n*Workaround*\r\n\r\nFigure out the real issue by logging the actual error within the sdk itself (at ~/Library/Application Support/Titanium/mobilesdk/osx/7.0.2.GA/iphone/cli/commands/_build.js in the determineLogServerPort function).\r\n\r\n*Steps to Reproduce*\r\n\r\n1. Create a different type of error with the server. For example, my /etc/hosts file did not have an entry for 127.0.0.1 localhost, so the actual node error was 'ENOTFOUND'.\r\n2. Create a new titanium app with `appc ti new`.\r\n3. Build with appc ti build -p ios\r\n\r\n*Actual Result*\r\n\r\nBuild errors out with following text:\r\n{code}\r\n [ERROR] Another process is currently bound to port 27973\r\n [ERROR] Set a unique between 1024 and 65535 in the section of the tiapp.xml\r\n{code}\r\n\r\n*Expected Result*\r\n\r\nMore detailed error. I.E. Something like:\r\n\r\n{code}Failed to create/connect to log server port with error \"[error given by node net package]\".{code}\r\nFollowed by suggested solution. For example if the node error was EADDRINUSE, then you could still use the existing error message. But if it's another error, log accordingly so the user has the best information for solving the issue.", "attachment": [], "flagged": false, "summary": "iOS: Log-server-port Build Error Masks Real Error", "creator": { "name": "emilyafeder@gmail.com", "key": "emilyafeder@gmail.com", "displayName": "Emily Feder", "active": true, "timeZone": "America/Chicago" }, "subtasks": [], "reporter": { "name": "emilyafeder@gmail.com", "key": "emilyafeder@gmail.com", "displayName": "Emily Feder", "active": true, "timeZone": "America/Chicago" }, "environment": "Titanium SDK: 7.0.2.GA\r\nJavascript Engine: V8 \r\nPlatform & version: iOS 11.2\r\nDevice Details: iOS simulator (iPhone 7+)\r\nHost Operating System: OS X 10.13 64 bit\r\nNode Version: 7.10.0\r\nTitanium CLI: 5.0.14\r\nNpm Version: 4.2.0", "closedSprints": [ { "id": 1058, "state": "closed", "name": "2018 Sprint 16 SDK", "startDate": "2018-07-29T22:26:06.486Z", "endDate": "2018-08-12T22:26:00.000Z", "completeDate": "2018-08-13T17:38:16.757Z", "originBoardId": 114 }, { "id": 1045, "state": "closed", "name": "2018 Sprint 13 SDK", "startDate": "2018-06-17T20:47:13.621Z", "endDate": "2018-07-01T20:47:00.000Z", "completeDate": "2018-07-02T18:40:05.029Z", "originBoardId": 114 }, { "id": 1050, "state": "closed", "name": "2018 Sprint 14 SDK", "startDate": "2018-07-01T18:40:57.193Z", "endDate": "2018-07-15T18:40:00.000Z", "completeDate": "2018-07-16T03:27:08.720Z", "originBoardId": 114 }, { "id": 1035, "state": "closed", "name": "2018 Sprint 11 SDK", "startDate": "2018-05-20T20:57:43.542Z", "endDate": "2018-06-03T20:57:00.000Z", "completeDate": "2018-06-04T15:13:14.425Z", "originBoardId": 114 }, { "id": 1053, "state": "closed", "name": "2018 Sprint 15 SDK", "startDate": "2018-07-15T21:52:05.453Z", "endDate": "2018-07-29T21:52:00.000Z", "completeDate": "2018-07-29T22:25:11.723Z", "originBoardId": 114 }, { "id": 1039, "state": "closed", "name": "2018 Sprint 12 SDK", "startDate": "2018-06-03T15:22:23.401Z", "endDate": "2018-06-17T15:22:00.000Z", "completeDate": "2018-06-18T20:45:36.363Z", "originBoardId": 114 } ], "comment": { "comments": [ { "id": "434871", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "body": "Hello [~emilyafeder@gmail.com], Thanks for sharing with us. Please provide a full sample test code that regenerates the issue. Better to provide a sample app as an attachment here. We will test the issue in our environment.\r\nThanks", "updateAuthor": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-02-25T06:50:26.000+0000", "updated": "2018-02-25T06:50:26.000+0000" }, { "id": "435376", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "body": "Hello [~emilyafeder@gmail.com],
Just passing a followup here.Are you able to get that sorted out? Please let us know if you need more help with this issue.\r\nRegards
\r\nAxway Appcelerator Support", "updateAuthor": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-03-08T05:19:15.000+0000", "updated": "2018-03-08T05:19:15.000+0000" }, { "id": "435463", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "The \"Another process is currently bound to port...\" error indicates that a Titanium app is currently running in an iOS Simulator. There are a couple ways in which a user can encounter this issue.\r\n\r\nThe most common culprit is due to the iOS Simulator that ships with Xcode 9 which allows multiple simulators to run at the same time, so it's possible to build your Titanium app and run it in one simulator, then build it again and run it in a different simulator and that's when you run into the port conflict. You can simply close the other simulator or kill the app by double pressing the home button and swiping the app away.\r\n\r\nIf you have 2 separate apps and run into this issue, then it's possible because the app id's are not unique or they just happen to hash to the same port number. Titanium will pick a port number based on the app id. This allows the Titanium app to be killed in the simulator and relaunched and the CLI should reconnect and display log messages.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2018-03-12T05:26:30.000+0000", "updated": "2018-03-12T05:26:30.000+0000" }, { "id": "435609", "author": { "name": "sdarda", "key": "sdarda", "displayName": "Sharif AbuDarda", "active": false, "timeZone": "Asia/Dhaka" }, "body": "Hello [~emilyafeder@gmail.com], Can you get back to us on Chris's comment? ", "updateAuthor": { "name": "sdarda", "key": "sdarda", "displayName": "Sharif AbuDarda", "active": false, "timeZone": "Asia/Dhaka" }, "created": "2018-03-14T20:53:33.000+0000", "updated": "2018-03-14T20:53:33.000+0000" }, { "id": "435614", "author": { "name": "emilyafeder@gmail.com", "key": "emilyafeder@gmail.com", "displayName": "Emily Feder", "active": true, "timeZone": "America/Chicago" }, "body": "Regarding the test app -- I'm still working on that.\r\n\r\nRegarding Chris Barber's comment, I do get that that is what the error is supposed to indicate. My point is that I got that error even though that wasn't the issue. I did not have multiple simulator/apps running at the same time and spent a lot of time fishing for the process that was using that port (even though there wasn't one). I had to dig into the sdk code and log out the actual error, which turned out to be that it did not recognize localhost as a legitimate host, because it had accidentally been removed from my `/etc/hosts` file. \r\n\r\nThe ticket request is to have the error at least log out the error generated by `net.createServer()`. Currently it just assumes that there's an error because you have another process such as another simulator using that port already.", "updateAuthor": { "name": "emilyafeder@gmail.com", "key": "emilyafeder@gmail.com", "displayName": "Emily Feder", "active": true, "timeZone": "America/Chicago" }, "created": "2018-03-14T21:42:58.000+0000", "updated": "2018-03-14T21:44:08.000+0000" }, { "id": "435641", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "[~emilyafeder@gmail.com] Ah, that makes sense. Thought that \"localhost\" may not be correct never crossed my mind. I'd be happy to fix the verbiage.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2018-03-15T14:24:17.000+0000", "updated": "2018-03-15T14:24:17.000+0000" }, { "id": "435645", "author": { "name": "emilyafeder@gmail.com", "key": "emilyafeder@gmail.com", "displayName": "Emily Feder", "active": true, "timeZone": "America/Chicago" }, "body": "Thanks!", "updateAuthor": { "name": "emilyafeder@gmail.com", "key": "emilyafeder@gmail.com", "displayName": "Emily Feder", "active": true, "timeZone": "America/Chicago" }, "created": "2018-03-15T16:16:47.000+0000", "updated": "2018-03-15T16:16:47.000+0000" } ], "maxResults": 12, "total": 12, "startAt": 0 } } }