[TIMOB-15710] Android: Module Packaging - Titanium fails to package android module project
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | High |
|---|
| Status | Closed |
|---|
| Resolution | Invalid |
|---|
| Resolution Date | 2013-12-03T22:39:01.000+0000 |
|---|
| Affected Version/s | Release 3.1.3 |
|---|
| Fix Version/s | n/a |
|---|
| Components | Android |
|---|
| Labels | Mavericks, qe-3.1.3 |
|---|
| Reporter | Samuel Dowse |
|---|
| Assignee | Allen Yeung |
|---|
| Created | 2013-10-09T00:07:43.000+0000 |
|---|
| Updated | 2017-03-23T21:30:08.000+0000 |
|---|
Description
Description
Packaging an android product to the titanium SDK directory, into an already created module or to a specified location does not work.
Packaging claims to have finished in the console, but an alert will be shown saying that the packaging was unsuccessful.
Steps To Reproduce
1. Open Studio
2. Create an android mobile module project
3. Package the project to the Titanium SDK
Result
Opened an alert:
{quote}Launching build and packaging failed.
Reason:
Could not move: /Users/tester/Documents/Titanium_Studio_Workspace/android/dist/com.appcelerator.android-android-1.0.zip.{quote}
Expected Result
Project should have packaged successfully into the titanium sdk folder.
Attachments
Verified this issue with : Appcelerator Studio, build: 3.1.3.201309132456 Titanium SDK: 3.1.3.GA Xcode: 5.0 OS X:10.9 ├── acs@1.0.7 ├── alloy@1.2.2 ├── npm@1.3.2 ├── titanium@3.1.2 └── titanium-code-processor@1.0.3 I am successfully able to create an android module and package it to Titanium SDK. I didn't see "launching build and packaging failed" error.
UNABLE to reproduce this scenario using: Titanium Studio, build: 3.1.4.201310100151 Titanium SDK: 3.1.3.GA Mavericks 10.9 Xcode 5.0.1 ├── acs@1.0.7 ├── alloy@1.2.2 ├── npm@1.3.2 ├── titanium@3.1.2 └── titanium-code-processor@1.0.3 Android module packages successfully to Titanium SDK.
[~sdowse] Could you try the same scenario with CLI 3.1.2? This looks to be an issue with CLI for Android in 3.2.0, if we could isolate it works with 3.1.2 but not the latest 3.2.0.
+Error still occurs+ Mac OSX 10.9 Mavericks Titanium Studio, build: 3.1.4.201310100151 Titanium SDK: 3.1.3.GA CLI: 3.1.2 Alloy: 1.2.2
Hi Samuel, could you attach the Studio log file (Help > Studio > View Log File) when this occurs? Thanks.
The package launch shortcut fails to launch the delegate after the changes to global toolbar. Pushed changes to development to launch the corresponding delegate for packaging Android module.
Hi everybody, I've got exactly the same issue on : Win8 Titanium Studio, build: 3.1.3.201309132423 Titanium SDK: 3.1.3.GA CLI: 3.1.2 Here is the log file : !ENTRY com.appcelerator.titanium.mobile 4 0 2013-11-09 02:11:39.278 !MESSAGE (Build 3.1.3.201309132423) [ERROR] Could not move: C:\Users\Marvin\Documents\Titanium_Studio_Workspace\hostfinder\dist\com.marvin.hostf-android-1.0.zip. !STACK 1 org.eclipse.core.runtime.CoreException: Could not move: C:\Users\Marvin\Documents\Titanium_Studio_Workspace\hostfinder\dist\com.marvin.hostf-android-1.0.zip. at org.eclipse.core.internal.filesystem.Policy.error(Policy.java:55) at org.eclipse.core.filesystem.provider.FileStore.move(FileStore.java:415) at org.eclipse.core.internal.filesystem.local.LocalFile.move(LocalFile.java:352) at com.appcelerator.titanium.mobile.module.launching.ModulePackagerUtil.processModule(ModulePackagerUtil.java:107) at com.appcelerator.titanium.mobile.ui.module.launch.AndroidModulePackageLaunchConfigurationDelegate.distribute(AndroidModulePackageLaunchConfigurationDelegate.java:141) at com.appcelerator.titanium.mobile.ui.module.launch.AndroidModulePackageLaunchConfigurationDelegate.access$0(AndroidModulePackageLaunchConfigurationDelegate.java:114) at com.appcelerator.titanium.mobile.ui.module.launch.AndroidModulePackageLaunchConfigurationDelegate$PackagingProcess$1.run(AndroidModulePackageLaunchConfigurationDelegate.java:230) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: org.eclipse.core.runtime.CoreException: File not found: C:\Users\Marvin\Documents\Titanium_Studio_Workspace\hostfinder\dist\com.marvin.hostf-android-1.0.zip. at org.eclipse.core.internal.filesystem.Policy.error(Policy.java:55) at org.eclipse.core.internal.filesystem.local.LocalFile.openInputStream(LocalFile.java:371) at org.eclipse.core.filesystem.provider.FileStore.copyFile(FileStore.java:220) at org.eclipse.core.filesystem.provider.FileStore.copy(FileStore.java:143) at org.eclipse.core.internal.filesystem.local.LocalFile.copy(LocalFile.java:111) at org.eclipse.core.filesystem.provider.FileStore.move(FileStore.java:410) ... 6 more Caused by: java.io.FileNotFoundException: C:\Users\Marvin\Documents\Titanium_Studio_Workspace\hostfinder\dist\com.marvin.hostf-android-1.0.zip (Le chemin d’accès spécifié est introuvable) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.
The reported error is due to the package file not being generated from the CLI package command., and we are incorrectly attempting to move the non-existent file. I have pushed changes to consider this condition (and additional changes for 3.2.0 build to allow packaging android module app) and show the appropriate error. However, since I'm unable to reproduce the scenario with CLI 3.1.2 and SDK 3.1.3 GA, can you provide the console output after the android app is packaged ? If there are any failures in the console output while packaging the Android app, that should attribute to the reason why the package file for the app is not generated.
+There are two attached log files:+ log.txt is the studio 3.1.3 output moduleLog.txt is the studio 3.2.0 output The screenshot attached shows the entire console output that is given.
[~sdowse] I am specially interested in the console output rather than Studio log file. After you run packaging for Android module, there will be output in the console view indicating about executing the build.xml file and any success messages or errors while packaging the Android module. Since they may not necessarily be captured in the Studio log file, I'm interested to see whether there are any errors from the underlying CLI while packaging the module.
+Console Log:+ Executing build.xml... Distributing the module to the selected output location... Module packaging completed.
Consol Log, display exactly the same for me :/
Sam attached the console output (Output.txt) when running build.xml directly since it provides more info. [~marvin07ro] Could you try the following: 1. Right-click on the build.xml file under project and select Run As > Ant Build...; 2. Select Properties tab and uncheck the option "Use global properties..."; 3. Click on "Add Properties..." and put "android.ndk" for the name and your Android NDK location for the value; 4. Hit "Run". Attaching the resulted output here will be very helpful. Thanks.
!http://www.zimage.fr/images/169207Screen-Tita.png! here is what happened when I try the following : 1. Right-click on the build.xml file under project and select Run As > Ant Build...; 2. Select Properties tab and uncheck the option "Use global properties..."; 3. Click on "Add Properties..." and put "android.ndk" for the name and your Android NDK location for the value; 4. Hit "Run". and the log: !ENTRY org.eclipse.core.variables 4 120 2013-11-13 21:47:50.190 !MESSAGE Reference to undefined variable INSTALLED_PATH I had the same error before that, I guess I have to add INSTALLED_PATH to my path, but I don't know what value to give, plus I don't find anything on the internet.
[~sdowse] which version of the android ndk are you using?
Resolving as invalid. It turns out that there was a space in the NDK path and the Android NDK doesn't work well with this during a module build. I've created two separate features and related it to this ticket to improve the experience.
Closing ticket as invalid.