[TIMOB-16169] Android: Build error with _build.js file with 3.2.0 release
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2014-01-17T19:11:19.000+0000 |
Affected Version/s | Release 3.2.0 |
Fix Version/s | 2014 Sprint 01, 2014 Sprint 01 Core, Release 3.2.3, Release 3.3.0 |
Components | Android |
Labels | n/a |
Reporter | daniele iuppariello |
Assignee | Chris Barber |
Created | 2014-01-10T11:39:17.000+0000 |
Updated | 2014-03-24T09:55:54.000+0000 |
Description
Steps to Reproduce
I tried to compile an existing project with new SDK 3.2.0 in Android and got a critical error [ERROR] Application Installer abnormal process termination. Process exit value was 8 (see log attachment for more details)Actual Result
errorExpected Result
I solved changhing in the file /Users/diuppariello/Library/Application Support/Titanium/mobilesdk/osx/3.2.0.GA/android/cli/commands/_build.js:2195 m[3].toLowerCase() in m[1].toLowerCase(). please, fix it with the next release! :)Attachments
File | Date | Size |
---|---|---|
.log | 2014-01-10T11:39:25.000+0000 | 3444227 |
log.txt | 2014-01-10T11:39:26.000+0000 | 1609 |
I do not think this ticket is related to TC-3487.
Master pull request: https://github.com/appcelerator/titanium_mobile/pull/5230 3.2.x pull request: https://github.com/appcelerator/titanium_mobile/pull/5231 To test: 1. create an android app 2. create the folder Resources/android/images 3. copy the appicon.png into Resources/android/images 4. rename the image to "high.png" 5. build the app
Checked on: Appcelerator Studio: 3.2.2.201401271736 SDK: 3.2.1.v20140128171647, 3.3.0.v20140128134708 CLI:3.2.1-beta2 The issues does not exist on SDK build 3.3.0.v20140128134708 and applications builds successfully, but the issue still exists on SDK build 3.2.1.v20140128171647
Verified as fixed using, Mavericks 10.9.2 Xcode: 5.1 Appcelerator Studio build: 3.2.3.v20140323233607 SDK: 3.2.3.v20140323211726 acs: 1.0.14 alloy: 1.3.1 titanium: 3.2.1 code processor: 1.1.0 I verified it as per the comment mentioned by Chris also and the app launches successfully without any error.