bug: Patching issues RVX Manager: 1.21.1

[54m4d]

Type

Error while patching

Tools used

RVX Manager

Application

v19.16.39

Bug description

I tried reinstalling RVX Manager multiple times, force stopping and clearing cache, but none of these actions made an improvement.

Error logs

- Device Info
RVX Manager: 1.21.1
Android version: 14
Supported architectures: arm64-v8a, armeabi-v7a, armeabi
Root permissions: No

- Patch Info
App: com.google.android.youtube v19.16.39 (Suggested: 19.16.39)
Patches version: v2.228.0-dev.15
Patches added: Hide Shorts dimming
Patches removed: Force snackbar theme, Spoof app version, Custom Shorts action buttons, Force player buttons background, Theme, Enable debug logging, Translations, Return YouTube Dislike
Default patch options changed: Visual preferences icons [RVX settings menu icon: gear]

- Settings
Allow changing patch selection: true
Version compatibility check: true
Show universal patches: false
Remove unused library: true
Use pre-release: true
Patches source: anddea/revanced-patches
Integration source: anddea/revanced-integrations

- Logs
Reading APK
Decoding app manifest
Loading patches
Merging integrations
Deleting existing temporary files directory
Decoding resources
Executing patches
Applied 48 patches
Compiling patched dex files
Compiled 8 dex files
An error occurred:
java.io.FileNotFoundException: /data/user/0/app.rvx.manager.flutter/cache/patcher/tmp-WUFJFY/revanced-temporary-files/patched/dex/classes7.dex: open failed: ENOENT (No such file or directory)
 at libcore.io.IoBridge.open(IoBridge.java:574)
 at java.io.RandomAccessFile.<init>(RandomAccessFile.java:289)
 at com.android.tools.smali.dexlib2.writer.io.FileDataStore.<init>(Unknown Source:7)
 at lanchon.multidexlib2.DexIO.writeMultiDexDirectoryCommon(Unknown Source:80)
 at lanchon.multidexlib2.DexIO.access$000(Unknown Source:0)
 at lanchon.multidexlib2.DexIO$1.call(SourceFile:0)
 at lanchon.multidexlib2.DexIO$1.call(SourceFile:0)
 at java.util.concurrent.FutureTask.run(FutureTask.java:264)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
 at java.lang.Thread.run(Thread.java:1012)
Caused by: android.system.ErrnoException: open failed: ENOENT (No such file or directory)
 at libcore.io.Linux.open(Native Method)
 at libcore.io.ForwardingOs.open(ForwardingOs.java:563)
 at libcore.io.BlockGuardOs.open(BlockGuardOs.java:274)
 at libcore.io.ForwardingOs.open(ForwardingOs.java:563)
 at android.app.ActivityThread$AndroidOs.open(ActivityThread.java:8782)
 at libcore.io.IoBridge.open(IoBridge.java:560)
 ... 10 more

Solution

No response

Additional context

No response

Device Environment

Android version: 14

Acknowledgements

• This issue does not reproduce on unpatched YouTube or YT Music.
• This issue is not a duplicate of an existing bug report.
• I didn't use any settings marked as Experimental Flags.
• I have chosen an appropriate title.
• All requested information has been provided properly.
• I have written the title and contents in English.

[ghost]

Already reported: #2355

In the meantime use revancify, tutorial:

https://www.reddit.com/r/revancedextended/comments/16019aj/how_to_install_with_revancify_tutorial/?rdt=48118

Edit: Also you are trying to patch anddea's rvx, not inotia00's. Inotia00 is only making sure that hes rvx manager supports his patches, not everyone elses. To patch anddea's rvx, use revancify. Though rvx manager currently has a bug that applies to inotia00's patches too.

[KobeW50]

This error is different than #2355

Also, that revancify tutorial is a bit outdated. The documentation or this guide is better

[54m4d]

I know how to use other patching methods, but how do you know it's the same issue?

[kitadai31]

Can you provide storage size and how much storage left?

[54m4d]

Can you provide storage size and how much storage left?

This is actually a good point, because last time I successfully patched the app, I had more storage space.

Currently, I have 2GB of storage left.

[ghost]

Can you provide storage size and how much storage left?

This is actually a good point, because last time I successfully patched the app, I had more storage space.

Currently, I have 2GB of storage left.

I have 224gb of storage free and 7gb of ram free and I couldnt install the patched app with RVX Manager.

[kitadai31]

Can you provide storage size and how much storage left?

This is actually a good point, because last time I successfully patched the app, I had more storage space.

Currently, I have 2GB of storage left.

Thank you
Then it is this issue: ReVanced/revanced-manager#2120

When storage space is not enough, Android system deletes Manager's temporary directory even while patching.
Fixed in Compose Manager (developing next major version of ReVanced Manager)

[54m4d]

Can you provide storage size and how much storage left?

This is actually a good point, because last time I successfully patched the app, I had more storage space.
Currently, I have 2GB of storage left.

Thank you Then it is this issue: ReVanced/revanced-manager#2120

When storage space is not enough, Android system deletes Manager's temporary directory even while patching. Fixed in Compose Manager (developing next major version of ReVanced Manager)

Thanks! That's very good to know. I will try to free up some space and then try again.

[ILoveOpenSourceApplications]

Hey @inotia00, will you be bumping RVX Manager to v1.21.2 with the next patch release?

[inotia00]

fixed in rvx-manager-1.21.3

[kitadai31]

It is not fixed yet!
ReVanced/revanced-manager#2135 solves EACCESS (Permission denied) error for in.apk when patching SoundCloud, which is separate from this issue (ENOENT while patching)

ReVanced/revanced-manager#2193 directly fixes this issue

[inotia00]

Well.. I haven't received any issues related to RVX Manager since a few weeks ago

The reasons for this decision are as follows:

1, RVX Manager is a minimally modified fork of ReVanced Manager
: RVX Manager is a fork to maintain compatibility with my patches

Most issues that occur in RVX Manager can be reproduced in ReVanced Manager

It's better to simply open an issue in the ReVanced Manager repository for maintenance and support

2, Even if a user opens an issue here, there is nothing I can do
: If a user opens an issue, they have to re-open the same issue in the ReVanced Manager repository to get support for the bug

3, RVX Manager is an option that exists simply to ensure compatibility with my patches
: There are other patching methods available in the docs besides RVX Manager

For this reason, all issues related to RVX Manager that were opened in the last few weeks have been marked as Not planned and closed