[ALOY-632] Builtins being processed out of order
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2013-08-23T19:51:40.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Alloy 1.2.0, Alloy 1.1.2, 2013 Sprint 09 |
| Components | XML |
| Labels | qe-testadded |
| Reporter | Tony Lukasavage |
| Assignee | Tony Lukasavage |
| Created | 2013-04-22T20:20:45.000+0000 |
| Updated | 2013-08-23T19:51:51.000+0000 |
Description
http://developer.appcelerator.com/question/151234/alloy---why-osios-undefined-in-built-in-animation-file
Essentially, builtins are being added in after they have already been processed, leaving behind bare compiler directives (OS_IOS for example), leaving a runtime error. We should make sure that builtins are added only once, or that they are added first before any other processing.
The bug fix can be verified with the test case found attached to ALOY-633 which references the same issue. It simply needs to run without a runtime exception to confirm that the bug has been resolved. Same goes for ALOY-633.
test app: https://github.com/appcelerator/alloy/tree/master/test/apps/testing/ALOY-632
Verified as fixed with Alloy 1.1.2-alpha version (verified crashing on 1.1.0) Anroid Nexus 4 and iPhone 5 devices Closing.
Reopen to apply label