How to fix the ''module java.base does not "opens java.io" to unnamed module '' error in Android Studio?

Question

Background

I started my first project in android studio to get familiar with Android programming.
I am following this tutorial, in which

I created a new project Empty Activity, without any change
It is supposed to simulate a simple app that shows "Hello World" message

Problem Description But every time I try to run and build (I want to emulator as of now), I get the following error message.

Unable to make field private final java.lang.String java.io.File.path accessible:
Unable to make field private final java.lang.String java.io.File.path
accessible: module java.base does not "opens java.io" to unnamed module @42760a00

Here is my config set-up:

Android Gradle plugin version: 4.2.1
Gradle Version: 7.0.1 (changed to fix another issue I had while syncing the Gradle ("Gradle sync failed: Unsupported class file major version 60") and based discussion on this forum as quoted below)

Andrey Dernov commented 14 Apr 2021 00:18 Please use Gradle 7.0 or JDK less than 16 version for importgin and building the project (Settings (Preferences on macOS) | Build, Execution, Deployment | Build Tools | Gradle | Gradle JVM option).

JDK: 16.0.1

Any suggestion or idea?

score 218 · Answer 1 · edited Oct 24 '22 at 23:30

218

The solution from GitHub has worked for me. It was no need to downgrade Java JDK. Just changed gradle version in gradle-wrapper properties to 7.1.1 (6.x does not support java 16), and adding the following line in gradle.properties:

org.gradle.jvmargs=-Xmx1536M \
--add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
--add-opens=java.base/java.lang=ALL-UNNAMED \
--add-opens=java.base/java.lang.reflect=ALL-UNNAMED \
--add-opens=java.base/java.io=ALL-UNNAMED \
--add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED

edited Oct 24 '22 at 23:30

Ondra Žižka

43,948
41
217
277

answered Sep 14 '21 at 14:50

lortschi

2,768
2
18
12

3

Thanks, man! it works for me, I just copied the code and paste it to android/gradle.properties – Jesus Erwin Suarez Feb 12 '22 at 01:56
5

It worked for me too. But could you explain what exactly this line do? – Arthur Pereira Mar 28 '22 at 18:30
2

it was not the correct answer, though it gives me and idea to change the gradle class path, and viola it worked – Lakhwinder Singh Mar 31 '22 at 08:34
2

For ButterKnife compiler, also add `--add-exports=jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED` – Miha_x64 May 23 '22 at 18:38
2

Worked for me after changing properties to 7.3.3 and making the change in jvmargs – Gilad M Oct 23 '22 at 15:01
Work also for Mac M1 – Raphael Cangucu Feb 18 '23 at 17:39
its worked for me. i have to some changes in AndroidManifest.xml too. like in intent filter add properties android:exported="true". Thanks – Ajay Mistry Apr 03 '23 at 18:39
1

@lortschi It worked but I want to know what caused the problem. – Tanjim ahmed Apr 13 '23 at 23:48
It worked and I don't care what caused the problem! – Matt Jul 08 '23 at 21:02

score 141 · Answer 2 · edited Jan 31 '23 at 09:28

141

You must be using a JDK version that is not supported by the Gradle Version. ( There is no need to downgrade )

1-Check your JDK Version from C:\Program Files\Java. In My Case, It's JDK-17.0.2

2-Check The Respective Gradle version for your JDK https://docs.gradle.org/current/userguide/compatibility.html

3-Open gradle-wrapper.properties from .\android\gradle\wrapper\ and change the distributionUrl to your required gradle version

e.g. for JDK 17

distributionUrl = https\://services.gradle.org/distributions/gradle-7.3-all.zip

4-Open build.gradle from .\android\build.gradle and change the plugin in the class path to the one according to your gradle version

e.g.

classpath("com.android.tools.build:gradle:4.2.2") for Gradle 6.7.1+
classpath("com.android.tools.build:gradle:7.0.0") for Gradle 7+

Check the Compatible Plugin for your Gradle version at https://developer.android.com/studio/releases/gradle-plugin#updating-gradle

5-run npx react-native run-android

edited Jan 31 '23 at 09:28

TWiStErRob

44,762
26
170
254

