generated from ReVanced/revanced-patches-template
-
-
Notifications
You must be signed in to change notification settings - Fork 227
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 (youtube): Crashes multiple times on launch. #962
Labels
Bug report
Something isn't working
Comments
Step 4 is your issue. |
So I can't run it at all without root then? That's unfortunate. |
Root has nothing to do with selecting patches incompatible with the APK you select. |
You need to patch the recommended yt version Use a guide https://hokorayinphinempp.github.io/obsidian-git-sync/Revanced/1%20Start%20Here%21/Revanced%20Start/ |
Slenderman00
pushed a commit
to Slenderman00/revanced-patches-grindr
that referenced
this issue
Jan 31, 2024
# [2.102.0](ReVanced/revanced-patches@v2.101.0...v2.102.0) (2022-11-03) ### Features * **youtube-music:** bump patches compatibility to v5.31.50 ([ReVanced#962](ReVanced/revanced-patches#962)) ([476fcc8](ReVanced/revanced-patches@fb6a5df))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Type
Error at runtime
Bug description
After installing the Revanced Manager, enabling experimental patches for the MicroG patch to be used (my phone is non-rooted), selecting the YouTube APK (latest from Play Store as of yesterday, May 14th), then keeping the default patches and toggling the MicroG patch, then patching the app (successfully, but there are dependancy errors in the log) and installing it, it does not open. Instead, Android reports that it keeps crashing frequently.
Steps to reproduce
Relevant log output
Screenshots or videos
Screen_Recording_20230515-222053_One.UI.Home.mp4
Solution
Not applicable
Additional context
My phone is not rooted
My phone is a Galaxy A70
My phone is running the latest available Android 11 and OneUI 3.1
Acknowledgements
The text was updated successfully, but these errors were encountered: