Develop Reference

How can I fix the "Cannot parse result path string:" error in android studio version 3.6.2 on running the application?

I am trying to run/debug the application in android studio version 3.6.2 but returning an error saying Cannot parse result path string:
Build output box shows:
Build failed:
Cannot parse result path string:

The problem is with the gradle version
I simply had to switch from version 6.5 to 6.5.1 and after rebuilding it worked just fine.
If you are on windows go File -> Project Structure, on project change the gradle version.

The problem might be the gradle version. Using a gradle version above 6.5 should fix the problem to allow the build to complete. If the problem persists, I would suggest reinstalling android studio with updated gradle version.
To change gradle version: Navigate to file-> project structure and access the dropdown menu besides gradle.

Go to gradle project >>update dependencies classpath .
Thats all

This seems to be a issue with gradle cache. Try below methods
Method1: Try invalidate cahce/restart option from menu.
Method2: Clear the gradle cache manually by deleting "cache" folder from the below location "C:\Users\USER_NAME.gradle\caches"

Android Studio - Unsupported Modules Detected - Unfortunately you can't have non-Gradle Java modules and Android-Gradle modules in one project

Related to Error: Unfortunately you can't have non-Gradle Java modules and > Android-Gradle modules in one project
I upgraded gradle from version 3.5.3 to 3.6.2 today in my Android Java project, and now I get this error:
Unsupported Modules Detected
Compilation is not supported for following modules: NameOfMyApp, app. Unfortunately you can't have non-Gradle Java modules and Android-Gradle modules in one project.
Unfortunately, I tried every solution in the linked question, but nothing worked. I still get this error. It seems like my project compiles and works just fine though. However, this error is annoying... continually popping up.
Anyone know how to fix it? I only started having this issue since the upgrade of Android Studio, gradle, and other updates recently pushed out.

Follow these steps one by one to solve the error.
Close the Project
Exit Android Studio
Then go to your application folder and delete .iml file
And also delete .idea Folder
Then open Android studio again and import your project
Note- If .iml and .idea files are not visible then press Command, shift and > buttons together when you are inside your Application folder

Eclipse Neon for Eclipse Committers can't resolve org.eclipse

I recently upgraded to Eclipse Neon. I had a plugin project that built fine in Eclipse Luna, but now in neon, everywhere that I imported "org.eclipse."something I get an error:
The import org.eclipse cannot be resolved.
The plugin.xml has errors etc.
The Project build path has "Plugin Dependencies" on the build path.
My version of Eclipse is
Eclipse IDE for Eclipse Committers
Version: Neon.3 Release (4.6.3)
Build id: 20170314-1500
I'm running on MacOSX High Sierra.
It's probably something very simple.

I have a similar problem every time I upgrade my eclipse installation.
For me the problem can be solved by adjusting the Target platform (can be found in the settings - just search for it) to match the currently running one. For that in most cases I simply add a target platform with default configuration and set that one active.
After a rebuild (normally performed automatically) all those errors are gone.

IntelliJ Gradle Could not Determine Java Version

I'm using IntelliJ to work with a Gradle project. I noticed that whenever I try to refresh the Gradle project (or when trying to import/re-import a project as a Gradle project) I get the following error:
Error: Could not determine the Java version
$JAVA_HOME is set, the SDK is set to Java 8 (and gradle -version confirms it is also is set to Java 8), and the project builds fine from the command line. Restarting IntelliJ also does nothing. I also deleted the project specific and global .gradle folders, which did not resolve the issue.
I am running IntelliJ 14.1.4 on Ubuntu 15.04 and Gradle 2.5.
EDIT: Tried it on a different machine (also Ubuntu 15.04, Oracle Java 8) running IntelliJ 14.1.1 and it worked correctly.

I had this problem too. It seems it was linked to the project being setup with a rather old gradle build. Changing distributionUrl to a new distribution in /gradle//wrapper/gradle-wrapper.properties solved it

You should try to switch Idea boot jdk. It works for me.

Can't run imported gradle android project in Eclipse

First, im new in gradle so please bear with me.
I successfully build and imported this project with gradle & eclipse on ubuntu 13.10. This is what i did :
run gradle build in terminal (success)
add apply plugin: 'eclipse' in the build.gradle
run gradle eclipse in terminal (success)
import it as existing project on eclipse
The problem is, when i tried to run the project, eclipse read it as "normal" java program, not the android one. This is the SS :
The main project in my workspace is not in eclipse format.
And this is its properties :
Notice there's no android tab in it's properties. And i cant run it as android application.
Am i missing something? Please kindly help me.
Thanks for your help.

Usually to develop Android in Eclipse you need to install ADT into Eclipse or start with ADT-Bundle (Android IDE) from Google. (You have not as Preferences missing Android group)
However ADT does not have gradle support. And Android Studio is still not even yet beta (preview or alpha, bleeding edge, need to update with almost every build).
There is Nodeclipse/Enide Gradle for Eclipse
(marketplace), that lets launch gradle build even on general project.
For the latest build.gradle template for classic Android project check
gh.c/N/n-1/b/m/o.n.e.e.g/docs/android/build.gradle.
This lets create new Android project in Eclipse with ADT and use ADT tools for most of things,
but additionally have newer build with gradle
and execute defined gradle tasks
But for Android project with several modules (as in this case) you would need to DIY do it yourself:
try to configure Eclipse .classpath to correct values, as gradle eclipse task won't yet do it all for you.

Eclipse plugin in Gradle that you have used does not support Android projects - they are significantly different from regular Java projects. Some things can work but there will be a lot of things missing including Android nature for generated projects.
And the ADT plugin provided by Google does not support Gradle projects yet as the team focuses on Android Studio first. http://tools.android.com/tech-docs/new-build-system can give you some ideas about the current state.