Gradle sync failed: Unable to start the daemon process with no specific main class defined












0















I'm using android studio 3.2.1 and seeing this error



Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/3.3/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
Error: Could not find or load main class =


This started happening all of a sudden and I don't know what changed and how to fix this?










share|improve this question



























    0















    I'm using android studio 3.2.1 and seeing this error



    Unable to start the daemon process.
    This problem might be caused by incorrect configuration of the daemon.
    For example, an unrecognized jvm option is used.
    Please refer to the user guide chapter on the daemon at https://docs.gradle.org/3.3/userguide/gradle_daemon.html
    Please read the following process output to find out more:
    -----------------------
    Error: Could not find or load main class =


    This started happening all of a sudden and I don't know what changed and how to fix this?










    share|improve this question

























      0












      0








      0








      I'm using android studio 3.2.1 and seeing this error



      Unable to start the daemon process.
      This problem might be caused by incorrect configuration of the daemon.
      For example, an unrecognized jvm option is used.
      Please refer to the user guide chapter on the daemon at https://docs.gradle.org/3.3/userguide/gradle_daemon.html
      Please read the following process output to find out more:
      -----------------------
      Error: Could not find or load main class =


      This started happening all of a sudden and I don't know what changed and how to fix this?










      share|improve this question














      I'm using android studio 3.2.1 and seeing this error



      Unable to start the daemon process.
      This problem might be caused by incorrect configuration of the daemon.
      For example, an unrecognized jvm option is used.
      Please refer to the user guide chapter on the daemon at https://docs.gradle.org/3.3/userguide/gradle_daemon.html
      Please read the following process output to find out more:
      -----------------------
      Error: Could not find or load main class =


      This started happening all of a sudden and I don't know what changed and how to fix this?







      android android-studio gradle android-gradle






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 12 '18 at 23:51









      Jayaprakash MaraJayaprakash Mara

      4818




      4818
























          1 Answer
          1






          active

          oldest

          votes


















          1














          Your issue is related with your jvmargs on your gradle properties file.




          For example, an unrecognized jvm option is used




          You can try the following:




          1. Open your gradle.properties


          2. Add the following:



            org.gradle.jvmargs=-Xmx2048m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8




          (it can be more, depends on your machine memory capacity).




          1. Save the file, reboot project


          —-



          From the documentation:




          org.gradle.jvmargs=(JVM arguments)
          Specifies the JVM arguments used
          for the Gradle Daemon. The setting is particularly useful for
          configuring JVM memory settings for build performance.







          share|improve this answer


























          • Man, you're a savior!

            – Jayaprakash Mara
            Nov 13 '18 at 15:49











          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',
          autoActivateHeartbeat: false,
          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%2f53271778%2fgradle-sync-failed-unable-to-start-the-daemon-process-with-no-specific-main-cla%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









          1














          Your issue is related with your jvmargs on your gradle properties file.




          For example, an unrecognized jvm option is used




          You can try the following:




          1. Open your gradle.properties


          2. Add the following:



            org.gradle.jvmargs=-Xmx2048m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8




          (it can be more, depends on your machine memory capacity).




          1. Save the file, reboot project


          —-



          From the documentation:




          org.gradle.jvmargs=(JVM arguments)
          Specifies the JVM arguments used
          for the Gradle Daemon. The setting is particularly useful for
          configuring JVM memory settings for build performance.







          share|improve this answer


























          • Man, you're a savior!

            – Jayaprakash Mara
            Nov 13 '18 at 15:49
















          1














          Your issue is related with your jvmargs on your gradle properties file.




          For example, an unrecognized jvm option is used




          You can try the following:




          1. Open your gradle.properties


          2. Add the following:



            org.gradle.jvmargs=-Xmx2048m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8




          (it can be more, depends on your machine memory capacity).




          1. Save the file, reboot project


          —-



          From the documentation:




          org.gradle.jvmargs=(JVM arguments)
          Specifies the JVM arguments used
          for the Gradle Daemon. The setting is particularly useful for
          configuring JVM memory settings for build performance.







          share|improve this answer


























          • Man, you're a savior!

            – Jayaprakash Mara
            Nov 13 '18 at 15:49














          1












          1








          1







          Your issue is related with your jvmargs on your gradle properties file.




          For example, an unrecognized jvm option is used




          You can try the following:




          1. Open your gradle.properties


          2. Add the following:



            org.gradle.jvmargs=-Xmx2048m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8




          (it can be more, depends on your machine memory capacity).




          1. Save the file, reboot project


          —-



          From the documentation:




          org.gradle.jvmargs=(JVM arguments)
          Specifies the JVM arguments used
          for the Gradle Daemon. The setting is particularly useful for
          configuring JVM memory settings for build performance.







          share|improve this answer















          Your issue is related with your jvmargs on your gradle properties file.




          For example, an unrecognized jvm option is used




          You can try the following:




          1. Open your gradle.properties


          2. Add the following:



            org.gradle.jvmargs=-Xmx2048m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8




          (it can be more, depends on your machine memory capacity).




          1. Save the file, reboot project


          —-



          From the documentation:




          org.gradle.jvmargs=(JVM arguments)
          Specifies the JVM arguments used
          for the Gradle Daemon. The setting is particularly useful for
          configuring JVM memory settings for build performance.








          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 13 '18 at 0:13

























          answered Nov 13 '18 at 0:08









          André SousaAndré Sousa

          1,1481818




          1,1481818













          • Man, you're a savior!

            – Jayaprakash Mara
            Nov 13 '18 at 15:49



















          • Man, you're a savior!

            – Jayaprakash Mara
            Nov 13 '18 at 15:49

















          Man, you're a savior!

          – Jayaprakash Mara
          Nov 13 '18 at 15:49





          Man, you're a savior!

          – Jayaprakash Mara
          Nov 13 '18 at 15:49


















          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53271778%2fgradle-sync-failed-unable-to-start-the-daemon-process-with-no-specific-main-cla%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

          Florida Star v. B. J. F.

          Error while running script in elastic search , gateway timeout

          Adding quotations to stringified JSON object values