[TIMOB-13313] Android: Module does not pick android-platform-11 android JAR and thus android.animate method does not work
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2016-08-29T19:54:25.000+0000 |
| Affected Version/s | Release 3.0.2, Release 3.1.0 |
| Fix Version/s | n/a |
| Components | Android |
| Labels | Titanium, android, exalture, module |
| Reporter | Ashish Nigam |
| Assignee | Ashraf Abu |
| Created | 2013-04-02T11:58:46.000+0000 |
| Updated | 2017-03-20T21:38:09.000+0000 |
Description
I tried using android-platform-11 Android JAR in module but it gives the following error message and does not run when try ant run or from eclipse.
Note: Build Path is configured properly.
**build.properties**
titanium.sdk=/Users/ashish.nigam/Library/Application Support/Titanium
titanium.os=osx
titanium.version=3.0.2.GA
android.sdk=/Applications/adt-bundle-mac/sdk
android.ndk=/Applications/android-ndk
titanium.platform=${titanium.sdk}/mobilesdk/${titanium.os}/${titanium.version}/android
android.platform=/Applications/adt-bundle-mac/sdk/platforms/android-11
google.apis=${android.sdk}/add-ons/addon-google_apis_google-11
[exec] [TRACE] Writing out AndroidManifest.xml
[exec] [DEBUG] /Applications/adt-bundle-mac/sdk/platform-tools/aapt package -m -J /var/folders/1y/_qvllvdj12bchp6yllkp5cp87s_zff/T/malL3fwti/nappmupdf/build/android/gen -M /var/folders/1y/_qvllvdj12bchp6yllkp5cp87s_zff/T/malL3fwti/nappmupdf/build/android/AndroidManifest.xml -S /var/folders/1y/_qvllvdj12bchp6yllkp5cp87s_zff/T/malL3fwti/nappmupdf/build/android/res -I /Applications/adt-bundle-mac/sdk/platforms/android-8/android.jar
[exec] [ERROR] /var/folders/1y/_qvllvdj12bchp6yllkp5cp87s_zff/T/malL3fwti/nappmupdf/build/android/res/animator/info.xml:2: error: No resource identifier found for attribute 'ordering' in package 'android'
[exec] [ERROR] /var/folders/1y/_qvllvdj12bchp6yllkp5cp87s_zff/T/malL3fwti/nappmupdf/build/android/res/animator/info.xml:5: error: No resource identifier found for attribute 'propertyName' in package 'android'
[exec] [ERROR] /var/folders/1y/_qvllvdj12bchp6yllkp5cp87s_zff/T/malL3fwti/nappmupdf/build/android/res/animator/info.xml:5: error: No resource identifier found for attribute 'valueFrom' in package 'android'
[exec] [ERROR] /var/folders/1y/_qvllvdj12bchp6yllkp5cp87s_zff/T/malL3fwti/nappmupdf/build/android/res/animator/info.xml:5: error: No resource identifier found for attribute 'valueTo' in package 'android'
[exec] [ERROR] /var/folders/1y/_qvllvdj12bchp6yllkp5cp87s_zff/T/malL3fwti/nappmupdf/build/android/res/animator/info.xml:11: error: No resource identifier found for attribute 'propertyName' in package 'android'
[exec] [ERROR] /var/folders/1y/_qvllvdj12bchp6yllkp5cp87s_zff/T/malL3fwti/nappmupdf/build/android/res/animator/info.xml:11: error: No resource identifier found for attribute 'valueTo' in package 'android'
[exec] [ERROR] /var/folders/1y/_qvllvdj12bchp6yllkp5cp87s_zff/T/malL3fwti/nappmupdf/build/android/res/animator/info.xml:16: error: No resource identifier found for attribute 'propertyName' in package 'android'
[exec] [ERROR] /var/folders/1y/_qvllvdj12bchp6yllkp5cp87s_zff/T/malL3fwti/nappmupdf/build/android/res/animator/info.xml:16: error: No resource identifier found for attribute 'valueTo' in package 'android'
[exec] [ERROR] Error generating R.java from manifest
[exec] [ERROR] Build Failed.
any news here? I just need a hotfix for the build.xml script.
Hi Mads/Ashish, Could you please provide a sample module and steps to reproduce this issue? I've tried creating a new module, and modifying the build.properties to API 11 and I don't run into this error. This seems to be related to the android manifest generation, so I tried inserting a node into the timodule.xml file with no luck reproducing this. Thanks
Hi Allen, its this ticket: http://support.appcelerator.com/tickets/APP-737468/tickets and here is my module: https://dl.dropbox.com/u/2132088/NappMuPDF.zip
[~viezel] I tried that module that it built fine for me. Do you have reproduction steps on when it 'fails' for you? Was it during runtime or when you build the app or when you build the module?
Hi Allen, It also builds fine, if I do "ant dist". But if I do "ant run" to get it to create an example project for the emulator. then the above console log happens. It will complain that android-8 does not have the animator framework, and its properties. Which is correct. But my build.properties, I use android-11. So somewhere in the build process in create the example app for the emulator / or device - its uses the android-8 rather than what I specify in the projects build.properties. Are you following me? Cheers, Mads
Hi Allen, sorry for bugging you, but im going crazy with the workflow of copying the zip to a new project, clean the project, build to device. turnaround time is about 3-4 min. Any quick fix solution for this?
This is a bug that we will properly fix in 3.2.0 during the rewrite of the android build command. For now you can work around this issue by doing the following: 1. Go to the sdk directory that your module is using. For me it was something like: /Library/Application Support/Titanium/mobilesdk/osx/3.2.0 2. Open /Library/Application Support/Titanium/mobilesdk/osx/3.2.0/all/tiapp.xml (this is the template tiapp.xml that we use when a new project is generated) 3. Change the android node to something like
4. Then go back to your project and do 'ant run' The reason why this is happening is because the 'ant run' command actually creates a new project into a temp directory and then run that. The api level is read from the tiapp.xml and not your build.properties.Hi Allen, Thanks for the quick fix. It works! But then a new issue arrises :) using ant run or ant install will clear the libs folder. My module uses c libraries, which I place in the libs folder. Where can I place them, so they are copied into the libs folder when compiled? Cheers, Mads.
'libs' is a folder where we place the generated libraries. I would try placing it in 'lib' instead and see if that works for you.
I have no idea exactly how to classify this. Allen states this was going to be fixed in the new Android build which shipped with Titanium SDK 3.2.0. On the other hand, the Ant build for Titanium modules was replaced in Titanium SDK 4.0.0.
Closing ticket as invalid.