[AC-2256] Renamed asset is not reflected in Resources folder on clean build when filenames differ in lower/upper case only
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | n/a |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2013-09-09T20:53:10.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Alloy |
| Labels | n/a |
| Reporter | Stefan Funk |
| Assignee | Mauro Parra-Miranda |
| Created | 2013-07-29T20:30:16.000+0000 |
| Updated | 2016-03-08T07:41:15.000+0000 |
Description
- create an Alloy project
- add an image to the app/assets/images folder with name "Test.png"
- create an ImageView and reference the image with "/images/test.png"
Note the upper/lower-case difference
- build and run on Android emulator
observe that the image is not found/displayed
- right-click the image in the app/assets/images folder and rename it properly to "test.png" with lower-case "t"
- clean the build
- notice that the Resources folder is not removed
- build and run on Android emulator
observe that the image is still not found/displayed
Solution
- delete the Resources folder in addition to cleaning the build
Expected that cleaning the build would ensure that files are properly updated.
Seems to work properly when the filenames differ in more than lower/uppercase writing.
Please provide a testcase.
This is invalid. iOS and Android are case sensitive.
I am not sure why this is invalid. The problem is that a clean build does not seem to copy a resource to the resources folder when it's upper/lower-case spelling has changed. It maybe filed at the wrong place, as it is a Titanium Studio problem.
Invalid issue.