[TIMOB-23787] Android: Can't add android modules to project when using SDK 6.0.0.v20160817065403
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2016-09-28T07:04:05.000+0000 |
Affected Version/s | Release 6.0.0 |
Fix Version/s | Release 6.0.0 |
Components | Android |
Labels | qe-4.7.0, regression |
Reporter | Lokesh Choudhary |
Assignee | Gary Mathews |
Created | 2016-08-18T00:39:20.000+0000 |
Updated | 2016-10-10T20:49:52.000+0000 |
Description
*This is a regression. Not seen with SDK 5.4.0.GA*
Steps to reproduce:
1. Create an android project using studio. 2. Enable services/hyperloop. 3. After the app is created add e.g ti.map module. 3. Look at the modules section in the tiapp.xml.Actual results:
1. The android modules versions are greyed out. 2. If you hover over soasta module version number for android you get message:The com.soasta.touchtest module does not support android platform for 6.0.0.xx....
2. If you try to add modules e.g the ti.map module you don't get an option for android modules.
*NOTE:* Attached screenshots for reference.
Expected Results:
1. You should be able to add android modules to your project & select the module version. Also, you should not getThe com.soasta.touchtest module does not support android platform for 6.0.0.xx....
message.
Attachments
File | Date | Size |
---|---|---|
Screen Shot 2016-08-17 at 5.18.52 PM.png | 2016-08-18T00:36:30.000+0000 | 117176 |
Screen Shot 2016-08-17 at 5.19.22 PM.png | 2016-08-18T00:36:34.000+0000 | 31086 |
Screen Shot 2016-08-17 at 5.19.36 PM.png | 2016-08-18T00:36:39.000+0000 | 65061 |
Screen Shot 2016-08-17 at 5.31.32 PM.png | 2016-08-18T00:36:42.000+0000 | 43386 |
Screen Shot 2016-08-22 at 2.55.15 PM.png | 2016-08-22T21:58:26.000+0000 | 42920 |
Screen Shot 2016-10-06 at 11.05.02 AM.png | 2016-10-06T18:11:21.000+0000 | 41167 |
[~msamah] Have we packaged and put the recompiled modules into master? And probably indicate here which version of ti.map supports which version of titanium SDK. [~lchoudhary] Can you put expected results? I thought SOASTA was a plugin, and there shouldn't be any need to recompile it for Android v8. [~kkolipaka] what are the conditions that Studio check for to give the message
modules does not support version ...
[~cng] [~msamah] - We need to update
com.soasta.touchtest
version module to3
to avoid this error with SDK 6.0As Kondal mentioned, all modules in Android TiSDK 6 now needs to be recompiled by bumping their version from
2
to3
to be detected.This is related to TIMOB-23649
I think a large majority of the modules have been recompiled with TiSDK 6 and had the apiversion bumped to 3. This is basically a continuation of TIMOB-19794. [~lchoudhary] Can you try the modules in TIMOB-19794? They have been recompiled for TiSDK 6.0.0+ Also, is there a place/repo to recompile that touchtest module? It needs to be recompiled with TiSDK 6.0.0 and bumped apiversion to 3. CC: [~cwilliams] fyi.
We probably need to double check the packaged modules in Timob have been updated to the newer modules too for Android in the 6_0_X and master branch.
A little surprised we need to do anything with TouchTest, but I'd start by asking [~scottd]
[~lchoudhary] which version are u using for those modules? You would need to use these versions: https://github.com/appcelerator/hyperloop.next/releases/tag/2.0.0 https://github.com/appcelerator-modules/appcelerator.aca/releases/tag/2.0.0 Modules that are recompiled and have their manifest updated to apiversion 3: https://github.com/appcelerator/hyperloop.next/blob/master/android/manifest#L6
[~msamah], I am using the ones which come with the SDK 6.0.0. If you see in one of my latest screenshot they are ver 2.0.0. Are these wrong ones ? I double checked & the modules have manifest updated to apiversion 3.
That is very strange.
[~lchoudhary] - Issue might fall into one of these.
You need Studio 4.8.0 to detect
apiversion: 3
. Any earlier studio version can't detect the module with version3
Probably you would have not restarted the studio after installing the new modules.
[~kkolipaka], I was not using studio 4.8.0 but 4.7.1. Let me try with studio 4.8.0. [~cng], Let me try that.
[~kkolipaka],[~cng], With studio 4.8.0 this works fine I can add android modules. FYI, the touch test module is still ver 1.0 & is greyed out in the tiapp.xml for android.
Touch module requires to be recompiled. -Which I believe is in another Jira Ticket.- Can this issue be resolved?
Also, did you try with this module? https://drive.google.com/file/d/0B5kns9m6-03wZTdFNVFZSGxoSEk/view
[~cng] Module in https://drive.google.com/file/d/0B5kns9m6-03wZTdFNVFZSGxoSEk/view does not work for TiSDK 6+. Only if you extract/unzip it and add the exact version, does it appear. Update: I did the wrong method of using this.
So for testing purpose, to check that downloaded file work, I replaced
com.soasta.touchtest-android-1.0.zip
withcom.soasta.touchtest-android-2.0.zip
in the folder for latest version. It worked correctly to install it in a newly created app. Only thing is that the tiapp.xml seems to be hardcoded to refer to version1.0
.[~fmiao] can you indicate to me where in any of our cli (I am guessing appc-cli-titanium) do we hardcode the version to 1.0? Now we are seeing in tiapp.xml,
<module platform="android" version="1.0">com.soasta.touchtest</module>
we need to change that somewhere.[~cng]. Nope,
appc-cli-titanium
doesn't hardcode the version 1.0 for soasta. You'll need to look into the jar that's run when enabling test, i.e.../Titanium/plugins/com.appcelerator.test/versions/8244.293/MakeAppTouchTestable/MakeAppTouchTestable.jar
.[~ingo][~emerriman] So we tried to just edit and recompile the module ourselves, but now we are stuck because there's something that needs to be changed in
MakeAppTouchTestable.jar
file that I have no idea where it's built from, so we might just have to get in touch with SOASTA. Any ideas how we can approach this?The ZIP is being handled in this ticket APPTS-8874
[~gmathews] ^
make_app_touch_testable: https://github.com/appcelerator/make_app_touch_testable/pull/1
Verified the fix. Android modules can now be added successfully. Closing. Environment: Appc Studio : 4.8.0.201609292239 Ti SDK : 6.0.0.v20161007121506 Ti CLI : 5.0.10 Alloy : 1.9.2 MAC El Capitan : 10.11.6 Appc NPM : 4.2.8-7 Appc CLI : 6.0.0-57 Node: 4.6.0 Nexus 6 - Android 6.0.1