Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-26898] Android: Build error "Failed to run dexer" can occur when including several libraries

GitHub Issuen/a
TypeBug
PriorityCritical
StatusClosed
ResolutionFixed
Resolution Date2019-07-16T22:48:13.000+0000
Affected Version/sn/a
Fix Version/sRelease 7.5.2
ComponentsAndroid
Labelsandroid, build, cli, dexer, java
ReporterArbind
AssigneeGary Mathews
Created2019-03-06T04:06:05.000+0000
Updated2019-07-16T22:48:16.000+0000

Description

With the recent update, android compilation gets stuck at the "Running dexer" step. This happens when I add the cloudpush module to the project. To reproduce the error, you can simply create a blank project (alloy), add the cloudpush module for android, and try to compile the app for Android.

Attachments

FileDateSize
appc-logs.txt2019-03-06T11:27:55.000+000038763
appc-logs-dexer.txt2019-03-09T00:49:57.000+000038794

Comments

  1. Rakhi Mitro 2019-03-06

    Hello, Thanks for reporting this. Which SDK are you using? It would be great if you can share complete console logs or screenshot which displays the issue.
  2. Arbind 2019-03-06

    It happens with both, 7.5.1GA as well as 7.5.2 RC. Here are the logs.
  3. Sharif AbuDarda 2019-03-06

    Hello [~mr.arbindbhagat], There seems to be an issue with cloudpush module with SDK 7.5.1.GA and onward. I tried to test a sample app (classic) with the module enabled with SDK 7.5.1.GA. The first issue I encounter was
       [ERROR] Conflicting jar files detected:
       [ERROR]   
       [ERROR] The following modules have different "cloudpush.jar" files
       [ERROR]    ti.cloudpush   (version 6.0.0) (hash=50e8dfdde7c5dd4feb4557c03ba305fc)
       [ERROR]    ti.cloudpush   (version 6.0.0) (hash=818fe6b00dcd4fa6f53bbeae31a63504)
       [ERROR]   
       [ERROR] You can either select a version of these modules where the conflicting jar file is the same or you
       [ERROR] can try copying the jar file from one module's "lib" folder to the other module's "lib" folder.
       
    So, I changed the module version to 5.2.0 and this time the console hangs on running dexer. The process never finishes and my processor seems to work a lot in the back. [~rmitro], Can you try to reproduce the behavior? After that, we can move it to engineering. Thanks.
  4. Arbind 2019-03-06

    Yes, you are right. That was the main/initial issue. And Appcelerator released 7.5.2 RC ( https://www.appcelerator.com/blog/2019/03/rc-release-titanium-sdk-7-5-2/ ) saying that it would fix the cloudpush issue. But it has not fixed it. And yes, I can reproduce the issue that you mentioned above.
  5. Gary Mathews 2019-03-09

    [~rmitro] Please use 7.5.2 which contains ti.cloudpush-6.0.1
       appc ti sdk install -b 7_5_X -d
       
    [~mr.arbindbhagat] Make sure your application is using ti.cloudpush-6.0.1. Could you also provide a build log?
  6. Arbind 2019-03-09

    Hi Gary, Yes, I did try with 7.5.2 using ti.cloudpush-6.0.1 , but that didn't help. It gets stuck for more than 30 minutes at the step of "Running Dexer" . Attached is the logs. [^appc-logs-dexer.txt]
  7. Sharif AbuDarda 2019-03-09

    Hello [~gmathews], I tried with the SDK 7.5.2.v20190306131103 with ti.cloudpush-6.0.1 selected in tiapp.xml. The app stuck before running dexer. I have the same log as [~mr.arbindbhagat]. This seems to be a valid issue with ti.cloudpush module. Thanks.
  8. Gary Mathews 2019-03-11

    [~mr.arbindbhagat] [~sdarda] What version of Java are you using?
  9. Sharif AbuDarda 2019-03-11

    Hello, It's 1.8.0, I am on Mac OS
       java version "1.8.0_131"
       Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
       Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
       
  10. Arbind 2019-03-11

    Hi, I am on Mac OS and my java is 1.8.0.
        java version "1.8.0_201"
        Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
        Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
        
  11. Gary Mathews 2019-03-11

    [~shossain][~mr.arbindbhagat] We're having a hard time reproducing this issue on our machines, could you try a couple of things? 1. Try using an older version of ti.playservices in your tiapp.xml
        <module platform="android" version="11.0.40">ti.playservices</module>
        
    2. Remove the ti.playservices module entry from your tiapp.xml and use a lower version of ti.cloudpush
        <module platform="android" version="5.2.0">ti.cloudpush</module>
        
    Could you note the outcome of those two changes?
  12. Arbind 2019-03-11

    Gary, I tried to compile without including ti.playservices module, and it failed. I tried to compile by including the ti.playservices latest version module, and it failed. I tried to compile with ti.playservices 11.0.40 version module, and it worked. (1) So, does it mean that, there is an issue with the latest version of ti.playservices module? (2) Why am I required to include the ti.playservices module even if I don't use it?
  13. Sharif AbuDarda 2019-03-12

    Hello [~gmathews], [~mr.arbindbhagat], Here is my observation. 1. I tried with
        <module platform="android" version="11.0.40">ti.playservices</module> 
        <module platform="android" version="6.0.1">ti.cloudpush</module>
        
    set in the tiapp.xml and I run with trace log. The project builds and run fine in 2min 10s in the emulator. 2. Then, I run the project with only
        <module platform="android" version="6.0.1">ti.cloudpush</module> 
        
    set in the tiapp.xml and I see the ti.playservices module version=16.1.2 is used by default. Now, the project did finish building and run after 3min 15s. 3. Then, I clean the project "appc ti clean" and try to run again. Now I see the log stuck after running dexer for over 30 minutes. So, ti.playservices=11.0.40 module version works fine with the latest ti.cloudpush version=6.0.1(latest). Also, ti.playservices module version=16.1.2 works fine with ti.cloudpush version=5.2.0. The issue seems to be with ti.playservices module version=16.1.2 with ti.cloudpush version=6.0.1(latest). Thanks.
  14. Gary Mathews 2019-03-13

    master: https://github.com/appcelerator/titanium_mobile/pull/10774 8_0_X: https://github.com/appcelerator/titanium_mobile/pull/10775 7_5_X: https://github.com/appcelerator/titanium_mobile/pull/10776
  15. Lokesh Choudhary 2019-03-14

    Verified the fix in SDK 8.0.0.v20190313105932. Closing.
  16. Arbind 2019-03-14

    Can you please build it for 7.5.x as well so that I could install through the appc install command? I don't see it here http://builds.appcelerator.com/#7_5_X , and hence I am not able to install this fix.
  17. Lokesh Choudhary 2019-03-15

    [~mr.arbindbhagat], If you have appc CLI installed you can get the latest from CI by running appc ti sdk install -b 7_5_X.

JSON Source