GitHub Issue | n/a |
Type | Bug |
Priority | n/a |
Status | Closed |
Resolution | Needs more info |
Resolution Date | 2015-07-03T23:43:11.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | Titanium SDK & CLI |
Labels | TCSupportTriage, android, studio3 |
Reporter | Bikash |
Assignee | Radamantis Torres-Lechuga |
Created | 2015-02-03T14:20:15.000+0000 |
Updated | 2016-03-08T07:36:59.000+0000 |
[INFO] : Found Titanium module id=ti.admob version=1.0 platform=android deploy-type=test path=C:\Users\Bikash\Documents\Titanium_Studio_Workspace\ReviewJournal\modules\android\ti.admob\1.0
[ERROR] Application Installer abnormal process termination. Process exit value was 1
-------------------------------
I have also tested with ti.admob v2.1.2, but it creates the same issue.
If i will remove the ti.cloudpush module from the tiapp.xml file, then it is working else it throws the same error while testing using titanium stdio-> device run.
Hello We have tested the issue, We have overcome the issue with a workaround.
TESTING ENVIRONMENT
CLI version 3.4.1, Titanium SDK version 3.5.0.GA Android DeviceOBSERVATION AND WORKAROUND
Using "ti.cloudpush" and "ti.admob" together in a project causes the below error.Here we have use the ti.admob (version 2.1.2) and ti.cloudpush (version 3.3.4). Here the error message is telling us that the "google-play-services.jar" file for the two modules are different. Also, recommending solution by either "choosing a version combination for the modules where the "google-play-services.jar" file are same" or copying the "google-play-services.jar" file from one module and replacing the "google-play-services.jar" file of other module with that. We have tried this process by copying "google-play-services.jar" file of ti.cloudpush (version 3.3.4) module's lib folder and put it in ti.admob (version 2.1.2) modules lib folder by replacing it's own "google-play-services.jar" file. Now it's working and project runs smoothly. Hope this workaround helps. Thanks.
[~bikashkumar.sundaray] pleae try the suggested workaround and let us know if that works for you