answered Jan 21 '22 at 21:08

usamayaseen

1,428
1
6
10

2

Thanks, this worked for me! Best answer! – dmoebius Feb 13 '22 at 00:38
2

best answer and solution, thanks, this answer should be accepted instead of downgrade jdk answer – saman Apr 12 '22 at 06:29
Great answer, Thanks, You need to update some numbers and it will be up-to-date – H Amr Jan 14 '23 at 21:01
1

In the last code block, did you mean Gradle 6.7.1+ and Gradle 7+? – TWiStErRob Jan 27 '23 at 13:32
@TWiStErRob Yes it's Gradle, bad I thought I fixed it. Updated! – usamayaseen Jan 29 '23 at 22:25
any update to this answer since JDK has been replaced with JBR now? – Raulp Aug 24 '23 at 17:43

score 26 · Answer 3 · answered Jul 05 '21 at 16:10

I think I found the solution.

If you are importing an old project you are likely to face this error.

Basically you made your old project with lower JDK versions and now you have higher JDK versions installed currently in your system.

You should avoid higher JDK versions for building older projects.

Basically Download JDK 8 (1.8) and install it.
change environment variable (write JDK 8 path to environment variable)
Then change your project structure and write JDK 8 path to JDK location.

invalidate caches and restart android studio.
build your project and it should work.

If you got the following error:

Error:Cannot fit requested classes in a single dex file.Try supplying a main-dex list. # methods: 72477 > 65536

Then add the following dependency in your app.gradle file:

 // multidex
implementation 'com.android.support:multidex:1.0.3'

then you need to enable multidex in your app.gradle file.

