{ "id": "168576", "key": "TIMOB-24895", "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": "6", "description": "", "name": "Hold" }, "resolutiondate": "2019-07-30T15:08:38.000+0000", "created": "2017-06-23T07:38:32.000+0000", "priority": { "name": "Critical", "id": "1" }, "labels": [ "android" ], "versions": [ { "id": "17608", "name": "Release 6.1.0", "archived": false, "released": true, "releaseDate": "2017-05-26" } ], "issuelinks": [], "assignee": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "updated": "2019-07-30T15:08:38.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": "10202", "name": "Android", "description": "Android Platform" }, { "id": "10207", "name": "Tooling" } ], "description": "When building a freshly created Titanium Alloy project the build fails when building the Java source files with the following error:\r\n\r\n{noformat}\r\n[ERROR] : Failed to compile Java source files:\r\n[ERROR] : \r\n[ERROR] : /home/simon/test/Asdf/build/android/gen/de/viinet/asdf/AssetCryptImpl.java:44: error: cannot find symbol\r\n[ERROR] : \t\tRange range = assets.get(path);\r\n[ERROR] : \t\t ^\r\n[ERROR] : symbol: variable assets\r\n[ERROR] : location: class AssetCryptImpl\r\n[ERROR] : /home/simon/test/Asdf/build/android/gen/de/viinet/asdf/AssetCryptImpl.java:48: error: cannot find symbol\r\n[ERROR] : \t\treturn new String(filterDataInRange(assetsBytes, range.offset, range.length));\r\n[ERROR] : \t\t ^\r\n[ERROR] : symbol: variable assetsBytes\r\n[ERROR] : location: class AssetCryptImpl\r\n[ERROR] : Note: /home/simon/test/Asdf/build/android/gen/de/viinet/asdf/AssetCryptImpl.java uses unchecked or unsafe operations.\r\n[ERROR] : Note: Recompile with -Xlint:unchecked for details.\r\n[ERROR] : 2 errors\r\n{noformat}\r\n\r\nThis is because the asset encryption does not finish and the AssetCryptImpl.java does not contain the generated variables. Manually executing the command included in the build output gives a Segmentation Fault. So there seems to be some error with the ELF {{.titanium/mobilesdk/linux/6.1.0.GA/android/titanium_prep.linux64}}\r\n\r\n{noformat}\r\n[INFO] : \b\b \b Encrypting JavaScript files: /home/simon/.titanium/mobilesdk/linux/6.1.0.GA/android/titanium_prep.linux64 \"de.viinet.asdf\" \"/home/simon/test/Asdf/build/android/assets\" \"alloy/CFG.js\" \"app.js\" \"alloy/backbone.js\" \"alloy/constants.js\" \"alloy/controllers/BaseController.js\" \"alloy/controllers/index.js\" \"alloy/styles/index.js\" \"alloy/sync/localStorage.js\" \"alloy/sync/properties.js\" \"alloy/sync/sql.js\" \"alloy/underscore.js\" \"alloy/widget.js\" \"alloy.js\" \"ti.cloud/ti.cloud.js\" \"_app_props_.json\"\r\n{noformat}\r\n\r\nNot quite sure who's responsible because with kernel {{linux-image-4.4.0-79-generic 4.4.0-79.100~14.04.1}} it works like expected.", "attachment": [ { "id": "62729", "filename": "build.log", "author": { "name": "smang", "key": "smang", "displayName": "Simon Mang", "active": true, "timeZone": "Europe/Berlin" }, "created": "2017-06-23T07:37:53.000+0000", "size": 137453, "mimeType": "text/x-log" }, { "id": "62737", "filename": "hello.jar", "author": { "name": "smang", "key": "smang", "displayName": "Simon Mang", "active": true, "timeZone": "Europe/Berlin" }, "created": "2017-06-26T07:32:22.000+0000", "size": 760, "mimeType": "application/x-java-archive" } ], "flagged": false, "summary": "AssetCryptImpl.java symbol not found while build for Android on Linux", "creator": { "name": "smang", "key": "smang", "displayName": "Simon Mang", "active": true, "timeZone": "Europe/Berlin" }, "subtasks": [], "reporter": { "name": "smang", "key": "smang", "displayName": "Simon Mang", "active": true, "timeZone": "Europe/Berlin" }, "environment": "Linux 4.4.0-81-generic #104~14.04.1-Ubuntu x86_64 GNU/Linux\r\nCLI 6.2.2\r\nSDK 6.1.0", "comment": { "comments": [ { "id": "422616", "author": { "name": "knd_rt@hotmail.com", "key": "knd_rt@hotmail.com", "displayName": "knd_rt@hotmail.com", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Got same issue in ubuntu 17.10, it worked perfctly a couple of days ago, so I bet it was a kernel update the \"problem\" but it is exacly same output error", "updateAuthor": { "name": "knd_rt@hotmail.com", "key": "knd_rt@hotmail.com", "displayName": "knd_rt@hotmail.com", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2017-06-23T13:07:45.000+0000", "updated": "2017-06-23T13:07:59.000+0000" }, { "id": "422645", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "[~smang] So if {{linux-image-4.4.0-79-generic 4.4.0-79.100~14.04.1}} works, what kernel version does not work? Also, what Linux distro are you using? Ubuntu?\r\n\r\n[~knd_rt@hotmail.com] Ubuntu 17.10 does not exist.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2017-06-23T17:25:14.000+0000", "updated": "2017-06-23T17:25:14.000+0000" }, { "id": "422646", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "Also note that the Titanium Android build chooses the 32-bit vs 64-bit version of titanium_prep by using the cpu architecture for which Node.js was compiled. In other words, if it is running {{titanium_prep.linux64}}, then you are running the 64-bit version of Node.js which means you're on a 64-bit Linux kernel and 64-bit hardware.\r\n\r\nNow, here's the important part, {{titanium_prep}} dynamically links to the Java Virtual Machine library. In this case, it is critical that you have the 64-bit version of this library installed. From what I recall, there should be a {{i386}} and {{amd64}} versions of {{libjvm.so}}.\r\n\r\nIt's possible that the seg fault is being caused by {{libjvm.so}}. I'm not sure how to test this. Maybe you could check if {{java}} and/or a Java app works with your updated kernel?", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2017-06-23T17:36:19.000+0000", "updated": "2017-06-23T17:36:19.000+0000" }, { "id": "422724", "author": { "name": "smang", "key": "smang", "displayName": "Simon Mang", "active": true, "timeZone": "Europe/Berlin" }, "body": "@cbarber {{Linux 4.4.0-81-generic #104~14.04.1-Ubuntu x86_64 GNU/Linux}} like I mentioned above in the \"Environment\" tag of this issue does not work. And I guess knd_rt meant 16.10 ;)\r\n\r\nI created a HelloWorld java example. And compiling and running it works great on the 4.4.0-81 kernel.", "updateAuthor": { "name": "smang", "key": "smang", "displayName": "Simon Mang", "active": true, "timeZone": "Europe/Berlin" }, "created": "2017-06-26T07:31:01.000+0000", "updated": "2017-06-26T07:31:41.000+0000" }, { "id": "422725", "author": { "name": "smang", "key": "smang", "displayName": "Simon Mang", "active": true, "timeZone": "Europe/Berlin" }, "body": "BTW my java version\r\n\r\n{noformat}\r\njava -version\r\njava version \"1.8.0_72\"\r\nJava(TM) SE Runtime Environment (build 1.8.0_72-b15)\r\nJava HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode)\r\n{noformat}\r\n", "updateAuthor": { "name": "smang", "key": "smang", "displayName": "Simon Mang", "active": true, "timeZone": "Europe/Berlin" }, "created": "2017-06-26T07:33:35.000+0000", "updated": "2017-06-26T07:33:35.000+0000" }, { "id": "422726", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "[~smang] Doh, I missed the environment information. Thanks for the info. I'll see about trying to reproduce the issue.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2017-06-26T07:36:28.000+0000", "updated": "2017-06-26T07:36:28.000+0000" }, { "id": "422734", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "Confirmed the seg fault on Ubuntu 17.04 with Java 1.8 OpenJDK 64-bit and kernel 4.10.0-24-generic.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2017-06-26T16:10:07.000+0000", "updated": "2017-06-26T16:10:07.000+0000" }, { "id": "422834", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "It appears the bug is widespread and affects other software besides Titanium: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772. I'm not certain at this time that A) we can do anything or B) we need to do anything. Once the problem is fixed, we can revisit this ticket and see if it's fixed.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2017-06-26T21:17:57.000+0000", "updated": "2017-06-26T21:17:57.000+0000" } ], "maxResults": 9, "total": 9, "startAt": 0 } } }