Fatal Exception at AnroidRuntime after releasing new update











up vote
1
down vote

favorite












After updating for a new release of my app I'm getting this error crash repeatedly on the opening of the app and nothing else. This crash happening after few seconds of the opening of the app.



Error Log:



E/AndroidRuntime: FATAL EXCEPTION: Thread-3
Process: com.company.app, PID: 13304
java.lang.NoSuchMethodError: No direct method <init>(Lorg/apache/http/c/c;Lorg/apache/http/conn/scheme/SchemeRegistry;)V in class Lorg/apache/http/impl/conn/tsccm/ThreadSafeClientConnManager; or its super classes (declaration of 'org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager' appears in /system/framework/org.apache.http.legacy.boot.jar)
at com.a.g.c.c(Unknown Source:54)
at com.a.g.c.a(Unknown Source:4)
at com.a.e.b.a(Unknown Source:0)
at com.a.e.b.b(Unknown Source:23000)
at com.a.d.b.c(Unknown Source:5000)
at com.a.d.b.b(Unknown Source:0)
at com.a.d.b.a(Unknown Source:4000)
at com.a.c.f.a(Unknown Source:12000)
at com.a.c.f$1.run(Unknown Source:4)
at com.a.a.b.b.a(Unknown Source:8)
at com.a.e.a(Unknown Source:51031)
at com.a.e.a(Unknown Source:0)
at com.a.e$4.run(Unknown Source:1000)
at com.a.e.o(Unknown Source:31)
at com.a.e.a(Unknown Source:45000)
at com.a.c.a(Unknown Source:20)
at com.a.c.b(Unknown Source:27000)
at com.a.c$1.run(Unknown Source:7)
at com.a.a.b.c.run(Unknown Source:8)
at com.a.a.b.d.run(Unknown Source:2000)


This error is showing in Logcat not getting on Crashlytics.
What are the main causes of this happening and how to solve this problem?