android {
compileSdkVersion 30

defaultConfig {
    applicationId "com.convenient.easymeasure"
    minSdkVersion 19
    targetSdkVersion 30
    versionCode 1
    versionName "1.0"
    multiDexEnabled true

    testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
}

score 15 · Answer 4 · answered Dec 20 '21 at 01:34

has worked for me in Macbook Air M1 Apple Silicon. you no need to downgrade or uninstall Java JDK.

in my case Just changed gradle version in gradle-wrapper.properties to 7.2 like this :

distributionUrl=https\://services.gradle.org/distributions/gradle-7.2-all.zip

and adding the following line in gradle.properties:

org.gradle.jvmargs=-Xmx1536M --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.reflect=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED

related solution on github

score 13 · Accepted Answer · answered Jun 01 '21 at 18:44

13

I found this discussion kind of related to my question. But could not figure out how to pass JVM parameters in Android studio.

But, the error is gone after replacing JDK 16 by JDK 15.

answered Jun 01 '21 at 18:44

Ashkanxy

2,380
2
6
17

5

I also fix the issue by replacing jdk 16 to 1.8. – Hill Jun 24 '21 at 07:57
78

Downgrading JDK is not a solution. – Rohit Gaikwad Nov 03 '21 at 07:15
@RohitGaikwad Why? – reducing activity Jan 15 '22 at 16:40
1

@reducingactivity, At first you should ask your AppSecurity Team whether downgrading is an accepted solution? They should never accept this. In enterprise applications all 3rd party softwares should move to latest versions only(For getting official support, new features and to avoid migration overhead (If you don't move from JDK15 to higher a version, then one day you will be forced to do so)). Moreover, Ask yourself just due to this one modularization issue why the enterprise should move back to JDK15? Looks like this is just a POC application. – Rohit Gaikwad Jan 16 '22 at 02:44
5

@RohitGaikwad I am not working in corporation with some dumb ban on downgrading. "They should never accept this." there are sometimes good reason for downgrading, including critical security issues. Blanket ban on downgrading is a typical corporation bureaucracy red tape. And that assumes that developers are unable to control their own machines, which is not true even in all corporations. Blanket "is not a solution" claim is not true. – reducing activity Jan 16 '22 at 07:14
1

@reducingactivity. Okay go for it, happy journey!!! Also, make sure you downgrade your other 3rdparty libraries example like logging from log4j2.x to 1.x!, If your developers encounters any blocking issues with logging. Moreover, What's the exact justification/root cause to downgrade the JDK? This needs to be bring on the table at first. – Rohit Gaikwad Jan 16 '22 at 11:24
1

@RohitGaikwad "What's the exact justification/root cause to downgrade the JDK?" "Android Studio is broken with it" is pretty compelling reason when one makes Android app :) "If your developers" - I do not have developers, I am developer. – reducing activity Jan 16 '22 at 12:30
2

@reducingactivity "Android Studio is broken" is not a root cause its an issue you are facing during development with JDK16. You need to justify what exact change in JDK16 have broken this. Check JDK16 release notes/Bug fix report for any changes made in the area you think is causing this regression. If your company have a paid support raise a bug with Oracle along with a POC which results into this exception. Also, Try with JDK17 it should be a better option then to downgrade as its a LTS and JDK15/16 are not LTS. The solution to upgrade Gradle looks good to me, find such issues at your end. – Rohit Gaikwad Jan 16 '22 at 13:18

score 9 · Answer 6 · answered Aug 31 '21 at 03:09

9

Run Flutter doctor, if there´s an error indicating that the java bundled can´t be found (specially if you have Android Studio version Artic Fox), run this commands if using Mac:

cd /Applications/Android\ Studio.app/Contents/jre
ln -s ../jre jdk
ln -s "/Library/Internet Plug-Ins/JavaAppletPlugin.plugin" jdk

answered Aug 31 '21 at 03:09

Andrey Solera

2,311
2
26
51

I was fighting with Android Studio Artic Fox (for 2 days) to build and run an android emulator. Flutter doctor was all good. I tried JDK 11, 15, 16. I tried adding variables to .bash_profile. I installed and tried older emulators. Nothing was working. Your commands worked. Can you explain why Andrey? – lopes710 Oct 23 '21 at 21:13
2

@lopes710 the reason is because the Artic Fox version have a different location for the java library, the commands from above is for giving the correct path. This error usually happens when you come from an older version of Android Studio to Artic Fox – Andrey Solera Oct 24 '21 at 14:43
This should be the accepted answer. If on mac, and after updating Android Studio to Arctic Fox 2020.3.1 (patch 4) from the previous version (4.2.2) – derZorn Jan 10 '22 at 11:16
Same here, I was wasting my time installing and changing versions of Java. - macOS Ventura. - Android Studio Dolphin (2021.3.1). – Edgar Mejía Jan 24 '23 at 01:11

score 5 · Answer 7 · answered Jan 30 '22 at 04:39

5

I was able to fix it by upgrading grade project settings using Android Studio which replaced classpath("com.android.tools.build:gradle:4.2.2") with classpath('com.android.tools.build:gradle:7.0.3') in android/build.gradle

answered Jan 30 '22 at 04:39

Kewal Shah

1,131
18
29

This replacement solved my issue in my Flutter project. – Suat Özkaya May 18 '23 at 14:07

score 5 · Answer 8 · answered Jan 23 '23 at 16:52

For those having these issues with the latest Android Studio - Electric Eel version, and other canaries and preview releases, note that the bundled jre directory in the Android Studio installation folder is now renamed to jbr

(This answer came from eja's answer on this question.)

To resolve this, just create a sym link jre -> jbr and Flutter won't complain.

On Linux

cd ~/android-studio/ && ln -s jbr jre

Windows (check installation folder)

cd C:\Program Files\Android\Android Studio
mklink /D "jre" "jbr"

or

New-Item -ItemType SymbolicLink -Path .\jre -Target .\jbr

Mac OS

cd /Applications/Android\ Studio.app/Contents
ln -s jbr jre

Note that if you are running a preview release, the default installation directory might be different, e.g. on Linux it would be

~/android-studio-preview/

score 5 · Answer 9 · edited Jun 18 '23 at 23:43

In my case the following steps did the trick:

Changing the gradle verion in gradle-wrapper.properties to:

distributionUrl=https\://services.gradle.org/distributions/gradle-7.3.3-all.zip

Changing build gradle and google services classpath version in build.gradle to:

dependencies {
    classpath 'com.android.tools.build:gradle:7.2.1'
    classpath 'com.google.gms:google-services:4.3.5'
}

score 3 · Answer 10 · answered Jan 15 '23 at 22:45

I had the same issue with a Flutter 2 project after updating Android Studio to electric eel. I was still able to build the android project, but flutter run on the Flutter project would cause this issue. lortschi's answer was the key, but it was missing one more entry to make it work, so my final gradle.properties looks like this now:

org.gradle.jvmargs=-Xmx1536M \
--add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
--add-opens=java.base/java.lang=ALL-UNNAMED \
--add-opens=java.base/java.lang.reflect=ALL-UNNAMED \
--add-opens=java.base/java.io=ALL-UNNAMED \
--add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED \
--add-opens=jdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED
android.useAndroidX=true
android.enableJetifier=true

I was very skeptical, but it worked.

score 3 · Answer 11 · answered Jun 26 '23 at 13:17

3

If you are importing an old project you may get this error

Download JDK 8 (1.8) and install it.
Change your project structure and write JDK 8 path to the JDK location.

some screenshots for reference (Android Studio Flaming version) (sorry, couldn't em images)

file -> project structure

SDK location -> Gradle Settings

Gradle JDK choose download JDK

Choose version 1.8

After download choose gradle jdk to 1.8

answered Jun 26 '23 at 13:17

darkbits

31
3

1

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jun 27 '23 at 14:33
I thought your answer was clear. Helped me, at least. Sometimes you just need some hand-holding with screenshots to sort things out. Thanks! – TheUnwokenFool Aug 31 '23 at 19:34

score 2 · Answer 12 · answered Dec 25 '21 at 14:58

2

I downloaded 2 JDK jdk-17.0.1 and jdk-11.0.13 and add below line on gradle.properties

org.gradle.java.home=C\:\\Program Files (x86)\\Java\\jdk-11.0.13

Also go to Android Studio (Arctic Fox)-> Project Structure -> Gradle setting and choose JDK version

answered Dec 25 '21 at 14:58

shubomb

672
7
20

1

Did every other possible solution mentioned none helped, only this! Thanks! – NovyLevi May 17 '23 at 07:12

score 2 · Answer 13 · answered Jun 03 '22 at 15:03

2

This is a known issue when using Gson and reflection for parsing Json. Updating your Android Gradle Plugin version to 7.0.0+ and the error should go away.

answered Jun 03 '22 at 15:03

mbonnin

6,893
3
39
55

score 2 · Answer 14 · answered Aug 05 '23 at 14:57

In my case, my error was happened when I'm using:

Gradle version = 6.5 & Gradle JDK version = 17.0.6 in Android Studio Giraffe (Stable)

You could check the Gradle version in the gradle-wrapper.properties file, on this line:

distributionUrl=https\://services.gradle.org/distributions/gradle-6.5-bin.zip

And check JDK version on:

File > Settings > Build, Execution, Deployment > Build Tools > Gradle > Gradle JDK

To fix this error, you need to pick JDK version that is compatible with your Gradle Version. You could check the compatibility in here:

https://developer.android.com/build/releases/gradle-plugin#updating-gradle

I pick JDK 11.0.18 for Gradle version 6.5 (a lower JDK version compared to my current JDK)

In summary, choosing the compatible JDK version is the answer for this error.

One more option: do an AGP update via AGP upgrade assistance. — Gleichmut, Aug 11 '23 at 10:08

score 1 · Answer 15 · answered Mar 17 '22 at 10:16

1

Installing JDK 1.8.0 and setting JAVA_HOME path to JDK 1.8.0's folder in environment variables worked for me.

answered Mar 17 '22 at 10:16

uvx4040

19
3

JDK 1.8 no longer has active support, it only has security support (for a little while longer) and I would not recommend using it anymore. There are newer versions available. See also https://endoflife.date/java – Simon Forsberg Jul 05 '22 at 12:41

score 1 · Answer 16 · answered Mar 18 '22 at 08:49

1

Had same problem with Flutter. I uninstalled Android Studio and Android SDK and reinstalled everything and upgraded Flutter, without success.

Then I created a new Flutter project and copied the sources from the old one, and this time it worked.

answered Mar 18 '22 at 08:49

Jean G

147
1
10

score 1 · Answer 17 · answered Aug 25 '23 at 07:07

Add this line in your gradle.properties file.

org.gradle.jvmargs=-Xmx1536M --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.reflect=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED

score 0 · Answer 18 · answered Sep 09 '21 at 17:28

0

You must be using JDK-16, use the version below JDK-16, in my case, I downgrade to JDK-11 and it worked for me.

answered Sep 09 '21 at 17:28

tread khuram

320
2
8

6

Downgrading only delays problems, it doesn't solve them. – Simon Forsberg Jul 05 '22 at 12:39

score 0 · Answer 19 · answered Sep 05 '22 at 03:12

Just added from another solution

If you have later version installed, and your project is using older version. Don't forget to check in terminal which jdk is used.

In my case my project using JDK 15. And terminal using 18. So i uninstall the other version and leaving the proper version (in my mac, just delete another jdk directory in /Libray/Java/JavaVirtualMachine)

score 0 · Answer 20 · answered Jan 30 '23 at 15:34

Windows user:

Go to C:\Users\arpan.gradle\caches and delete all the gradle cache.

then,

Go to "C:\Program Files\Android\Android Studio" there you will see jbr and jre folder then copy the content of jbr and paste the content into jre folder. ss: and run flutter doctor again and run your App.

score 0 · Answer 21 · answered Mar 16 '23 at 17:31

0

run

sudo update-alternatives --config

java and select a minor version of java .

answered Mar 16 '23 at 17:31

medis adido

1

1

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Mar 22 '23 at 00:50

score 0 · Answer 22 · answered Jul 28 '23 at 08:01

This is a known issue by Gradle when running tests with Java 17 with Test Distribution enabled

Add this to your build.gradle (.kts version available at the link below)

tasks.named('test', Test) {
    jvmArgs(
        '--add-opens', 'java.base/java.lang=ALL-UNNAMED',
        '--add-opens', 'java.base/java.util=ALL-UNNAMED'
    )
}

See https://docs.gradle.com/enterprise/test-distribution/#accessing_jdk_internal_classes_from_your_tests

See original github issue https://github.com/gradle/gradle/issues/18647

score -2 · Answer 23 · answered Jun 01 '21 at 06:21

-2

Check if JDK is installed or not configure your SDK also and try again you can download JDKfrom Java SE

answered Jun 01 '21 at 06:21

Dheeraj Gupta

405
1
4
12

Yes they are both set-up and configured in project structure section – Ashkanxy Jun 01 '21 at 06:35

score -2 · Answer 24 · answered Apr 19 '23 at 10:36

Steps To Solve

1. Gradle.properties

distributionUrl=https\://services.gradle.org/distributions/gradle-7.5-all.zip

2. Java version

choose java version 17 or any compatiable

3. Gradle Project

choose kotlin version and gradle miniume version


buildscript {
    ext.kotlin_version = '1.7.10'
    repositories {
        google()
        mavenCentral()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:7.2.0'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    }
}

This isn't helpful in any possible way. – judepereira Apr 24 '23 at 15:26 — judepereira, Apr 24 '23 at 15:26

Engr.Aftab Ufaq · Answer 25 · 2022-07-06T12:32:56.633

-3

After I updated jdk to 18 then I got this error mention I the question. so I downgraded to jdk11. to install jdk11 please run this command I windows 10. choco install openjdk11. Hope it will fix your problem.

To run the above command you must have to install chocolatey and add it to path. chocolatey is dependency manager for windows 10. Here is link to guide

Here is the link https://community.chocolatey.org/packages/openjdk11

edited Jul 06 '22 at 12:32

answered May 22 '22 at 07:14

Engr.Aftab Ufaq

3,356
3
21
47

You mention both jdk 18 and 11 here, that's a bit confusing? – Simon Forsberg Jul 05 '22 at 12:42
@SimonForsberg I have updated answer hope this solve your problem. more clearly you need to install jdk 11 – Engr.Aftab Ufaq Jul 06 '22 at 12:33
3

Downgrading does not seem like a good idea. – Simon Forsberg Jul 06 '22 at 21:00

How to fix the ''module java.base does not "opens java.io" to unnamed module '' error in Android Studio?

25 Answers25

Steps To Solve

1. Gradle.properties

2. Java version

3. Gradle Project

Linked

Related