{ "id": "162661", "key": "TIMOB-23786", "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": [ { "id": "16980", "description": "New V8", "name": "Release 6.0.0", "archived": false, "released": true, "releaseDate": "2016-11-15" }, { "id": "18372", "name": "node-ios-device 1.0.0", "archived": false, "released": true, "releaseDate": "2016-10-10" }, { "id": "18373", "name": "ioslib 1.0.0", "archived": false, "released": true, "releaseDate": "2016-10-10" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2016-10-17T17:45:32.000+0000", "created": "2016-08-17T16:45:55.000+0000", "priority": { "name": "Critical", "id": "1" }, "labels": [ "notable", "qe-5.5.0", "qe-6.0.0" ], "versions": [ { "id": "18253", "name": "Release 5.5.0", "archived": false, "released": true, "releaseDate": "2016-09-13" } ], "issuelinks": [ { "id": "52461", "type": { "id": "10000", "name": "Blocks", "inward": "is blocked by", "outward": "blocks" }, "outwardIssue": { "id": "161074", "key": "TIMOB-23519", "fields": { "summary": "iOS10: Expose new Ti.UI.Pasteboard APIs", "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" } }, "priority": { "name": "High", "id": "2" }, "issuetype": { "id": "2", "description": "A new feature of the product, which has yet to be developed.", "name": "New Feature", "subtask": false } } } }, { "id": "53049", "type": { "id": "10020", "name": "Depends", "inward": "is dependent of", "outward": "depends on" }, "inwardIssue": { "id": "163849", "key": "TIMOB-24008", "fields": { "summary": "iOS: Can't use Xcode managed provisioning profiles to build app?", "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" } }, "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": "53007", "type": { "id": "10002", "name": "Duplicate", "inward": "is duplicated by", "outward": "duplicates" }, "outwardIssue": { "id": "163809", "key": "AC-4537", "fields": { "summary": "IOS 10 LOG", "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" } }, "issuetype": { "id": "7", "description": "gh.issue.story.desc", "name": "Story", "subtask": false } } } }, { "id": "53096", "type": { "id": "10003", "name": "Relates", "inward": "relates to", "outward": "relates to" }, "inwardIssue": { "id": "163960", "key": "TIMOB-24034", "fields": { "summary": "iOS: New logging system breaks differential builds - simulator builds only", "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" } }, "priority": { "name": "Critical", "id": "1" }, "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false } } } } ], "assignee": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "updated": "2017-01-05T15:04:02.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" }, { "id": "10207", "name": "Tooling" } ], "description": "h4. Steps to reproduce:\r\n# Use the environment above.\r\n# Create a new project {{appc new}}\r\n# Use the app.js below.\r\n# Run the application and click the button on the screen \r\n\r\nh4. App.js\r\n{noformat}\r\nvar win = Ti.UI.createWindow({\r\n backgroundColor: 'white',\r\n exitOnClose: true,\r\n fullscreen: false,\r\n layout: 'vertical',\r\n title: 'ERROR'\r\n});\r\n \r\nvar button = Titanium.UI.createButton({\r\n title: 'Click',\r\n top: 50,\r\n width: 100,\r\n height: 50\r\n});\r\nbutton.addEventListener('click',function(e)\r\n{\r\n Ti.API.info(\"########### Info\");\r\n Ti.API.warn(\"########### Warn\");\r\n Ti.API.error(\"########### Error\");\r\n\r\n});\r\n \r\nwin.add(button);\r\nwin.open();\r\n{noformat}\r\n\r\nh4. Actual\r\nNo logs are shown after: \r\n{noformat}\r\n[TRACE] : ** BUILD SUCCEEDED **\r\n[INFO] : Finished building the application in 14s 652ms\r\n[INFO] : Installing app on device: Eggs\r\n[INFO] : App successfully installed on device: Eggs\r\nPlease manually launch the application\r\n[TRACE] : updating tiapp metadata with Appcelerator Platform...\r\n[TRACE] : Uploaded tiapp metadata with Appcelerator Platform!\r\n{noformat}\r\n\r\n\r\n\r\n\r\nh4. Expected\r\nThis is what the iPhone 6 iOS 10 simulator shows:\r\n\r\n{noformat}\r\n-- Start simulator log -------------------------------------------------------\r\n[WARN] : ########### Warn\r\n[INFO] : ########### Info\r\n[ERROR] : ########### Error\r\n[TRACE] : updating tiapp metadata with Appcelerator Platform...\r\n[TRACE] : Uploaded tiapp metadata with Appcelerator Platform!\r\n{noformat}\r\n\r\n", "attachment": [ { "id": "60483", "filename": "app.js", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-10-11T07:25:09.000+0000", "size": 1874, "mimeType": "application/x-javascript" } ], "flagged": false, "summary": "iOS10: Logs not working on iOS 10 devices.", "creator": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "subtasks": [], "reporter": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "environment": "iPhone 6 (10.0) beta 6\r\n
Mac OSX El Capitan 10.11.6\r\nStudio: 4.7.0.201607250649\r\nTi SDK: 5.4.0.v20160608165242\r\n
Appc NPM: 4.2.7\r\nAppc CLI: 5.4.0.GA\r\n
Xcode 8 beta 6\r\nNode v4.4.4", "closedSprints": [ { "id": 732, "state": "closed", "name": "2016 Sprint 21 Tooling", "startDate": "2016-10-08T00:54:00.000Z", "endDate": "2016-10-22T00:54:00.000Z", "completeDate": "2016-10-24T04:18:13.798Z", "originBoardId": 199 } ], "comment": { "comments": [ { "id": "393403", "author": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "body": "Logs will appear if I run the application using debug. ", "updateAuthor": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "created": "2016-08-17T16:58:37.000+0000", "updated": "2016-08-17T16:58:37.000+0000" }, { "id": "393411", "author": { "name": "hknoechel", "key": "hansknoechel", "displayName": "Hans Knöchel", "active": true, "timeZone": "Europe/Berlin" }, "body": "Could be an open Xcode 8 issue (see [here|https://forums.developer.apple.com/thread/49323]).\r\n{quote}\r\nWhen debugging an app running on Simulator, logs may not be visible in the console.\r\n \r\nWorkaround: Use command + / in Simulator.app to open the system log in the Console app to view NSLogs. (26457535)\r\n{quote}\r\n\r\n*EDIT*: Wait, so it does work in sim? Can you also check if you have the jscore flag enabled?", "updateAuthor": { "name": "hknoechel", "key": "hansknoechel", "displayName": "Hans Knöchel", "active": true, "timeZone": "Europe/Berlin" }, "created": "2016-08-17T19:36:18.000+0000", "updated": "2016-08-17T19:40:30.000+0000" }, { "id": "393431", "author": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "body": "Yes sim worked and I do not have the jscore flag. ", "updateAuthor": { "name": "jlongton", "key": "jlongton", "displayName": "Josh Longton", "active": true, "timeZone": "Europe/London" }, "created": "2016-08-17T22:43:40.000+0000", "updated": "2016-08-17T22:44:48.000+0000" }, { "id": "393678", "author": { "name": "hknoechel", "key": "hansknoechel", "displayName": "Hans Knöchel", "active": true, "timeZone": "Europe/Berlin" }, "body": "Might be a Xcode 8 issue: http://stackoverflow.com/questions/37886600/ios-10-doesnt-print-nslogs", "updateAuthor": { "name": "hknoechel", "key": "hansknoechel", "displayName": "Hans Knöchel", "active": true, "timeZone": "Europe/Berlin" }, "created": "2016-08-19T22:26:23.000+0000", "updated": "2016-08-19T22:26:23.000+0000" }, { "id": "395149", "author": { "name": "ewieber", "key": "ewieber", "displayName": "Eric Wieber", "active": false, "timeZone": "America/Los_Angeles" }, "body": "I can also reproduce this issue. However, in light of what Hans said, should this be resolved as \"not our bug\"?", "updateAuthor": { "name": "ewieber", "key": "ewieber", "displayName": "Eric Wieber", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2016-09-01T22:18:02.000+0000", "updated": "2016-09-01T22:18:02.000+0000" }, { "id": "395578", "author": { "name": "cng", "key": "cng", "displayName": "Chee Kiat Ng", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Tested with Xcode 8 GM and logs are working. resolving as not our bug.", "updateAuthor": { "name": "cng", "key": "cng", "displayName": "Chee Kiat Ng", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2016-09-08T06:19:12.000+0000", "updated": "2016-09-08T06:19:12.000+0000" }, { "id": "395764", "author": { "name": "perdona", "key": "perdona", "displayName": "Caio Perdona", "active": true, "timeZone": "America/Los_Angeles" }, "body": "This is CRITICAL and we're having this issue since 5.2.0.GA. It is EXTREMELY DISAPPOINTING as we cannot debug on the device.\r\n", "updateAuthor": { "name": "perdona", "key": "perdona", "displayName": "Caio Perdona", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2016-09-09T21:27:02.000+0000", "updated": "2016-09-09T21:27:02.000+0000" }, { "id": "395986", "author": { "name": "stereoket", "key": "stereoket", "displayName": "Ketan Majmudar", "active": true, "timeZone": "Europe/London" }, "body": "I can't see logs on Sim or Device running ios10 for apps built with 5.4.0.GA (Ti SDK) using Xcode 7 (SDK v9.3)\r\n\r\nWe have a bug that needs to be resolved, we need logging to do this.", "updateAuthor": { "name": "stereoket", "key": "stereoket", "displayName": "Ketan Majmudar", "active": true, "timeZone": "Europe/London" }, "created": "2016-09-13T06:41:48.000+0000", "updated": "2016-09-13T06:41:48.000+0000" }, { "id": "395993", "author": { "name": "stereoket", "key": "stereoket", "displayName": "Ketan Majmudar", "active": true, "timeZone": "Europe/London" }, "body": "For now, (as we are using a custom logging function wrapped around the Ti.API logging) i have modified this to write all the log levels out to a flat file using Ti.Filesystem , which I can review in the iOS Simulator file structure. It's better than nothing. Actually found the iOS 10 issue i was looking for straight away.", "updateAuthor": { "name": "stereoket", "key": "stereoket", "displayName": "Ketan Majmudar", "active": true, "timeZone": "Europe/London" }, "created": "2016-09-13T09:18:11.000+0000", "updated": "2016-09-13T09:18:11.000+0000" }, { "id": "395995", "author": { "name": "hknoechel", "key": "hansknoechel", "displayName": "Hans Knöchel", "active": true, "timeZone": "Europe/Berlin" }, "body": "This issue is currently being investigated. It is caused by a major Xcode 8 issue that changed the whole logging- and debugging-system of iOS-apps. That's why many native apps currently run into the same issue. We thought Apple will provide a suitable fix for the GM but they didn't, so we are searching for a better way. Keeping this ticket updated.", "updateAuthor": { "name": "hknoechel", "key": "hansknoechel", "displayName": "Hans Knöchel", "active": true, "timeZone": "Europe/Berlin" }, "created": "2016-09-13T09:22:36.000+0000", "updated": "2016-09-13T09:22:36.000+0000" }, { "id": "396364", "author": { "name": "perdona", "key": "perdona", "displayName": "Caio Perdona", "active": true, "timeZone": "America/Los_Angeles" }, "body": "@Hans Hi Hans. Any update on this issue?", "updateAuthor": { "name": "perdona", "key": "perdona", "displayName": "Caio Perdona", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2016-09-16T17:56:43.000+0000", "updated": "2016-09-16T17:56:43.000+0000" }, { "id": "396370", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "[~perdona] I'm actively working on this. I've got a solution, but it's going to take some time to fix. We have to do quite a bit of work on both the Node.js build tooling and the iOS platform code. Please watch this ticket for updates.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-09-16T18:23:05.000+0000", "updated": "2016-09-16T18:23:05.000+0000" }, { "id": "396371", "author": { "name": "perdona", "key": "perdona", "displayName": "Caio Perdona", "active": true, "timeZone": "America/Los_Angeles" }, "body": "@Chris Barber Hi Chris. I'll keep tracking this ticket, thanks for the feedback!", "updateAuthor": { "name": "perdona", "key": "perdona", "displayName": "Caio Perdona", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2016-09-16T18:34:22.000+0000", "updated": "2016-09-16T18:34:22.000+0000" }, { "id": "396643", "author": { "name": "bfreid", "key": "bfreid", "displayName": "Brian Freid", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Can someone please provide an update on this ticket? Do you have an ETA of when this might be resolved? ", "updateAuthor": { "name": "bfreid", "key": "bfreid", "displayName": "Brian Freid", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2016-09-20T13:27:58.000+0000", "updated": "2016-09-20T13:27:58.000+0000" }, { "id": "396653", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "[~bfreid] This ticket is in progress. It will be fixed for Titanium SDK 6.0.0. Please watch this ticket to track the progress. Once it has been fixed, you can download and install an unstable CI (continuous integration) build or wait until 6.0.0 ships.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-09-20T14:12:54.000+0000", "updated": "2016-09-20T14:12:54.000+0000" }, { "id": "396657", "author": { "name": "jkneen", "key": "jkneen", "displayName": "Jason Kneen", "active": false, "timeZone": "Africa/Ceuta" }, "body": "Those facing this issue (including native developers), there's a workaround if you're running macOS Sierra -- the new console app can be used to select a device that's plugged in, and using filtering you can filter by process and see real-time logs.", "updateAuthor": { "name": "jkneen", "key": "jkneen", "displayName": "Jason Kneen", "active": false, "timeZone": "Africa/Ceuta" }, "created": "2016-09-20T14:25:51.000+0000", "updated": "2016-09-20T14:25:51.000+0000" }, { "id": "396682", "author": { "name": "acvauctions", "key": "acvauctions", "displayName": "Tim Poulsen (ACV)", "active": true, "timeZone": "America/New_York" }, "body": "LemonJar's iOS Console is also useful http://lemonjar.com/iosconsole/ Logs are noisy now. But you can filter on {{[INFO]}} for example to pare down to your own console.log messages.", "updateAuthor": { "name": "acvauctions", "key": "acvauctions", "displayName": "Tim Poulsen (ACV)", "active": true, "timeZone": "America/New_York" }, "created": "2016-09-20T16:14:10.000+0000", "updated": "2016-09-20T16:14:10.000+0000" }, { "id": "396710", "author": { "name": "bfreid", "key": "bfreid", "displayName": "Brian Freid", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Tim Poulsen, Thank you for your help. Because of your fix to the logs we were able to track down the issues that Facebook was experiencing and resolve our issue. Thank you so much for your help and patience in this matter. ", "updateAuthor": { "name": "bfreid", "key": "bfreid", "displayName": "Brian Freid", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2016-09-20T20:13:22.000+0000", "updated": "2016-09-20T20:13:22.000+0000" }, { "id": "398551", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "node-ios-device PR: https://github.com/appcelerator/node-ios-device/pull/25\r\nioslib PR: https://github.com/appcelerator/ioslib/pull/48\r\n\r\nTiSDK master PR: https://github.com/appcelerator/titanium_mobile/pull/8495\r\nTiSDK 6_0_X PR: https://github.com/appcelerator/titanium_mobile/pull/8496", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-10-10T23:19:25.000+0000", "updated": "2016-10-10T23:47:05.000+0000" }, { "id": "398575", "author": { "name": "cng", "key": "cng", "displayName": "Chee Kiat Ng", "active": false, "timeZone": "America/Los_Angeles" }, "body": "CR and FT passed. Tested with combinations of:\r\n- iOS 10 simulators and devices.\r\n- run-on-main-thread true/false.\r\n- use-jscore-framework true/false.\r\n- put app to background and return.\r\n- with wifi / without wifi enabled on device.\r\n\r\nMore scenarios to consider:\r\n- on Xcode 7.3.1.\r\n- on Alloy projects.\r\n- on Studio with live view or debugger enabled.", "updateAuthor": { "name": "cng", "key": "cng", "displayName": "Chee Kiat Ng", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2016-10-11T07:19:28.000+0000", "updated": "2016-10-11T07:19:28.000+0000" }, { "id": "398576", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "To test, create a new app and add a bunch of log calls or just use my attached {{app.js}}.\r\n\r\nBuild for iOS Simulator and launch app, then:\r\n* Fire home button twice and kill the app -> logging should stop and build should exit\r\n* Kill the simulator -> logging should stop and build should exit\r\n* Background the app -> setInterval() logging should continue\r\n\r\nBuild for device and launch app, then:\r\n* Tap home button twice and kill the app - logging should stop and build should exit\r\n* Unplug the device -> logging should stop and build should exit\r\n* Background the app -> setInterval() logging should pause", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-10-11T07:24:45.000+0000", "updated": "2016-10-11T07:26:33.000+0000" }, { "id": "398578", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "h2. Important!\r\n\r\nThe new logging system uses a TCP port. The port number is ALWAYS determined at build time, never at run time. This means that if you build two different Titanium apps, they cannot use the same port at the same time. There are a couple ways the tooling works to overcome this.\r\n\r\nFor both simulator and device builds, the iOS build will auto-select a port between 10000 and 60000 based on the app id. For example, the app id {{com.appcelerator.testapp3269}} will generate the port {{10416}}. The primary reason we do this is attempt to avoid the same port being used by different apps. The other reason we do this so we don't have a different port each build and crippling differential builds. A nice side-effect is the new logging system allows multiple simultaneous clients as well as reconnects and having a consistent port is convenient.\r\n\r\nIt is important to note that because we are auto-selecting a port number based on the app id, the probability of a collision is extremely high. {{com.appcelerator.testapp17}} and {{com.appcelerator.testapp8249}} both resolve to port {{19024}}. This is where {{}} comes in handy. You may specify a {{XXXXX}} in the {{}} section of the {{tiapp.xml}} and it will always be used first. Also note that the port number must be an integer between 1 and 65535 and probably should be greater than {{1024}} to avoid binding to a privileged port. The port number should be unique per project. You only need to use this if the auto-selected port number is causing collisions with other apps. This is really only a problem when working with multiple projects at the same time.\r\n\r\nIf there is a collision where two different apps are being built AND running at the same time with the same port, the first app to launch will get the port. The second app will try to bind to it, but it will fail. It is very important to note that whichever app launches 2nd will fail to bind to the port, however the 2nd app will still continue to run normally, just without logs. For simulator builds, you can open the simulator's {{system.log}}, or for device builds, use the macOS Sierra Console application at any time to view the log messages.\r\n\r\nThe biggest issue to be aware of is the 2nd app's iOS build will end up connecting to the 1st app's log server. There is currently no way for the iOS build to know which log server for which app it has connected to. In the future we may introduce a more proper protocol to handle this.\r\n\r\nFor simulator builds only, the port is shared with the local machine. For example, you could use port {{27017}} for device builds, but you can't for simulator builds if you have MongoDB installed. So, if there is no {{}}, or there is, but it's not available, or the app id-based port is not available, then the iOS build will fallback to a random port number that will certainly change every build.\r\n\r\nIt's also worth noting that for simulator builds only, the iOS build will start up a Node.js server on the selected port to make sure it's available. If it isn't, it will randomly test ports until it finds an available port. To be clear, device builds do not have this limitation.\r\n\r\nThe client in the iOS build that connects to the app will always connect after the app has started. This means it's possible for several messages to have already been logged. Because of this, Titanium will queue the last 100 log messages only while there are no client connections. As soon as the iOS build connects to the log server, the queue is flushed and released. This shouldn't be a huge deal since the client tries to connect every 250ms.\r\n\r\nFinally, logging is only enabled for simulator and device builds. It is NOT enabled for app store or adhoc builds. You can enable it by hacking the build system or via a CLI plugin.\r\n\r\n[~bimmel] please use the rambling above to document the behavior, limitations, and settings. Thanks!", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-10-11T08:38:03.000+0000", "updated": "2016-10-11T08:38:03.000+0000" }, { "id": "398610", "author": { "name": "hknoechel", "key": "hansknoechel", "displayName": "Hans Knöchel", "active": true, "timeZone": "Europe/Berlin" }, "body": "PR's merged! The latest build (6.0.0.v20161011102836) includes the fix. It actually does much more than \"just\" fixing it, it also speeds up the printed logs using a TCP connection instead of watching the log-file manually. To all watchers of this ticket: Please test the new 6.0.0 build (e.g. using {{appc ti sdk install -b 6_0_X}} or download your preferred build [from here|http://builds.appcelerator.com/#6_0_X]. We will most likely release 6.0.0 Beta next week that will of course also include the change. Code strong and probs to [~cbarber]!", "updateAuthor": { "name": "hknoechel", "key": "hansknoechel", "displayName": "Hans Knöchel", "active": true, "timeZone": "Europe/Berlin" }, "created": "2016-10-11T18:20:45.000+0000", "updated": "2016-10-11T18:20:45.000+0000" }, { "id": "398678", "author": { "name": "htbryant", "key": "htbryant", "displayName": "Harry Bryant", "active": true, "timeZone": "Europe/London" }, "body": "Verified as fixed, ran the above test cases on iOS Simulator and Device.\r\n\r\nTested On:\r\niPhone 6 Plus 10.0.2 Device & Simulator\r\nMac OS Sierra (10.12)\r\nTi SDK: 6.0.0.v20161012041242\r\nAppc Studio: 4.8.0.201610060953\r\nAppc NPM: 4.2.8-7\r\nApp CLI: 6.0.0-57\r\nXcode 8.0 \r\nNode v4.4.7\r\n\r\n*Closing ticket.*", "updateAuthor": { "name": "htbryant", "key": "htbryant", "displayName": "Harry Bryant", "active": true, "timeZone": "Europe/London" }, "created": "2016-10-12T16:15:11.000+0000", "updated": "2016-10-12T16:15:11.000+0000" }, { "id": "398798", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "Reopening to assign sprint", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-10-13T03:04:28.000+0000", "updated": "2016-10-13T03:04:28.000+0000" }, { "id": "398799", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "Sorry for so many re-opens and closings. Jira keeps removing the sprint when this ticket is closed. Ugh.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-10-13T03:07:46.000+0000", "updated": "2016-10-13T03:07:46.000+0000" }, { "id": "399001", "author": { "name": "amukherjee", "key": "amukherjee", "displayName": "Abir Mukherjee", "active": true, "timeZone": "America/Los_Angeles" }, "body": "I understand that the Jira was reopened because the sprint info was removed by Jira, but I also verified the fix with an iOS 10 device. I first reproduced the issue with Titanium SDK version 5.5. There were no console message in Studio with 5.5. Then I retried with Titanium SDK version 6.0.0.v20161013072802, and I saw appropriate log messages.\r\n\r\nThis is my environment:\r\nDevice: iPhone 7 iOS 10.0.1\r\nNPM Version: 2.15.9 \r\nNode Version: 4.5.0 \r\nMac OS: 10.11.6 \r\nAppc CLI: 5.5.0 \r\nAppc CLI NPM: 4.2.7 \r\nTitanium SDK version: 6.0.0.v20161013072802 \r\nAppcelerator Studio, build: 4.7.1.201609100950 \r\nXcode 8.0 GM\r\n", "updateAuthor": { "name": "amukherjee", "key": "amukherjee", "displayName": "Abir Mukherjee", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2016-10-14T20:36:27.000+0000", "updated": "2016-10-14T20:36:27.000+0000" }, { "id": "399126", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "Reopening to try and assign sprint again.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-10-17T17:45:17.000+0000", "updated": "2016-10-17T17:45:17.000+0000" }, { "id": "402232", "author": { "name": "cerw", "key": "cerw", "displayName": "Petr Cervenka", "active": true, "timeZone": "Asia/Shanghai" }, "body": "Any chance this can get fixed in 5.5 branch ? ", "updateAuthor": { "name": "cerw", "key": "cerw", "displayName": "Petr Cervenka", "active": true, "timeZone": "Asia/Shanghai" }, "created": "2016-11-30T02:27:09.000+0000", "updated": "2016-11-30T02:27:09.000+0000" }, { "id": "403010", "author": { "name": "jason.squire@gmail.com", "key": "jason.squire@gmail.com", "displayName": "Jason Squire", "active": true, "timeZone": "America/Los_Angeles" }, "body": "I am having the same issue on iOS 10 devices in the 5.5 branch.", "updateAuthor": { "name": "jason.squire@gmail.com", "key": "jason.squire@gmail.com", "displayName": "Jason Squire", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2016-12-08T19:49:05.000+0000", "updated": "2016-12-08T19:49:05.000+0000" }, { "id": "403012", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "[~jason.squire%40gmail.com] This was fixed in 6.0.0. Titanium 5.x and older does not support Xcode 8 and iOS 10.\r\n\r\n[~cerw] Sorry, there's no plans to backport the new logging facilities to 5.x.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-12-08T19:54:08.000+0000", "updated": "2016-12-08T19:54:08.000+0000" }, { "id": "403843", "author": { "name": "ray@raymondverbruggen.nl", "key": "ray@raymondverbruggen.nl", "displayName": "Raymond Verbruggen", "active": true, "timeZone": "Europe/Berlin" }, "body": "This blocks development and updates completely!\r\n\r\nA lot of modules bought from the Appcelerator Marketplace are not supported by SDK 6 (for whatever reason???).\r\n\r\nSo PLEASE either remove blocking of modules in SDK6, or backport logging to the SDK5.x development chain.\r\n\r\n", "updateAuthor": { "name": "ray@raymondverbruggen.nl", "key": "ray@raymondverbruggen.nl", "displayName": "Raymond Verbruggen", "active": true, "timeZone": "Europe/Berlin" }, "created": "2016-12-23T14:24:50.000+0000", "updated": "2016-12-23T14:24:50.000+0000" }, { "id": "403847", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "[~ray@raymondverbruggen.nl] iOS modules that work for Titanium 5.x should work in Titanium 6.x. I'm pretty sure it's just Android that was affected thanks to updating the V8 version.\r\n\r\nBackporting the iOS device logging is a massive amount of work and I don't see us doing that. If you upgrade to macOS Sierra, you can use the new system log tools to view the \"process\" logs.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-12-23T16:15:03.000+0000", "updated": "2016-12-23T16:15:03.000+0000" }, { "id": "403851", "author": { "name": "ray@raymondverbruggen.nl", "key": "ray@raymondverbruggen.nl", "displayName": "Raymond Verbruggen", "active": true, "timeZone": "Europe/Berlin" }, "body": "Hello Chris,\r\n\r\nThank you for your rapid response.\r\n\r\nI think that the amount of trouble that is caused by simply saying \"appcelerator does not support ... anymore\" is underestimated. It looks to me that there is only attention to OS'es new gimmicks, instead of realizing that a lot of developers have an update issue of existing apps for customers.\r\nIt's a developer's nightmare to be confronted with having released apps that cannot be continued/developed/supported by newer versions of the development chain.\r\nFor example see the screenshot.\r\nThis is a module that is critical for several apps. The company that I bought the module from is not responding to any questions at all. Likely no 6.x update will be made available. I need to update this large app, as it looks now I must develop/buy a completely new Bluetooth module. It is from Appcelerator's side too easy to simply \"not support\" it. Source code is not available so updating the module is not possible by me. Didn't you think of the number of module supplier's that are confronted by having to update their modules?\r\n\r\n\"Just Android that was affected\"... we are talking about a multi platform development tool! You cannot simply cut off 50% of all apps!\r\n\r\nWho is going to pay for all extra cost? I cannot do that because my company is too small.\r\n\r\nWhat is needed is a 5.x to 6.x migration guide; what can you encounter and how can you solve it?\r\nThe solution for a lot of developers in my opinion is to make 6.x support older modules!!!\r\nOtherwise it stops for us.\r\n\r\nLooking forward to hearing from you again.\r\nBest regards,\r\nRaymond", "updateAuthor": { "name": "ray@raymondverbruggen.nl", "key": "ray@raymondverbruggen.nl", "displayName": "Raymond Verbruggen", "active": true, "timeZone": "Europe/Berlin" }, "created": "2016-12-23T19:30:49.000+0000", "updated": "2016-12-23T19:30:49.000+0000" }, { "id": "403854", "author": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Hi [~ray@raymondverbruggen.nl],\r\n\r\nPlease note that our primary goal here is to make sure our customers are well-supported. With this, I believe you have a number of options already. Remember that our hand is forced here as well--Apple broke its existing logging system with iOS 10, and Google breaks compatibility with new versions of Chrome. But we have to support new versions of iOS, and new versions of Chrome bring many new features and improvements.\r\n\r\n# If you want to stick with SDK 5.X, use macOS Sierra for logging output, as Chris explained.\r\n# If you want to upgrade to SDK 6.X, realistically, only the Android modules needed recompiling (as the Chrome interface changed). Thus, your iOS bluetooth module should continue to work.\r\n# Our source code is open, so an interested party could backport the changes themselves.\r\n\r\nThere is a long set of release notes here: http://docs.appcelerator.com/platform/latest/#!/guide/Titanium_SDK_6.0.0.GA_Release_Note that detail many of the changes. It's impossible to make SDK 6.0 support older modules because of the requirements of Chrome updates.\r\n\r\nIf these options still do not meet your needs, please file a support ticket, and we'll see how else we can assist.\r\n\r\nBest,\r\nIngo", "updateAuthor": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2016-12-23T22:02:28.000+0000", "updated": "2016-12-23T22:02:28.000+0000" }, { "id": "403855", "author": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Apologies, I meant V8, not Chrome above.", "updateAuthor": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2016-12-23T23:30:22.000+0000", "updated": "2016-12-23T23:30:22.000+0000" }, { "id": "404144", "author": { "name": "ray@raymondverbruggen.nl", "key": "ray@raymondverbruggen.nl", "displayName": "Raymond Verbruggen", "active": true, "timeZone": "Europe/Berlin" }, "body": "Hi Ingo,\r\n\r\nFirst of all the best wishes for 2017!!\r\n\r\nI understand what you are saying.\r\nAnd I understand that you are confronted with changes.\r\n\r\nMy main issue is that we - as developers - need to maintain apps for customers.\r\nI choose for appcelerator already about 5 years ago, because of it's single code-base multi platform system.\r\nDuring the time a lot of appcelerator major updates we have been confronted with changes that need a lot of extra work.\r\nWork without adding functionality or improvements, only to keep the development toolchain up to date.\r\n\r\nThe following happened:\r\nNeeded to do a small quick update for a customer.\r\n\r\nNo logging! Google help -> the Ti.API.info IOS10 logging issue. This one is not mentioned nor is there a compatible workaround documented.\r\n\"Use macOS Sierra for logging output\"... what? how? A major function is not working anymore, so a little more help than that is needed...\r\n\r\nSwitch to SDK6, but some Android modules are not supported anymore.\r\nAlso the given Ti.include(\"functions.js\") workaround does not work anymore in my Alloy project (yes, it did). From alloy.js it does not include the \"functions.js\" file in the lib folder. Already deprecated since 3.3.0? SDK compiler 5.x still did not give a message about this. And I can surely understand that \"require\" is much better but there is no time for changing all that now. Lot of functions, and no right-click -> find references function in Appcelerator Studio...\r\n\r\nI hope you can understand my frustrations.\r\n\r\nLike I said, what is needed is a 5.x to 6.x migration guide; what can you encounter and how can you solve it? \r\nInstead of needing to call google for help when something is not working.\r\n\r\nBest regards,\r\nRaymond", "updateAuthor": { "name": "ray@raymondverbruggen.nl", "key": "ray@raymondverbruggen.nl", "displayName": "Raymond Verbruggen", "active": true, "timeZone": "Europe/Berlin" }, "created": "2017-01-05T13:34:07.000+0000", "updated": "2017-01-05T13:34:07.000+0000" }, { "id": "404150", "author": { "name": "jkneen", "key": "jkneen", "displayName": "Jason Kneen", "active": false, "timeZone": "Africa/Ceuta" }, "body": "Raymond,\r\n\r\nYou should be able to view logs on iOS 10 devices with your current setup using \r\n\r\nhttps://lemonjar.com/iosconsole/\r\n\r\nAlternatively, you can run 5.5.1.GA (which doesn't require Android V8 module re-compiling and should be a small update from 5.4.0 given my experience with updating apps from 5.4 to 5.5) with Sierra and view using the built-in console app (which is way better than the El Capitan one). \r\n\r\nRe Ti.Include -- this was deprecated years ago and replaced with a CommonJS approach which is what Alloy is based on. Mixing CommonJS and Ti.Include isn't a good solution can lead to many more issues. It should be straight-forward as well to port your Includes to commonJS modules, which will give better isolation, and reduce the risk of performance issues and memory leaks.\r\n\r\nPing me on Ti-Slack if you have any issues.\r\n\r\nJason\r\n\r\n\r\n\r\n", "updateAuthor": { "name": "jkneen", "key": "jkneen", "displayName": "Jason Kneen", "active": false, "timeZone": "Africa/Ceuta" }, "created": "2017-01-05T15:04:02.000+0000", "updated": "2017-01-05T15:04:02.000+0000" } ], "maxResults": 41, "total": 41, "startAt": 0 } } }