share|improve this question




























    up vote
    1
    down vote

    favorite












    After updating for a new release of my app I'm getting this error crash repeatedly on the opening of the app and nothing else. This crash happening after few seconds of the opening of the app.



    Error Log:



    E/AndroidRuntime: FATAL EXCEPTION: Thread-3
    Process: com.company.app, PID: 13304
    java.lang.NoSuchMethodError: No direct method <init>(Lorg/apache/http/c/c;Lorg/apache/http/conn/scheme/SchemeRegistry;)V in class Lorg/apache/http/impl/conn/tsccm/ThreadSafeClientConnManager; or its super classes (declaration of 'org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager' appears in /system/framework/org.apache.http.legacy.boot.jar)
    at com.a.g.c.c(Unknown Source:54)
    at com.a.g.c.a(Unknown Source:4)
    at com.a.e.b.a(Unknown Source:0)
    at com.a.e.b.b(Unknown Source:23000)
    at com.a.d.b.c(Unknown Source:5000)
    at com.a.d.b.b(Unknown Source:0)
    at com.a.d.b.a(Unknown Source:4000)
    at com.a.c.f.a(Unknown Source:12000)
    at com.a.c.f$1.run(Unknown Source:4)
    at com.a.a.b.b.a(Unknown Source:8)
    at com.a.e.a(Unknown Source:51031)
    at com.a.e.a(Unknown Source:0)
    at com.a.e$4.run(Unknown Source:1000)
    at com.a.e.o(Unknown Source:31)
    at com.a.e.a(Unknown Source:45000)
    at com.a.c.a(Unknown Source:20)
    at com.a.c.b(Unknown Source:27000)
    at com.a.c$1.run(Unknown Source:7)
    at com.a.a.b.c.run(Unknown Source:8)
    at com.a.a.b.d.run(Unknown Source:2000)


    This error is showing in Logcat not getting on Crashlytics.
    What are the main causes of this happening and how to solve this problem?










    share|improve this question


























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      After updating for a new release of my app I'm getting this error crash repeatedly on the opening of the app and nothing else. This crash happening after few seconds of the opening of the app.



      Error Log:



      E/AndroidRuntime: FATAL EXCEPTION: Thread-3
      Process: com.company.app, PID: 13304
      java.lang.NoSuchMethodError: No direct method <init>(Lorg/apache/http/c/c;Lorg/apache/http/conn/scheme/SchemeRegistry;)V in class Lorg/apache/http/impl/conn/tsccm/ThreadSafeClientConnManager; or its super classes (declaration of 'org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager' appears in /system/framework/org.apache.http.legacy.boot.jar)
      at com.a.g.c.c(Unknown Source:54)
      at com.a.g.c.a(Unknown Source:4)
      at com.a.e.b.a(Unknown Source:0)
      at com.a.e.b.b(Unknown Source:23000)
      at com.a.d.b.c(Unknown Source:5000)
      at com.a.d.b.b(Unknown Source:0)
      at com.a.d.b.a(Unknown Source:4000)
      at com.a.c.f.a(Unknown Source:12000)
      at com.a.c.f$1.run(Unknown Source:4)
      at com.a.a.b.b.a(Unknown Source:8)
      at com.a.e.a(Unknown Source:51031)
      at com.a.e.a(Unknown Source:0)
      at com.a.e$4.run(Unknown Source:1000)
      at com.a.e.o(Unknown Source:31)
      at com.a.e.a(Unknown Source:45000)
      at com.a.c.a(Unknown Source:20)
      at com.a.c.b(Unknown Source:27000)
      at com.a.c$1.run(Unknown Source:7)
      at com.a.a.b.c.run(Unknown Source:8)
      at com.a.a.b.d.run(Unknown Source:2000)


      This error is showing in Logcat not getting on Crashlytics.
      What are the main causes of this happening and how to solve this problem?










      share|improve this question















      After updating for a new release of my app I'm getting this error crash repeatedly on the opening of the app and nothing else. This crash happening after few seconds of the opening of the app.



      Error Log:



      E/AndroidRuntime: FATAL EXCEPTION: Thread-3
      Process: com.company.app, PID: 13304
      java.lang.NoSuchMethodError: No direct method <init>(Lorg/apache/http/c/c;Lorg/apache/http/conn/scheme/SchemeRegistry;)V in class Lorg/apache/http/impl/conn/tsccm/ThreadSafeClientConnManager; or its super classes (declaration of 'org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager' appears in /system/framework/org.apache.http.legacy.boot.jar)
      at com.a.g.c.c(Unknown Source:54)
      at com.a.g.c.a(Unknown Source:4)
      at com.a.e.b.a(Unknown Source:0)
      at com.a.e.b.b(Unknown Source:23000)
      at com.a.d.b.c(Unknown Source:5000)
      at com.a.d.b.b(Unknown Source:0)
      at com.a.d.b.a(Unknown Source:4000)
      at com.a.c.f.a(Unknown Source:12000)
      at com.a.c.f$1.run(Unknown Source:4)
      at com.a.a.b.b.a(Unknown Source:8)
      at com.a.e.a(Unknown Source:51031)
      at com.a.e.a(Unknown Source:0)
      at com.a.e$4.run(Unknown Source:1000)
      at com.a.e.o(Unknown Source:31)
      at com.a.e.a(Unknown Source:45000)
      at com.a.c.a(Unknown Source:20)
      at com.a.c.b(Unknown Source:27000)
      at com.a.c$1.run(Unknown Source:7)
      at com.a.a.b.c.run(Unknown Source:8)
      at com.a.a.b.d.run(Unknown Source:2000)


      This error is showing in Logcat not getting on Crashlytics.
      What are the main causes of this happening and how to solve this problem?







      android obfuscation android-proguard runtimeexception






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 22 at 3:44









      shizhen

      2,4333727




      2,4333727










      asked Nov 22 at 3:33









      sasuke

      3471926




      3471926
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote



          accepted











          What are the main causes of this happening and how to solve this problem?




          This is due to your apache classes are stripped by your proguard obfuscation step. Try to add -keep options for those apache classes. E.g.



          -keep class org.apache.http.** { *; }





          share|improve this answer























          • But this release working in some of many devices and in many crashes frequently
            – sasuke
            Nov 22 at 5:31










          • you can double check if the required class exists in your apk using apkanalyser.
            – shizhen
            Nov 22 at 5:34













          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423496%2ffatal-exception-at-anroidruntime-after-releasing-new-update%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          0
          down vote



          accepted











          What are the main causes of this happening and how to solve this problem?




          This is due to your apache classes are stripped by your proguard obfuscation step. Try to add -keep options for those apache classes. E.g.



          -keep class org.apache.http.** { *; }





          share|improve this answer























          • But this release working in some of many devices and in many crashes frequently
            – sasuke
            Nov 22 at 5:31










          • you can double check if the required class exists in your apk using apkanalyser.
            – shizhen
            Nov 22 at 5:34

















          up vote
          0
          down vote



          accepted











          What are the main causes of this happening and how to solve this problem?




          This is due to your apache classes are stripped by your proguard obfuscation step. Try to add -keep options for those apache classes. E.g.



          -keep class org.apache.http.** { *; }





          share|improve this answer























          • But this release working in some of many devices and in many crashes frequently
            – sasuke
            Nov 22 at 5:31










          • you can double check if the required class exists in your apk using apkanalyser.
            – shizhen
            Nov 22 at 5:34















          up vote
          0
          down vote



          accepted







          up vote
          0
          down vote



          accepted







          What are the main causes of this happening and how to solve this problem?




          This is due to your apache classes are stripped by your proguard obfuscation step. Try to add -keep options for those apache classes. E.g.



          -keep class org.apache.http.** { *; }





          share|improve this answer















          What are the main causes of this happening and how to solve this problem?




          This is due to your apache classes are stripped by your proguard obfuscation step. Try to add -keep options for those apache classes. E.g.



          -keep class org.apache.http.** { *; }






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 23 at 1:21

























          answered Nov 22 at 3:40









          shizhen

          2,4333727




          2,4333727












          • But this release working in some of many devices and in many crashes frequently
            – sasuke
            Nov 22 at 5:31










          • you can double check if the required class exists in your apk using apkanalyser.
            – shizhen
            Nov 22 at 5:34




















          • But this release working in some of many devices and in many crashes frequently
            – sasuke
            Nov 22 at 5:31










          • you can double check if the required class exists in your apk using apkanalyser.
            – shizhen
            Nov 22 at 5:34


















          But this release working in some of many devices and in many crashes frequently
          – sasuke
          Nov 22 at 5:31




          But this release working in some of many devices and in many crashes frequently
          – sasuke
          Nov 22 at 5:31












          you can double check if the required class exists in your apk using apkanalyser.
          – shizhen
          Nov 22 at 5:34






          you can double check if the required class exists in your apk using apkanalyser.
          – shizhen
          Nov 22 at 5:34




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423496%2ffatal-exception-at-anroidruntime-after-releasing-new-update%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Trompette piccolo

          Slow SSRS Report in dynamic grouping and multiple parameters

          Simon Yates (cyclisme)