{ "id": "166228", "key": "AC-4818", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "12217", "key": "AC", "name": "Appcelerator - INBOX", "projectCategory": { "id": "10000", "description": "", "name": "Customer Service" } }, "resolution": { "id": "7", "description": "", "name": "Invalid" }, "resolutiondate": "2017-02-23T14:27:45.000+0000", "created": "2017-02-22T17:59:45.000+0000", "labels": [ "android", "manifest", "titanium" ], "versions": [], "issuelinks": [], "assignee": { "name": "shossain", "key": "shossain", "displayName": "Shak Hossain", "active": false, "timeZone": "America/Los_Angeles" }, "updated": "2017-03-02T12:21:29.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": "14548", "name": "Titanium SDK & CLI", "description": "Please enter tickets related to the MobileSDK here." } ], "description": "We have added both intent filters and a second activity to the tiapp.xml but it does not fully transfer to the AndroidManifest.xml. As a work around, we followed the instructions here: \r\n\r\nhttp://docs.appcelerator.com/platform/latest/#!/guide/Maintaining_a_Custom_AndroidManifest.xml\r\n\r\nBut first we received this error:\r\n{{[ERROR] Detected legacy \"/platform\" directory in project directory.\r\n[ERROR] Please move the \"/platform\" directory to \"/app/platform\" for Alloy 1.8.0 or later.\r\n[ERROR] Alloy compiler failed}}\r\n\r\nSo we moved the custom AndroidManifest.xml to /app/platform/android/AndroidManifest.xml and we STILL could not get the custom manifest.\r\n\r\nThere is an example application here: https://github.com/DaKaZ/multiactive You can see the first activity in the tiapp.xml does not transfer. You can also see that if you create the custom manifest the auto generated manifest is used, not the custom.", "attachment": [], "flagged": false, "summary": "Android manifest in tiapp.xml does not transfer completely to AndroidManifest.xml AND using a custom manifest does not work", "creator": { "name": "dakazmier", "key": "dakazmier", "displayName": "Michael Kazmier", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "dakazmier", "key": "dakazmier", "displayName": "Michael Kazmier", "active": true, "timeZone": "America/Los_Angeles" }, "environment": "SDK: 5.5.1.GA\r\nCLI: 5.0.11\r\nMacOS", "comment": { "comments": [ { "id": "407599", "author": { "name": "dakazmier", "key": "dakazmier", "displayName": "Michael Kazmier", "active": true, "timeZone": "America/Los_Angeles" }, "body": "We found an interesting work around for the first issue - the translation of the tiapp.xml into the AndroidManifest.xml. If you put the second Activity at the same level of the in tiapp.xml it works as desired. So, for the first bug perhaps all that is needed is a documentation update to explain to a user how to do this?", "updateAuthor": { "name": "dakazmier", "key": "dakazmier", "displayName": "Michael Kazmier", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2017-02-22T18:26:10.000+0000", "updated": "2017-02-22T18:26:10.000+0000" }, { "id": "407737", "author": { "name": "sdarda", "key": "sdarda", "displayName": "Sharif AbuDarda", "active": false, "timeZone": "Asia/Dhaka" }, "body": "This should be the ideal case. You should put all your activity under single manifest section in tiapp.xml. Thanks.", "updateAuthor": { "name": "sdarda", "key": "sdarda", "displayName": "Sharif AbuDarda", "active": false, "timeZone": "Asia/Dhaka" }, "created": "2017-02-23T14:27:18.000+0000", "updated": "2017-02-23T14:27:18.000+0000" }, { "id": "407739", "author": { "name": "sdarda", "key": "sdarda", "displayName": "Sharif AbuDarda", "active": false, "timeZone": "Asia/Dhaka" }, "body": "As documented \"Most elements inside the will be added as children to the element inside of AndroidManifest.xml at build time\" in http://docs.appcelerator.com/platform/latest/#!/guide/Maintaining_a_Custom_AndroidManifest.xml", "updateAuthor": { "name": "sdarda", "key": "sdarda", "displayName": "Sharif AbuDarda", "active": false, "timeZone": "Asia/Dhaka" }, "created": "2017-02-23T14:31:24.000+0000", "updated": "2017-02-23T14:31:24.000+0000" }, { "id": "407915", "author": { "name": "dakazmier", "key": "dakazmier", "displayName": "Michael Kazmier", "active": true, "timeZone": "America/Los_Angeles" }, "body": "There are two problems with the documentation:\r\n\r\n1. Declaring a second activity does not work as described\r\n2. The completely custom AndroidManifest.xml does not work\r\n\r\nTo recreate issue #1, try to use this android section:\r\n\r\n\r\n\t\t\r\n\t\t\t\r\n\t\t\t\r\n\t\t\t\t\r\n\t\t\t\t\t\r\n\t\t\t\t\t\t\r\n\t\t\t\t\t\t\r\n\t\t\t\t\t\r\n\t\t\t\t\t\r\n\t\t\t\t\t\t\r\n\t\t\t\t\t\t\r\n\t\t\t\t\t\t\r\n\t\t\t\t\t\t\r\n\t\t\t\t\t\r\n\t\t\t\t\r\n\t\t\t\r\n\t\t\t\t\r\n\t\t\t\t\t\r\n\t\t\t\t\t\r\n\t\t\t\t\r\n\t\t\t\r\n\t\t\t\t\r\n\t\t\t\t\r\n\t\t\t\t\r\n\t\t\t\t\r\n\t\t\t\r\n\t\t\t\r\n\t\t\t\r\n\t\t\t\r\n\t\t\t\r\n\t\t\r\n\t\r\n\r\n\r\nThe above does not work, just check the compiled AndroidManifest.xml for the SecondActivity. Now try this one:\r\n\r\n\t\r\n\t\t\r\n\t\t\t\r\n\t\t\t\r\n\t\t\t\t\r\n\t\t\t\t\t\r\n\t\t\t\t\t\t\r\n\t\t\t\t\t\t\r\n\t\t\t\t\t\r\n\t\t\t\t\t\r\n\t\t\t\t\t\t\r\n\t\t\t\t\t\t\r\n\t\t\t\t\t\t\r\n\t\t\t\t\t\t\r\n\t\t\t\t\t\r\n\t\t\t\t\r\n\t\t\t\t\r\n\t\t\t\t\r\n\t\t\t\t\r\n\t\t\t\t\r\n\t\t\t\r\n\t\t\t\r\n\t\t\t\r\n\t\t\t\r\n\t\t\t\r\n\t\t\r\n\t\t\r\n\t\t\t\r\n\t\t\t\t\r\n\t\t\t\t\t\r\n\t\t\t\t\t\r\n\t\t\t\t\r\n\t\t\t\r\n\t\t\r\n\t\r\n", "updateAuthor": { "name": "dakazmier", "key": "dakazmier", "displayName": "Michael Kazmier", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2017-02-23T22:08:17.000+0000", "updated": "2017-02-23T22:08:17.000+0000" }, { "id": "408302", "author": { "name": "dirleidionisio", "key": "dirleidionisio", "displayName": "Dirlei DionĂ­sio", "active": true, "timeZone": "America/Sao_Paulo" }, "body": "I'm also having the second problem with SDK 6.0.1 in an Alloy Project, but I found a workaround: put the same custom AndroidManifest.xml in both directories: app/platform/android AND platform/android.\r\n\r\nThe build process will use platform/android/AndroidManifest.xml and after that, will rewrite the entire folder by app/platform/android.\r\n\r\nI know, it's a weird workaround, but it works.\r\n\r\nI endorse the claim to have custom android manifest working without workarounds.", "updateAuthor": { "name": "dirleidionisio", "key": "dirleidionisio", "displayName": "Dirlei DionĂ­sio", "active": true, "timeZone": "America/Sao_Paulo" }, "created": "2017-03-02T12:21:29.000+0000", "updated": "2017-03-02T12:21:29.000+0000" } ], "maxResults": 5, "total": 5, "startAt": 0 } } }