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?

lortschi · Answer 1 · 2021-09-14T15:17:41.417

75

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 Sep 14 '21 at 15:17

answered Sep 14 '21 at 14:50

lortschi

1,250
1
11
11

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
It worked for me too. But could you explain what exactly this line do? – Arthur Pereira Mar 28 '22 at 18:30
1

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
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

usamayaseen · Answer 2 · 2022-04-21T21:52:25.420

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 JDK 6.71+
classpath("com.android.tools.build:gradle:7.0.0") for JDK 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

best answer and solution, thanks, this answer should be accepted instead of downgrade jdk answer — saman, Apr 12 '22 at 06:29

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

16

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

1,012
1
3
13

4

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

Downgrading JDK is not a solution. – Rohit Gaikwad Nov 03 '21 at 07:15
@RohitGaikwad Why? – reducing activity Jan 15 '22 at 16:40
@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
2

@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
@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
@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
@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 11 · Answer 4 · 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 7 · Answer 5 · answered Aug 31 '21 at 03:09

7

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

2,033
1
23
44

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 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

score 4 · Answer 6 · 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

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

14 Answers14

Linked

Related