[ALOY-803] Windows: issues using subfolders in controllers/views
GitHub Issue | n/a |
Type | Bug |
Priority | Critical |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2013-08-23T02:42:54.000+0000 |
Affected Version/s | Alloy 1.2.2, Alloy 1.2.1, Alloy 1.2.0 |
Fix Version/s | Alloy 1.2.1, 2013 Sprint 17 |
Components | Runtime, Titanium SDK |
Labels | qe-testadded |
Reporter | Federico Casali |
Assignee | Tony Lukasavage |
Created | 2013-08-21T04:10:12.000+0000 |
Updated | 2013-08-26T18:55:13.000+0000 |
Description
Problem description
On Windows, issues could be encountered when using controller subfolders.
Scenario #1
Alloy version 1.2.1-cr
1. Run the "sample1_app.zip" sample code and click on the 'title 1' row.
2. Click on the 'Click' button
Result: 'Runtime error' is displayed, not being able to find the requested module "Requested module not found: alloy/styles/featureswin1" (see screenshot "scenario1_screenshot").
Scenario #2
Alloy version 1.2.1-cr
1. Run the "sample2_app.zip" sample code and click on the 'title 1' row.
2. Click on the 'Click' button
Result: no Runtimes error are now displayed. App works as expected. In this case, 'win1' is not inside the 'features' subfolder.
Scenario #3
Alloy version 1.2.1 (latest from branch) and 1.2.2 (master)
1. Run the "sample1_app.zip" sample code and click on the 'title 1' row.
2. Click on the 'Click' button
Result: 'Runtime error' is displayed, not being able to find the requested module "Requested module not found: alloy/styles/features\win1" (see screenshot "scenario3_screenshot").
Scenario #4
Alloy version 1.2.1 (latest from branch) and 1.2.2 (master)
1. Run the "sample2_app.zip" sample code and click on the 'title 1' row.
2. Click on the 'Click' button
Result: no Runtimes error are now displayed (just like Scenario #2)
Note
Sample codes works correctly on Linux and Mac OS X machines using both Alloy 1.2.1-cr and 1.2.2
Attachments
PR: https://github.com/appcelerator/alloy/pull/233 Test the scenarios in the ticket on Windows and ensure that the aforementioned runtime errors no longer exist.
Verified fixed with the attached samples TiSDK 3.1.3.v20130822140128 Alloy 1.2.1-cr2 & 1.2.2 master Ti Studio 3.1.3.201308201707 CLI 3.1.2 GA Node 0.10.13 Closing.