[TIMOB-15647] Android: CLI: Incremental builds causes js files to be included in encrypted builds
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2013-11-04T09:26:52.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | 2013 Sprint 23, 2013 Sprint 23 Core, Release 3.2.0 |
| Components | Android, CLI |
| Labels | cli, module_android, qe-closed-3.2.0, qe-manualtest, qe-testadded |
| Reporter | Allen Yeung |
| Assignee | Chris Barber |
| Created | 2013-11-03T05:38:19.000+0000 |
| Updated | 2014-11-19T19:20:17.000+0000 |
Description
Steps to reproduce:
1. Build a development build of the app "ti build -p android -T device --deploy-type development"
2. Build a normal device build (which is encrypted)"ti build -p android -T device"
3. Unzip the apk under build/android/bin/yourapp.apk
Expected:
The js files under resource should not be included since they are encrypted
Actual:
The js files are found in the apk
Pull request: https://github.com/appcelerator/titanium_mobile/pull/4905
To test, run:
Then we verify there are no unencrypted .js files in the build resources dir:Tested with: CLI 3.2.0 (git://github.com/appcelerator/titanium.git) Alloy 1.3.3 Titanium SDK, build: 3.2.0.v20131107161747 There is no unencrypted .js files in the build resources dir.