It's more complicated than that. Java programs use their own code, libraries distributed with the Java JVM, and third party libraries that are referenced and are loaded via the classpath. So in this case, MC is using a third party library from Apache (http://commons.apache.org/io/) using the FileUtils class. The method in this class writeStringToFile() doesn't exist in all versions of that library, but it DOES exist in the version that Minecraft distributes and references. However, if for some reason, the JVM loads a different version of the library first, then when you refer to FileUtils.writeStringToFile() it could throw this error. That's what the minyaa site was talking about. There was an older version of the library laying around after an upgrade, and there was a chance the wrong version would be selected.
Any file on the hard disk named something like "commons-io<anything>.jar" would be suspect, especially if it was in the JVM tree because that can cause them to be preloaded in favor of anything specified in the classpath.
Minecraft should be using %appdata%/.minecraft/libraries/commons-io/commons-io/2.4/commons-io-2.4.jar
Spent some time on MC chat support. After several attempts to fix the problem someone found some information on a similar bug on a previous version of the launcher. He said he would log my issue in so hopefully it will be resolved soon.
It's more complicated than that. Java programs use their own code, libraries distributed with the Java JVM, and third party libraries that are referenced and are loaded via the classpath. So in this case, MC is using a third party library from Apache (http://commons.apache.org/io/) using the FileUtils class. The method in this class writeStringToFile() doesn't exist in all versions of that library, but it DOES exist in the version that Minecraft distributes and references. However, if for some reason, the JVM loads a different version of the library first, then when you refer to FileUtils.writeStringToFile() it could throw this error. That's what the minyaa site was talking about. There was an older version of the library laying around after an upgrade, and there was a chance the wrong version would be selected.
Any file on the hard disk named something like "commons-io<anything>.jar" would be suspect, especially if it was in the JVM tree because that can cause them to be preloaded in favor of anything specified in the classpath.
Minecraft should be using %appdata%/.minecraft/libraries/commons-io/commons-io/2.4/commons-io-2.4.jar
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSo all CADolfan has to do is to search for multiple versions of the apache librariy. Thanks, gerbil
Spent some time on MC chat support. After several attempts to fix the problem someone found some information on a similar bug on a previous version of the launcher. He said he would log my issue in so hopefully it will be resolved soon.
https://bugs.mojang.com/browse/MCL-1274#