I have installed Android Studio Canary 2020.3.1.22 and trying to run Flutter project on Apple Silicon(ARM) Mac. Unfortunately, it is giving me this error when I try to run default flutter counter app.
Here is the error I am getting:
Could not open settings generic class cache for settings file '/Users/khamidjonkhamidov/StudioProjects/dummy/android/settings.gradle' (/Users/khamidjonkhamidov/.gradle/caches/6.7/scripts/f0emg6u6oecmxqzgk5g9nn4ui).
> BUG! exception in phase 'semantic analysis' in source unit '_BuildScript_' Unsupported class file major version 61
Gradle version: 6.7 but I tried 7+
JDK version 17
I would really appreciate your help)
According to the official grade docs: Java 17 and later versions are not yet supported.
You can check compatibility here.
So I have installed Java11 from Azul.
p.s. don't forget to change jdk version in Android studio
Preferences -> Build -> Build Tools -> Gradle -> Gradle JDK
Got the same error while I upgraded my build.gradle to Java 17. And the fix is as simple as we think:
Gradle starts supporting Java17 only from 7.3 release
Here's the complete reference for Java vs Gradle compatibility:
https://docs.gradle.org/current/userguide/compatibility.html
Upgraded my gradle to 7.3 in gradle-wrapper.properties.
https\://services.gradle.org/distributions/gradle-7.3.3-bin.zip
Some of you may experience now the Gradle dependency cache corrupt error after this like me. So better delete the gradle-wrapper.jar and reinstall it using the command:
./gradlew wrapper
Everything will work perfectly fine from here.
In case if you still face Gradle corrupt issue, please check whether you are using latest version of IDE especially Intellij.
First, you can execute this command: /usr/libexec/java_home -V, to retrieve all installed jdsk:
[~]$ /usr/libexec/java_home -V
Matching Java Virtual Machines (4):
17.0 (x86_64) "Oracle Corporation" - "OpenJDK 17.0" /Users/ciccio/Library/Java/JavaVirtualMachines/openjdk-17.0/Contents/Home
14.0.1 (x86_64) "Oracle Corporation" - "OpenJDK 14.0.1" /Users/ciccio/Library/Java/JavaVirtualMachines/openjdk-14.0.1/Contents/Home
11.0.12.1 (x86_64) "Amazon.com Inc." - "Amazon Corretto 11" /Users/ciccio/Library/Java/JavaVirtualMachines/corretto-11.0.12/Contents/Home
10.0.2 (x86_64) "Oracle Corporation" - "Java SE 10.0.2" /Library/Java/JavaVirtualMachines/jdk-10.0.2.jdk/Contents/Home
1.8.0_302 (x86_64) "Amazon" - "Amazon Corretto 8" /Users/ciccio/Library/Java/JavaVirtualMachines/corretto-1.8.0_302/Contents/Home
Now, imagine you want to remove the version 17:
[~]$ java -version
openjdk version "17" 2021-09-14
OpenJDK Runtime Environment Homebrew (build 17+0)
OpenJDK 64-Bit Server VM Homebrew (build 17+0, mixed mode, sharing)
Go into the path of the version you want to remove (in this case "/Users/ciccio/Library/Java/JavaVirtualMachines/openjdk-17.0/Contents/Home"), and delete entire folder: "/Users/ciccio/Library/Java/JavaVirtualMachines/openjdk-17.0".
Once removed, go back on terminal and use:
[~]$ /usr/libexec/java_home -v 14.0.1 --exec javac -version
javac 14.0.1
to force the new version to use (14.0.1).
Next check if is correct:
[~]$ java -version
openjdk version "14.0.1" 2020-04-14
OpenJDK Runtime Environment (build 14.0.1+7)
OpenJDK 64-Bit Server VM (build 14.0.1+7, mixed mode, sharing)
[~]$
Your Gradle now is back to work.
Basically, I installed jdk using brew install java which was not compatible with my current gradle I guess. So
I uninstalled java first using: brew uninstall java
installed JDK 8 or JDK 11 from azul.
Installed gradle: gradle-6.9-all.zip
When done, everything worked smoothly.
I found a way to fix this error without messing with the locally installed Java version or Gradle. Here is what I did:
If you are developing a Flutter project and got this error, go to File -> Close Project.
Then re-open from the android folder (omit this if you received from a pure Android project).
Now, Gradle may detect the issue on its own, and it will take a while to check. After it is done, it may provide upgrade steps in an upgrade assistant window at the bottom of the window along with logcat, build, terminal etc… which you need to accept and tell it to execute. Once it finishes, the error is resolved, and you are good to go.
If it does not seem to do anything on its own, then please open the Project Structure tab. Now select the latest Gradle version available that does not contain -rc (you don't want these, most of the time they are not stable releases).
Now select the JDK version that Gradle uses by going to Gradle (sidebar on the right of the window) -> Wrench Icon -> Gradle Settings. Select a compatible JDK version according to the Gradle project's documentation, as found HERE. Current latest stable version of Gradle is 7.4 with maximum supported JDK version 17 (also latest I believe if you use something like openJDK which I use), but Android Studio version at 7.1 so be careful.
Tested on MacBook Air M1 running macOS Monterey 12.2.1.
I faced this error when I updated my android studio
Solution:
you need to upgrade your distributionUrl According to the java version
Below is the Java version and Supported Gradle version
Check currently active java version:-
javac -version
If it is greater than 11 downgrade it to 11 or 8. Check your available java jdk version installed:-
/usr/libexec/java_home -V
If java 11 or 8 is not installed first install one of them using this link:- Download jdk 8
then change the default java version in .bash_profile
Edit .bash_profile
sudo nano ~/.bash_profile
Add 1.8 or 11 as default. (Add below line to bash_profile file)
export JAVA_HOME=$(/usr/libexec/java_home -v 1.8)
OR
export JAVA_HOME=$(/usr/libexec/java_home -v 11)
Now Press CTRL+X to exit the bash. Press 'Y' to save changes. And reload bash_profile
source ~/.bash_profile
Happened with newly created Flutter app in 2023 January with Mac Mini M1. If you have another working Flutter apps do not downgrade or update Java version as it will cause problem with all other working ones. Find gradle-wrapper.properities file inside gradle/wrapper folder (directly inside Android folder) and check gradle version. You just need to use newer version of gradle. I replaced this one and used flutter run command from terminal and it worked:
distributionUrl=https\://services.gradle.org/distributions/gradle-7.5-all.zip
With this one:
distributionUrl=https\://services.gradle.org/distributions/gradle-7.6-all.zip
No need to do anything else. Version number may be different for you depending on when you are trying this and what Java version you have.
Finally I Got the Solution
It is very easy to solve
step 1 : select the gradle version which support your java version link
step 2 : open your project navigate to your_project_name/android/gradle/wrapper/gradle-wrapper.properties
step 3 : in distributionUrl change the gradle version according to your java version
That's it No need to install older java versions
Happy coding
System: Mac M1, Android Studio Electric Eel (2022.1.1 Patch 1), JDK 19.02
I encountered this error when created a fresh project using flutter create and tried to run it in Android Studio.
Now I've got an interesting solution that worked for me:
Open the flutter project in Android Studio
Open build.gradle, the one under android folder
On the top right it shows "Open for Editing in Android Studio" (although it's already in Android Studio!). Click on that to open it for editing. I opened it in another window, but doesn't matter.
It starts to automatically download and update gradle to sync the build file. At one point, tt might also prompt you to upgrade gradle, which is good to do.
Done! Close the build.gradle and re-run the project. It should build and run fine.
I had this issue when I set the target for a new IntelliJ Kotlin project to be Java 17. My fix was to:
set the target to 9 in build.gradle.kt
close the project
delete the .gradle and .idea directories from the project folder
remove the project from the recent projects list
open the gradle file from IntelliJ and get it to rebuild everything
Open the Gradle settings and change the Gradle JVM to the same JDK version you are using.
(I am using 14.0.2)
This worked for me.
I had that Issue creating Projects from IntelliJ.
It seems the issue was the Gradle JVM Version.
Here is a configuration that works:
System:
Mac with ARM, Mac OS 12.1, M1 Max
java version 18.0.1-zulu
kotlin version 1.7.0
gradle version 7.5
I installed those version with sdkman https://sdkman.io/
and set the config manually on intellij (See attached Screenshot for Details)
IntelliJ Gradle JVM config
My solution was to open the android project in Android Studio. It detected the needed Gradle update and performed the update upon command.
I can't speak for everyone, but for me, I went into Flutter project's file android/gradle/gradle.properties, and changed the org.gradle.java.home value so that it pointed to a folder containing JDK 11 instead of JDK 18. That way, it used a JDK version that was actually supported.
On my side I fixed this issue by setting the default Java Version to 8 (download it if needed)
Mac:
Open Terminal.
open ~/.bash_profile
Add
# SWITCH TO JAVA VERSION 8
export JAVA_HOME=`/usr/libexec/java_home -v 1.8`
Save and restart Android Studio.
Giving my two seconds here...
In my case, I could fix it by finding my gradle version in the file gradle.wrapper.properties and checking the compatibility with the JDK, so I needed to install the JDK 16, so in my build.gradle(:app) I put this line of code inside the android {} :
compileOptions {
sourceCompatibility JavaVersion.VERSION_16
targetCompatibility JavaVersion.VERSION_16
}
After this I build my android version again, and it worked.
I ran into this issue on VSCode+Mac using the Gradle for Java extension.
My project uses Java 17 but Gradle was using JDK19, which I also had installed.
I removed the jdk-19.jdk folder from /Library/Java/JavaVirtualMachines and then ran the "Clean Java Language Server Workspace" task in VSCode.
After that, Gradle successfully built and I was even able to put the jdk-19 folder back and things continued to work.
Changing the Java Version in the Intellij resolved the issue.
Easy fix in 2023:
Command in the terminal:
export JAVA_HOME=$(/usr/libexec/java_home -v 1.8)
Check classpath, current working one:
classpath 'com.android.tools.build:gradle:7.1.2'
Check gradle-wrapper.properities file:
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-7.4-all.zip
If still not solved you need to change Gradle JDK from inside Android Studio like below.
After that you can run fluter app directly from terminal without any issue. Note: Android Studio default JDK (11.0.15) does not work and causes this issue. Azul Zulu 16.0.2 works and solves the issue.
In my case, I use the react native cli and my android gradle is 7.3.1. I open the android folder in the android folder in the android studio and it suggests my gradle once after degradation it works fine
Windows Users
Open Android Studio and Click on Setting ICON far right. And Go to Project Structure Option and select the SDK's Version 11.0.15 and click apply than on the left side click on Module Option and select Module SDK's options and select Project SDK 11. and at the bottom at Project Settings CLICK on SDK and select on 11 SDK versions. It will give you the JDK path
C:\Program Files\Android\Android Studio\jbr
Copy this path and Open the System Environment Variable Create a New JAVA_HOME path with the location
and click OK and save everything Now run your app in ANDROID STUDIO and ENJOY!
Context: Flutter, Mac M1, Java 19.0.2
Problem occured on following command:
flutter build apk
I just installed (reintalled) gradle via homebrew like this:
brew install gradle
I suppose it was related to my recent upgrade (Java was upgraded to OpenJDK Temurin 19.0.2).
I also noticed that flutter command was trying to use gradle 7.4 (the only one gradle version installed before). As previously mentioned by others, there has to be consistency between your Java version and gradle version according to Gradle Official Compatibility Matrix.
Please, verify it with following commands:
java -version
gradle -version
I think this process / solution can be applicable in general. Hope it helps!
I'm using os x and I've installed sbt with brew. After I've installed intellij and scala plugin for intellij it recognized .scala files of my project and suggested to import sbt project. When importing I saw that intellij is downloading sbt instead of using sbt installation that I have installed previously. How to force intellij to use sbt from brew? I don't want to clutter my ssd...
It is not a wise decision. sbt API changes slightly between versions. If intellij requires certain version for inner processing, it would be better to fulfil its expectations.
Set sbt.version in project/build.properties. IntelliJ respects the requested version. It won't download again if it has already been downloaded. You probably see this because the launcher you installed is a different version than what is installed in intellij. You can also set intellij to use the launcher you already have installed by changing the setting in preferences
the m2eclipse plugin is latest
the eclipse is the latest
the JDK is jdk7
the eclipse uses embedded maven version 3.xxx
I am keep getting this error “Error: Could not find or load main class org.codehaus.plexus.classworlds.launcher.Launcher”
It seems that there are some problems running the embedded Maven.
Try installing a fresh Maven version, then click Preferences , Maven, Installationsand set the directory where you have installed Maven.
my envirement
eclipse version : 4.3 kepler
maven version : 3.2.x
OS : windows 7
m2e plugin version : 1.5
the problem caused by combination of things, e.g mismatch between maven installation and setting.xml is one, but mainly the problem was:
solution for my problem was to run the eclipse in administrator mode.
you can run maven embedded (comes with eclipse) or external installation
just to make sure they are pointing to the right setting.xml file
somehow the embedded disappears sometimes, just restart eclipse it will appear again
finally I can confirm the latest m2e 1.5 or above supports maven 3.
Note: set JAVA_HOME is a must, because maven uses it to look up java which runs maven itself
set non-embeded maven installation location in the windows path is needed
set M2_HOME was NOT needed in my case, thus to get m2e working in eclipse or interact maven though command line, M2_HOME is not needed
I am getting this error in a Maven build (mvn clean install) on a Mac with Mountain Lion
org.tmatesoft.svn.core.SVNException: svn: The path 'XYZ' appears to be part of Subversion 1.7 (SVNKit 1.4) or greater
working copy rooted at '/Users/XYZ/workspace/XYZ'.
Please upgrade your Subversion (SVNKit) client to use this working copy.
I had SVN installed as part of the Apple Command Line tools package and that gets installed at /usr/bin. I have installed the latest SVN as well but that got installed at /usr/local/bin.
When the maven build runs, it does not pick up the latest SVN, it picks the older one and fails.
Has anyone faced this kind of problem before?
I think there are 2 options -
1) Somehow force maven to use the new installed SVN.
2) Upgrade the SVN installed as part of Apple' Command Line tools to the latest SVN. I have reinstalled Command Line tools with the latest version but it still sticks to the older version.
I dont control the pom.xml so modifying it is not a viable option.
Any pointers in resolving this would be much appreciated.
Thanks!
This means your svn client is version 1.7 but the working copy(your project workspace) was checkout with the older version.
It's simple by execute the following command at your project root directory, where the pom.xml is there.
svn upgrade
please note, the maven use the svn client which is in your OS path.
After upgrade you should configure your IDE to use the version 1.7 as well. In my case I use the Eclipes Juno sr1 with Svnkit.
Anyhow if you would not like to change the working copy or IDE configuration. There is an alternative by install the svn clinet 1.4/1.5/1.6 and set it active via OS path instead.
I hope this may help.
Regards,
Charlee Ch.