[TIMOB-17059] Unable to package Android Module
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2018-02-26T15:33:42.000+0000 |
Affected Version/s | Release 3.3.0 |
Fix Version/s | Release 3.3.0, Release 3.4.0 |
Components | Android, CLI |
Labels | module_module, qe-3.3.0, qe-testadded |
Reporter | Deepti Pandey |
Assignee | Chris Barber |
Created | 2014-05-28T11:55:49.000+0000 |
Updated | 2018-02-26T15:33:47.000+0000 |
Description
Test steps:
1. Create an android module
2. Package it to any mobile app project or titaniumSDK
Actual Result:
Error occurs (edited for clarity):
Executing build.xml...
C:\Users\Global\Documents\Workspace\moduleproject\android\build.xml:37:
Cannot find C:\Program Files (x86)\Appcelerator\Appcelerator Studio\module\android\build.xml imported from
C:\Users\Global\Documents\Workspace\moduleproject\android\build.xml
Attachments
File | Date | Size |
---|---|---|
error.png | 2014-05-28T11:58:45.000+0000 | 106809 |
studio_module_publish_error.log | 2014-06-12T11:11:47.000+0000 | 8426 |
I wonder if this is a path issue. It looks as if it is looking in the wrong place for the Titanium SDK. I had to edit the build.properties file attached to a module for this sort of thing. Do we pass these properties into the build file as part of invoking ANT, or does a user need to edit the build.properties file manually?
Master pull request: https://github.com/appcelerator/titanium_mobile/pull/5785 3_3_X pull request: https://github.com/appcelerator/titanium_mobile/pull/5786
I had the same error as originally reported with sdk: 3.3.0.20140605150555. Now I'm getting the following error with below mentioned environments. I am attaching the studio log file for more information.
*Tested Environment* || *Component* || *Version*|| | Appcelerator Studio | 3.3.0.201406111021 | | Titanium SDK | 3.3.0.v20140611130912 | | ACS | 1.0.14 | | Alloy | 1.4.0-rc | | CLI | 3.3.0-rc | | Titanium-code-processor | 1.1.1 | | Node.JS | v0.10.26 | | OS | Windows 8.1 |
Can you please try executing the build directly from the command line?
Followed the steps provided by [~sdowse]. Now Android packages could be *able to publish* without any issues.
Closing based on my comment, and feedback from [~kvelummaylum].
Reopening to fix sprint.