Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-15997] Incremental builds while modifying custom android manifest files do not work

GitHub Issuen/a
TypeBug
PriorityLow
StatusClosed
ResolutionWon't Fix
Resolution Date2016-09-06T22:17:04.000+0000
Affected Version/sRelease 3.2.0
Fix Version/sn/a
ComponentsAndroid, CLI
Labelsn/a
ReporterAllen Yeung
AssigneeChris Barber
Created2013-12-16T08:09:51.000+0000
Updated2017-03-23T22:33:21.000+0000

Description

Steps to reproduce: 1. Build an android project with a file named AndroidManifest1.xml inside platform/android 2. Rename the AndroidManifest1.xml to AndroidManifest.xml Expected: The manifest inside the build directory should not be symlinked to the one in platform/android Actual: It is symlinked to it. Doing a clean build after renaming the manifest will fix this problem.

Comments

  1. Chris Barber 2016-09-06

    There is no issue with the AndroidManifest.xml being symlinked. We shall not change it. When the Android build was rewritten for Node.js, a flaw was purposely ported from the old Python code. For iOS, <plist> overrides a custom Info.plist and a custom Info.plist overrides the default Info.plst. However with Android, if a custom AndroidManifest.xml is present, the <manifest> section of the tiapp.xml does NOT override the custom AndroidManifest.xml by default. To enable this behavior, you must set ti config android.mergeCustomAndroidManifest true. I have created TIMOB-23872 to enable the merging of custom AndroidManifest values over custom AndroidManifest.xml files.
  2. Lee Morris 2017-03-23

    Closing ticket as Won't Fix with reference to the above comments.

JSON Source