[ALOY-760] Generate runtime files to Titanium platform-specific folders
| GitHub Issue | n/a |
|---|---|
| Type | Improvement |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2014-08-05T23:51:19.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Alloy 1.3.0, 2013 Sprint 22 |
| Components | Titanium SDK, Tooling |
| Labels | notable, qe-automatedtest |
| Reporter | Tony Lukasavage |
| Assignee | Tony Lukasavage |
| Created | 2013-07-24T19:48:08.000+0000 |
| Updated | 2014-08-05T23:51:51.000+0000 |
Description
When Alloy generates files and deploys them to the Resources folder, it does not make use of the platform-specific folders. It should do so in the future to allow multiple platforms to run together and to be deployed to successfully. This will be useful for liveview and tishadow.
PR: https://github.com/appcelerator/alloy/pull/211 Functional testing can be confirmed by running the automated tests. In addition, I'd suggest running any complex alloy apps we have at our disposal for multiple platforms. Be sure to switch between the platforms multiple times to ensure that the platform-specific files are be created during the appropriate builds.
Re-opening due to TIMOB-14884
Tested on iPad with TiSDK 3.2.0.v20131022171645. iOS is now using the platform-specific commonjs files on devices as expected.