Closed ghost closed 1 year ago
At least you should write down which method you patched with
At least you should write down which method you patched with
I first patched YouTube music, the folder was not deleted. After that, I flashed YouTube_18.16.39 and the story repeated itself, the revanced-cache folder and its contents are not deleted when the folder is completed or the button is pressed. What is not clear here?
What tools did you use?
Is it CLI? or is it rvx-builder ? or is it Revancify?
Please describe in detail the environment and issues you have tried to patch with screenshots.
What tools did you use?
Is it CLI? or is it rvx-builder ? or is it Revancify?
Please describe in detail the environment and issues you have tried to patch with screenshots.
I launched the program, it asked me to update the program itself to version rvx-builder v3.9.2, I updated the . After that, all patches were updated. (I deleted all the old patches). Next, I already had YouTube and YouTubeMusik files uploaded that I wanted to patch. Through (Upload APK) I chose YouTubeMusik, clicked to patch, everything was successfully flashed. But on completion of the file patch, it always deleted the folder ( revanced-cache ) . Now this folder remains completely with all the files in this folder and it has to be deleted by hand.
I think this will make it clearer.
tool used : rvx-builder 3.9.2
environment : Windows
content of the issue : The patch proceeds normally, but the revanced-cache directory is not removed
This is a temporary workaround to fix this old issue https://github.com/inotia00/rvx-builder/issues/7
The revanced-cache directory will be automatically removed each time you start the next patch
but after patching, a new revanced-cache directory will be created.
If this bothers you, simply use an older build of rvx-builder https://github.com/inotia00/rvx-builder/releases/tag/v3.9.1
Type
Other
Application
YouTube_Music_5.55.53_arm64-v8a
Bug description
After changing the file, the revanced-cache folder and its contents are not deleted.
Steps to reproduce
No
Relevant log output
Screenshots or videos
No response
Solution
No response
Additional context
No response
Device Environment
No response
Acknowledgements