[AC-3021] Launcher Icons: density specific icons are never used (Android)
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | n/a |
| Status | Closed |
| Resolution | Needs more info |
| Resolution Date | 2011-12-19T02:51:54.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Studio, Titanium SDK & CLI |
| Labels | android, defect |
| Reporter | Shawn Lipscomb |
| Assignee | Paul Dowsett |
| Created | 2011-09-27T08:37:03.000+0000 |
| Updated | 2016-03-08T07:48:03.000+0000 |
Description
Launcher icons in 3 sizes that are put into the platform/android/res/drawable-DENSITY folders (e.g. drawable-mdpi, drawable-ldpi, drawable-hdpi) are never used as launcher icons when the app is installed on an Android device. Ti Studio forces you to specify a program icon in the tiapp.xml Overview page, and that icon file has to be in the Resources directory (you get an i/o error 2 if there is no icon in the Resources dir). Titanium apps are using the Resources copy of the icon for everything.
Q&A entry here: http://developer.appcelerator.com/question/124701/launcher-icons---how-to-get-titanium-to-correctly-use-the-right-size
Still having thie same problem.
Shawn Thank you for this ticket. Would you please provide [a Test Case](https://wiki.appcelerator.org/display/guides/How+to+Submit+a+Bug+Report#HowtoSubmitaBugReport-CreatingaTestCase) to prove the bug, and to test it when it's resolved? Although I would ordinarily request it to be added to the body of the ticket, as the issue relates to assets, it's probably best to add it as a archived project. Would you also check this ticket against [How to Submit a Bug Report](https://wiki.appcelerator.org/display/guides/How+to+Submit+a+Bug+Report) to verify that you have included all the rest of the necessary information (for example, the copied and pasted exception). I will resolve this ticket for the moment - please reopen to update it. Once the information is provided, I can move it to the main project. Thanks in advance
Closing due to inactivity. If this issue still exists, please raise a new ticket, including all the information in the [JIRA Ticket Checklist](https://wiki.appcelerator.org/display/guides/How+to+Submit+a+Bug+Report#HowtoSubmitaBugReport-JIRATicketChecklist) to ensure that we can escalate it quickly. Read [How to Submit a Bug Report](https://wiki.appcelerator.org/display/guides/How+to+Submit+a+Bug+Report) if you have not read it before, and always start a ticket using the [JIRA Ticket Template](https://wiki.appcelerator.org/display/guides/JIRA+Ticket+Template). Thanks in advance