[ALOY-810] When moving app outside Studio workspace, alloy compile fails
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2014-01-20T22:41:56.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | n/a |
| Labels | n/a |
| Reporter | Davide Cassenti |
| Assignee | Unknown |
| Created | 2013-08-29T09:43:34.000+0000 |
| Updated | 2018-03-07T22:28:25.000+0000 |
Description
Steps to reproduce
1) create an app in Appcelerator Studio 2) move the app's directory into a different path (~/Downloads/) 3) open the new path in console 4) alloy compile --config platform=iosActual result
Compilation fails with this error: ~~~ [ERROR] Alloy "app" directory does not exist at "/Users/dcassenti/Downloads/app" ~~~ Running the same command when the app is in the workspace works; same happens if - instead of creating a new app - I do: 1) download someone's app in ~/Downloads/ 2) open the app's main directory 3) alloy compile --config platform=iosComments
- Davide Cassenti 2013-08-29 I checked the alloy source, actually the problem is different. It fails if you have a tiapp.xml in the parent folder (in my case, I had one ~/Downloads/tiapp.xml). Not sure if this might be considered an issue or not.
- Tony Lukasavage 2014-01-20 Alloy's just doing its best to find what you are trying to compile. It sees a tiapp.xml and an app folder, so it thinks it found it. I think it's fair to expect developers to call the compile form the appropriate folder.
- Eric Merriman 2018-03-07 Closing as invalid. If this is incorrect, please reopen.