{ "id": "171568", "key": "DAEMON-255", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "12519", "key": "DAEMON", "name": "Appcelerator Daemon" }, "fixVersions": [], "resolution": { "id": "10000", "description": "", "name": "Done" }, "resolutiondate": "2018-10-25T13:20:51.000+0000", "created": "2018-04-25T14:42:54.000+0000", "priority": { "name": "High", "id": "2" }, "labels": [], "versions": [], "issuelinks": [], "assignee": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "updated": "2018-10-25T13:20:51.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": "15051", "name": "androidlib", "description": "Library for Android related functions" }, { "id": "15049", "name": "appcd", "description": "Bootstrap, appcd CLI commands (start, stop, restart, exec, logcat, config, status)" } ], "description": "Hello,\r\n\r\nWe have an Enterprise customer who is facing an issue with Appcelerator Studio. Appcelerator Studio not detecting android emulator and emulator doesn't come up on windows 7. We have attached the screenshot, Studio Diagnostic log and *appc ti setup check* log file. \r\n\r\nIf any others information needed please let us know.\r\n\r\nThanks", "attachment": [ { "id": "65086", "filename": "appc_ti_info_t_android.txt", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-04-25T14:55:49.000+0000", "size": 8501, "mimeType": "text/plain" }, { "id": "65085", "filename": "appc_ti_setup_check.txt", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-04-25T14:41:59.000+0000", "size": 4682, "mimeType": "text/plain" }, { "id": "65179", "filename": "appcd_android_info.txt", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-05-17T13:26:08.000+0000", "size": 40759, "mimeType": "text/plain" }, { "id": "65089", "filename": "appcd_log.txt", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-04-27T13:11:14.000+0000", "size": 766, "mimeType": "text/plain" }, { "id": "65088", "filename": "Appc Daemon Dump.txt", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-04-27T13:11:16.000+0000", "size": 464670, "mimeType": "text/plain" }, { "id": "65263", "filename": "complete-Build-log.txt", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-06-15T12:36:27.000+0000", "size": 34178, "mimeType": "text/plain" }, { "id": "65084", "filename": "DiagnosticTest.txt", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-04-25T14:42:01.000+0000", "size": 15302, "mimeType": "text/plain" }, { "id": "65180", "filename": "image001.jpg", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-05-17T13:26:07.000+0000", "size": 16645, "mimeType": "image/jpeg" }, { "id": "65181", "filename": "image002.jpg", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-05-17T13:26:07.000+0000", "size": 17333, "mimeType": "image/jpeg" }, { "id": "65189", "filename": "Img-01-22-05-18.jpg", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-05-22T16:22:45.000+0000", "size": 54151, "mimeType": "image/jpeg" }, { "id": "65190", "filename": "Img-02-22-05-2018.jpg", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-05-22T16:22:46.000+0000", "size": 55512, "mimeType": "image/jpeg" }, { "id": "65138", "filename": "Out_Comes.jpg", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-05-09T16:36:54.000+0000", "size": 49332, "mimeType": "image/jpeg" }, { "id": "65083", "filename": "Screenshot.jpg", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-04-25T14:42:32.000+0000", "size": 131122, "mimeType": "image/jpeg" }, { "id": "65109", "filename": "Server_not_running.jpg", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-05-02T15:16:12.000+0000", "size": 14180, "mimeType": "image/jpeg" }, { "id": "65137", "filename": "Stuck.jpg", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-05-09T13:53:55.000+0000", "size": 126151, "mimeType": "image/jpeg" } ], "flagged": false, "summary": "Appcelerator Studio not detecting android emulator and emulator doesn't come up on windows 7", "creator": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "subtasks": [], "reporter": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "environment": "Appcelerator Studio, Android Emulator, Android SDK", "closedSprints": [ { "id": 1046, "state": "closed", "name": "2018 Sprint 13 Tooling", "startDate": "2018-06-17T20:46:34.882Z", "endDate": "2018-07-01T20:46:00.000Z", "completeDate": "2018-07-02T18:42:28.216Z", "originBoardId": 219 }, { "id": 1049, "state": "closed", "name": "2018 Sprint 14 Tooling", "startDate": "2018-07-01T18:43:06.111Z", "endDate": "2018-07-15T18:43:00.000Z", "completeDate": "2018-07-16T03:28:17.452Z", "originBoardId": 219 }, { "id": 1036, "state": "closed", "name": "2018 Sprint 10 Tooling", "startDate": "2018-05-07T00:06:53.730Z", "endDate": "2018-05-21T00:06:00.000Z", "completeDate": "2018-05-20T21:01:23.546Z", "originBoardId": 219 }, { "id": 1037, "state": "closed", "name": "2018 Sprint 11 Tooling", "startDate": "2018-05-20T21:01:41.131Z", "endDate": "2018-06-03T21:01:00.000Z", "completeDate": "2018-06-04T15:14:21.945Z", "originBoardId": 219 }, { "id": 1040, "state": "closed", "name": "2018 Sprint 12 Tooling", "startDate": "2018-06-04T15:22:00.964Z", "endDate": "2018-06-18T15:22:00.000Z", "completeDate": "2018-06-18T20:46:08.498Z", "originBoardId": 219 } ], "comment": { "comments": [ { "id": "437177", "author": { "name": "kkolipaka", "key": "kkolipaka", "displayName": "Kondal Kolipaka", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Looking at the Screenshot.jpg - {{C:\\android-sdk-win}} is not recognised as a valid android SDK path. Investing further on this\r\n\r\nCan you also provide the \"Appc Daemon Dump\" for studio\r\n\r\nIn Studio, go to Help > Studio > Generate Appc Daemon Dump. \r\nIt generates the appc daemon dump and provide you the location for the generated file.\r\n", "updateAuthor": { "name": "kkolipaka", "key": "kkolipaka", "displayName": "Kondal Kolipaka", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2018-04-27T04:21:00.000+0000", "updated": "2018-04-27T04:23:03.000+0000" }, { "id": "437178", "author": { "name": "kkolipaka", "key": "kkolipaka", "displayName": "Kondal Kolipaka", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Looks like Appc daemon is unable to find the android emulators. To confirm on this, can you run the following command and attach {{ appcd.log}} to the ticket.\r\n\r\n{code:java}\r\n$ appc appcd exec /system-info/1.x/info > appcd.log\r\n{code}\r\n", "updateAuthor": { "name": "kkolipaka", "key": "kkolipaka", "displayName": "Kondal Kolipaka", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2018-04-27T04:46:25.000+0000", "updated": "2018-04-27T04:46:25.000+0000" }, { "id": "437179", "author": { "name": "kkolipaka", "key": "kkolipaka", "displayName": "Kondal Kolipaka", "active": false, "timeZone": "America/Los_Angeles" }, "body": "[~eharris] [~cbarber] I think we were having a similar issue earlier, do you guys recall the ticket for this", "updateAuthor": { "name": "kkolipaka", "key": "kkolipaka", "displayName": "Kondal Kolipaka", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2018-04-27T04:47:47.000+0000", "updated": "2018-04-27T04:47:47.000+0000" }, { "id": "437185", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "body": "I have attached the required logs named: Appc Daemon Dump.txt and appcd_log.txt. Thanks", "updateAuthor": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-04-27T13:12:33.000+0000", "updated": "2018-04-27T13:12:33.000+0000" }, { "id": "437369", "author": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "body": "[~mrahman] Apologies they will have to start the daemon first, so the steps are the following\r\n\r\n1. {{appc appcd start}}, should log {{Appc Daemon started}}\r\n2. {{appc appcd exec /system-info/1.x/info}}, check it looks ok\r\n3. {{appc appcd exec /system-info/1.x/info > appcd.log}}\r\n\r\nThen upload that appcd.log file", "updateAuthor": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "created": "2018-05-04T13:27:44.000+0000", "updated": "2018-05-04T13:27:44.000+0000" }, { "id": "437484", "author": { "name": "kkolipaka", "key": "kkolipaka", "displayName": "Kondal Kolipaka", "active": false, "timeZone": "America/Los_Angeles" }, "body": "[~eharris] Do you see any issue from the appc daemon dump [^Appc Daemon Dump.txt] ", "updateAuthor": { "name": "kkolipaka", "key": "kkolipaka", "displayName": "Kondal Kolipaka", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2018-05-09T06:22:21.000+0000", "updated": "2018-05-09T06:22:21.000+0000" }, { "id": "437486", "author": { "name": "kkolipaka", "key": "kkolipaka", "displayName": "Kondal Kolipaka", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Maybe we can debug the below command and see where it's hanging. \r\n\r\n{code:java}\r\nset DEBUG=* && appc appcd exec /system-info/1.x/info\r\n{code}\r\n", "updateAuthor": { "name": "kkolipaka", "key": "kkolipaka", "displayName": "Kondal Kolipaka", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2018-05-09T06:28:42.000+0000", "updated": "2018-05-09T06:28:42.000+0000" }, { "id": "437601", "author": { "name": "kkolipaka", "key": "kkolipaka", "displayName": "Kondal Kolipaka", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Doesn't seem to be the studio issue, hence I'll move the component to DAEMON project to get the high priority", "updateAuthor": { "name": "kkolipaka", "key": "kkolipaka", "displayName": "Kondal Kolipaka", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2018-05-14T05:19:12.000+0000", "updated": "2018-05-14T05:19:12.000+0000" }, { "id": "437693", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "I'm not convinced this is a daemon issue. It's obvious that \"ti info\" cannot see the emulators, but that's not the same source that Studio pulls from to get the list of emulators.\r\n\r\nThere is no {{appc appcd exec /system-info/1.x/info}} output attached to this ticket. It would be better to attach the output of just the Android info by running either {{appc appcd exec /system-info/1.x/info/android}} or {{appc appcd exec /android/1.x/info}}. This output would tell us if the daemon can detect the emulators, however if it doesn't detect the emulators it won't tell us _why_ it couldn't detect the emulators.\r\n\r\nTo get the why, we need an {{appc appcd dump output.json}} immediately after running {{appc appcd exec /android/1.x/info}}.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2018-05-16T15:20:52.000+0000", "updated": "2018-05-16T15:22:57.000+0000" }, { "id": "437729", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "body": "[~cbarber], Command: appc appcd exec /android/1.x/info they are able to get the output, attached the same for reference (appcd_android_info.txt). \r\nBut the Below 2 commands\r\nappc appcd exec /system-info/1.x/info\r\nappc appcd exec /system-info/1.x/info/android is running for more than 4 hrs.\r\n\r\nThere was no o/p as mentioned in attached screenshot (image001, image002).\r\n", "updateAuthor": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-05-17T13:26:34.000+0000", "updated": "2018-05-17T13:26:34.000+0000" }, { "id": "437735", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "[~mrahman] They probably just need to restart the daemon: {{appc appcd restart}}. They also should upgrade to the latest Appcelerator CLI so that it pulls down the latest appcd version.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2018-05-17T15:30:20.000+0000", "updated": "2018-05-17T15:30:20.000+0000" }, { "id": "437847", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "body": "Hello [~cbarber], They have restarted the daemon by using *appc appcd restart*. Then upgraded the latest Appcelerator CLI but still facing the same issue. Appcelerator Studio not detecting android emulator and emulator doesn't come up on windows 7. They have emulators available in Appcelerator, but they still have the error persists as “Problem detected with the SDK settings”.\r\nDue to which emulator is not selected by default. Provided the screenshot for your reference.\r\nIn another screenshot, they tried to build the project in cmd prompt but getting an error as “Unable to find any emulators”. Img-02-22-05-2018.jpg and Img-01-22-05-2018.jpg reference as screenshot.\r\n", "updateAuthor": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-05-22T16:24:54.000+0000", "updated": "2018-05-22T16:24:54.000+0000" }, { "id": "437859", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "[~mrahman] I noticed is the AVD directory is {{C:\\android-sdk-win\\.android\\avd}}. This is a non-standard location. Usually it is in the user's home directory.\r\n\r\nTitanium SDK *does not *support a non-standard AVD location. It must be in {{C:\\Users\\\\.android\\avd}}.\r\n\r\nAppc Daemon _does_ support non-standard AVD locations, but it must be manually set by running {{appc appcd config android.avd.path C:\\android-sdk-win\\.android\\avd}}. If you do this, then run {{appc appcd exec /appcd/plugin/stop/android}} and Studio should start displaying the list of emulators. However, if you move the AVDs to the user's home directory to make Titanium SDK happy as indicated above, then do not set the {{android.avd.path}}.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2018-05-22T22:27:17.000+0000", "updated": "2018-05-22T22:27:17.000+0000" }, { "id": "437912", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "body": "We have shared this with the customer and waiting for his update. Thanks", "updateAuthor": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-05-24T13:19:26.000+0000", "updated": "2018-05-24T13:19:26.000+0000" }, { "id": "438427", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "body": "[~cbarber], We have an update from the customer. The customer replied: Sorry for the delayed response, I was on a business trip and could not get back. Here is the last error response from the compiler:\r\n\r\n\r\n{code}alloy compile --platform android\r\n\r\nC:\\Users\\A78986\\AppData\\Roaming\\npm\\node_modules\\alloy\\Alloy\\commands\\compile\\sourceMapper.js:97\r\nthrow e;\r\n^\r\n\r\nSyntaxError: Unexpected character '?' (68:0)\r\nat Parser.pp$5.raise (C:\\Users\\A78986\\AppData\\Roaming\\npm\\node_modules\\alloy\\node_modules\\babylon\\lib\\index.js:4454:13)\r\nat Parser.getTokenFromCode (C:\\Users\\A78986\\AppData\\Roaming\\npm\\node_modules\\alloy\\node_modules\\babylon\\lib\\index.js:1147:10)\r\nat Parser.readToken (C:\\Users\\A78986\\AppData\\Roaming\\npm\\node_modules\\alloy\\node_modules\\babylon\\lib\\index.js:776:19)\r\nat Parser.nextToken (C:\\Users\\A78986\\AppData\\Roaming\\npm\\node_modules\\alloy\\node_modules\\babylon\\lib\\index.js:766:19)\r\nat Parser.next (C:\\Users\\A78986\\AppData\\Roaming\\npm\\node_modules\\alloy\\node_modules\\babylon\\lib\\index.js:691:10)\r\nat Parser.eat (C:\\Users\\A78986\\AppData\\Roaming\\npm\\node_modules\\alloy\\node_modules\\babylon\\lib\\index.js:698:12)\r\nat Parser.pp$1.parseBlockBody (C:\\Users\\A78986\\AppData\\Roaming\\npm\\node_m{code}\r\n\r\nThanks\r\n ", "updateAuthor": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-06-14T19:59:13.000+0000", "updated": "2018-06-14T19:59:13.000+0000" }, { "id": "438434", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "That looks to be an Alloy error, not a Daemon related error.\r\n\r\n[~mrahman] Can we get a reproducible test case from the customer?\r\n\r\n[~fmiao] What do you make of the \"Unexpected character\" error above?", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2018-06-14T22:44:44.000+0000", "updated": "2018-06-14T22:44:44.000+0000" }, { "id": "438435", "author": { "name": "fmiao", "key": "fmiao", "displayName": "Feon Sua Xin Miao", "active": true, "timeZone": "America/Vancouver" }, "body": "Why is it loading alloy from {{\\AppData\\Roaming\\npm\\node_modules\\}}?\r\nWhat's the alloy version?\r\nCan we have the complete build log?\r\n", "updateAuthor": { "name": "fmiao", "key": "fmiao", "displayName": "Feon Sua Xin Miao", "active": true, "timeZone": "America/Vancouver" }, "created": "2018-06-14T23:15:48.000+0000", "updated": "2018-06-14T23:15:48.000+0000" }, { "id": "438437", "author": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "body": "[~fmiao], Here is the answers from the customer regarding your questions:\r\n1) It is the same way it loads initially before this issue happened.\r\n2) 1.11.0\r\n3) Attaching the log named complete-Build-log.txt", "updateAuthor": { "name": "mrahman", "key": "mrahman", "displayName": "Mostafizur Rahman", "active": true, "timeZone": "Asia/Dhaka" }, "created": "2018-06-15T12:36:33.000+0000", "updated": "2018-06-15T12:36:33.000+0000" }, { "id": "438488", "author": { "name": "fmiao", "key": "fmiao", "displayName": "Feon Sua Xin Miao", "active": true, "timeZone": "America/Vancouver" }, "body": "[~mrahman], I could reproduce a similar error when I misplaced a `?` in {{alloy.js}}. If you run appc with debug enable, you should get more information on exactly which line causes the issue.\r\n\r\n{code}\r\n[INFO] [app.js] Titanium entry point processing...\r\n[DEBUG] var Alloy = require('/alloy'),\r\n[DEBUG] _ = Alloy._,\r\n[DEBUG] Backbone = Alloy.Backbone;\r\n[DEBUG] console.log('a')?;\r\n[DEBUG] Alloy.createController('index');\r\n[DEBUG] .../.appcelerator/install/7.0.2/package/node_modules/alloy/Alloy/commands/compile/sourceMapper.js:97\r\n[DEBUG] \tthrow e;\r\n[DEBUG] \t^\r\n[DEBUG] SyntaxError: Unexpected token (11:15)\r\n[DEBUG] at Parser.pp$5.raise (.../.appcelerator/install/7.0.2/package/node_modules/alloy/node_modules/babylon/lib/index.js:4454:13)\r\n[DEBUG] at Parser.pp.unexpected (.../.appcelerator/install/7.0.2/package/node_modules/alloy/node_modules/babylon/lib/index.js:1761:8)\r\n{code}", "updateAuthor": { "name": "fmiao", "key": "fmiao", "displayName": "Feon Sua Xin Miao", "active": true, "timeZone": "America/Vancouver" }, "created": "2018-06-18T20:06:48.000+0000", "updated": "2018-06-18T20:07:02.000+0000" }, { "id": "442935", "author": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "body": "Closing based off feedback", "updateAuthor": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "created": "2018-10-25T13:20:51.000+0000", "updated": "2018-10-25T13:20:51.000+0000" } ], "maxResults": 32, "total": 32, "startAt": 0 } } }