Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-13277] Android: Module Packaging fails with exec returned 2

GitHub Issuen/a
TypeBug
PriorityCritical
StatusClosed
ResolutionCannot Reproduce
Resolution Date2013-04-01T22:41:27.000+0000
Affected Version/sn/a
Fix Version/s2013 Sprint 07 Core, 2013 Sprint 07
ComponentsAndroid
Labelsqe-3.1.0, triage
ReporterDustin Hyde
AssigneeAllen Yeung
Created2013-03-28T22:55:35.000+0000
Updated2017-03-21T21:36:41.000+0000

Description

Android Module Packaging fails with exec returned 2. Logs and screenshots attached. Test Steps: 1. Create Android Module. 2. Package Android Module. Test Result: Error.

Attachments

FileDateSize
_bash_profile2013-03-28T23:00:43.000+0000222
android studio preferences.png2013-03-28T22:55:35.000+0000135904
build.properties2013-03-28T22:55:35.000+0000277
studio ant console.txt2013-03-28T22:55:35.000+00001431
studio console error.txt2013-03-28T22:55:35.000+0000430
studio diagnostic log.txt2013-03-28T22:55:35.000+00008640
studio error log.txt2013-03-28T22:55:35.000+000044643
terminal command console.txt2013-03-28T22:55:35.000+00001516
ti info.txt2013-03-28T22:55:35.000+000026358
xcode path.png2013-03-28T22:55:35.000+0000140397
xcode studio preferences.png2013-03-28T22:55:35.000+0000154771
xcode version.png2013-03-28T22:55:35.000+0000681163

Comments

  1. Eric Merriman 2013-03-28

    I have problems with the module before build: Description Resource Path Location Type Project 'dustintestandroid' is missing required library: '/Users/emerriman/Library/Application Support/Titanium/mobilesdk/osx/3.1.0.v20130322171500/android/js.jar' dustintestandroid Build path Build Path Problem
  2. Dustin Hyde 2013-03-29

    A module created using SDK 3.0.2 does not have that resources error, but it fails to package nonetheless.
  3. Blain Hamon 2013-04-01

    For reference, the Ant console refers to a build.xml line 247. That line reads:
       <fail message="Neither the ANDROID_NDK environment variable, or the android.ndk property is not set to an existing Android NDK installation (check your module's build.properties). ">
       	<condition>
       		<not>
       			<or>
       				<available file="${android.ndk}" type="dir"/>
       				<available file="${env.ANDROID_NDK}" type="dir"/>
       
    Which means we should check to see if the test environment has a .bash_profile where ANDROID_NDK is set and the folder exists. This might be an issue of setup.
  4. Allen Yeung 2013-04-01

    I wasn't able to reproduce this on master. I tried creating an packaging a module from studio without any issues.
  5. Lee Morris 2017-03-21

    Closing ticket as the issue cannot be reproduced and due to the above comments.

JSON Source