Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-16814] Android: Setting custom appicon from the appropriate density folder in tiapp.xml copies the icon file to root of the resources folder

GitHub Issuen/a
TypeBug
PriorityMedium
StatusClosed
ResolutionInvalid
Resolution Date2014-04-07T17:01:28.000+0000
Affected Version/sRelease 3.2.3
Fix Version/s2014 Sprint 07, 2014 Sprint 07 Tooling
ComponentsAndroid
Labelsipass1, qe-3.2.3
ReporterLokesh Choudhary
AssigneeChris Barber
Created2014-04-05T00:02:49.000+0000
Updated2017-03-03T23:14:23.000+0000

Description

Description:

1. Create an app with density specific app icons in the density folder "platform/android/res/drawable-". 2. Delete the appicon.png file in the root of resources folder. 2. In the tiapp.xml in the icon field set the icon path to one of the icons in any of the density folders. 3. Click save.

Actual Result:

1. You will see that the selected app icon in tiapp.xml is copied to the root of the resources folder.

Expected result:

1. The appicon should not get copied to the root of the resources folder.

Comments

  1. Ingo Muschenetz 2014-04-07

    Chris, thoughts?
  2. Chris Barber 2014-04-07

    The Android build gets the name of the icon to use from the tiapp.xml. If that value does not exist, then it defaults to "appicon.png". It then checks the "Resources" and "Resources/android" folder for that icon. If it does not exist, it copies the default appicon.png from the SDK. You cannot specify an that is in the "platform/android/res/drawable-" directory. That's just not how things are designed to work.
  3. Lokesh Choudhary 2017-03-03

    Closing as invalid.

JSON Source