Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error #20

Closed
mountaincastle47 opened this issue Nov 18, 2022 · 10 comments
Closed

error #20

mountaincastle47 opened this issue Nov 18, 2022 · 10 comments

Comments

@mountaincastle47
Copy link

You have an outdated version of JDK.Please get it from here: https://www.azul.com/downloads/?version=java-17-lts

I already installed the latest jdk 17 and rebooted my pc.

@Spacellary
Copy link
Collaborator

Spacellary commented Dec 26, 2022

Make sure that when you're installing it, check all the components in the "Set JAVA HOME" option in the installer.

Also run java --version in your Command Prompt/Terminal and report the results here, as you may have multiple versions of JAVA installed for some tool or game, I've been there, and that could have been it... You'll need to set the JAVA_HOME properly to the newer version.


After running java --version you want to see something like this (Java 17/18/19):

openjdk 17.0.5 2022-10-18 LTS
OpenJDK Runtime Environment Zulu17.38+21-CA (build 17.0.5+8-LTS)
OpenJDK Client VM Zulu17.38+21-CA (build 17.0.5+8-LTS, mixed mode, emulated-client)

@mountaincastle47 Heya!
My friend, any luck so far? 🙏 With Zulu JDK 19 32-bit maybe?

@mountaincastle47
Copy link
Author

Shet man I'm so sorry but my pc is uhh well destroyed due to some unfortunate circumstances and is in repair so I'll let you know in a few days. Once again I'm sorry

@Spacellary
Copy link
Collaborator

No problem man! Rough situation, hope everything is fixed soon!

@mountaincastle47
Copy link
Author

Idk if it was because of the java 17 as i had to change my c drive but it works now on java 19. Thanks!

@mountaincastle47
Copy link
Author

Error: EBUSY: resource busy or locked, unlink '\?\E:\program\Revanced Extended\revanced-cache\1.apk'
at unlinkSync (node:fs:1780:3)
at _unlinkSync (node:internal/fs/rimraf:214:14)
at rimrafSync (node:internal/fs/rimraf:195:7)
at node:internal/fs/rimraf:253:9
at Array.forEach ()
at _rmdirSync (node:internal/fs/rimraf:250:7)
at rimrafSync (node:internal/fs/rimraf:193:7)
at rmSync (node:fs:1274:10)
at afterBuild (C:\snapshot\rvx-builder2\wsEvents\patchApp.js:28:3)
at Socket. (C:\snapshot\rvx-builder2\wsEvents\patchApp.js:186:53)
[builder] Please report this bug here: https://github.com/inotia00/rvx-builder/issues.

@mountaincastle47
Copy link
Author

i rebooted the pc multiple times in case of some rogue program fucking up the process but nothing :(

@Spacellary
Copy link
Collaborator

Spacellary commented Jan 11, 2023

[Had to edit this several times to add all steps. Sorry about that.]

Maybe the steps and options in this thread do something for you.

#7 (comment)


Or in the meantime, you could use the docker-compose building method for a guaranteed clean environment for building:

  1. Install Git if you don't have it already.
  2. Install and make sure Docker Desktop is running.
  3. I recommend making a new empty folder.
  4. Right click inside it and "Open in Terminal/Powershell" here.
  5. Run git clone -b revanced-extended https://github.com/inotia00/rvx-builder --depth=1 --no-tags
  6. cd into or reopen the Terminal inside the newly created revanced repository folder.
  7. Follow the rest of the instructions to build with docker-compose in the main page here.
Although it's recommended to build with the --no-cache flag, you don't have to unless you want to update the builder, that way it will use the previous image to get you running the builder quickly.

To update the builder, open the Terminal inside the revanced repository folder, do a git pull to be sure, and follow the docker-compose instructions to build again, and you really have to use the --no-cache flag this time.

Overall this method has the advantage of pulling directly from the repository at the time of build, so you will pull all the most recent commits even if they aren't yet in the release builds.

The main advantage is really the clean environment for building, that should be reproducible in any machine regardless of setup.
Docker is amazing.

@mountaincastle47
Copy link
Author

i am officially giving up :( i am just gonna try with another computer

@Spacellary
Copy link
Collaborator

It should work then. It goes away in a clean environment like Windows Sandbox or a VM, or even just another PC.

Good luck! 🤞

@mountaincastle47
Copy link
Author

it works lol fml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants