-
Notifications
You must be signed in to change notification settings - Fork 25
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
bug: RVX crashing when clicking and opening up Youtube links from Reddit #2607
Comments
It doesn't reproduce on my side Please attach crash log |
I must add that if you click on any Youtube link in a mobile browser and Discord RVX crashes also so it's Youtube links in general that make RVX crash starting with the 5.1.1 patches. To reproduce Google someting like cat videos and click on any video link you see and then RVX will just crash with message RVX has stopped. |
log.txt |
I have this same issue too. That is what happens if I try to open YouTube links directly from the browser 😲 |
19.44.39 app (v5.1.3 patch) Crashes while opening youtube links from browsers (Using brave) And again Android 14 / ONEUI 6.1 doesn't crash. |
Exclude Please report back if the issue is reproduced |
It still crashes when opening YouTube web links despite excluding Navigation bar components when patching. |
Fixed in revanced-patches-5.2.1-dev.3 (Tested on Android 15 AVD) |
Type
Error at runtime
Tools used
RVX Manager
Application
RVX 19.44.39
Patches: v5.1.3 / v5.1.2 / v5.1.1
Bug description
Ever since patches 5.1.1 were released clicking on Youtube links in Reddit causes RVX to crash. This issue wasn't present before. I have reinstalled unpached Youtube and this issue is not present. Step 1 Find a Youtube link in Reddit Step 2. Click on it and it opens in a broswer. Step 3. Select RVX as the app to open it and then it crashes.
Error logs
No response
Solution
No response
Additional context
No response
Device Environment
Android 8.1 Oreo Samsung Experience 9.5
Acknowledgements
Experimental Flags
.pre-release
(dev branch).The text was updated successfully, but these errors were encountered: