-
-
Notifications
You must be signed in to change notification settings - Fork 223
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: Keyboard Hard-Freezes when oppening the comment reply box #105
Comments
Exclude patches until the issue is solved, report back which one caused it |
Also try clearing the app data |
Lately my Samsung keyboard has been freezing. Maybe not related to ReVanced🤔 |
Sorry i didn't respond, i have been busy with university and didn't open GitHub for some time... I found this thread with a bunch of people having the same problem (I know it's revanced extended reddit but i'm using normal revanced[this repo] and we are all having the exact same issue). |
Will try if i have the time, currently i can't. Sorry.
I did clear data but it didn't solve the issue... |
Once you have time open a new issue with the new details you found |
So... update. It seems to be an issue with the YouTube app itself. Disabling all the patches didn't even solve the issue. So... dunno if something could even be done to solve it with a patch from the ReVanced team? So far i have identified that:
|
Oh wait... i just read more below about that and...
|
Note: On that chinese tablet and on my phone i had animations disabled because they are low end devices... maybe that is why it didn't happen there. |
Bug description
When oppening the comment reply box (making a comment) sometimes (constantly, but not always) the keyboard freezes, it happens with OpenBoard, it happens with Samsung Keyboard.
I'm suspecting it has to do with the "word prediction" feature.
Seems to be triggered by the comment box oppening and clossing multiple times by itself when trying to comment.
Error logs
Solution
No idea, more research is needed to find the exact cause of the issue.
Additional context
Acknowledgements
The text was updated successfully, but these errors were encountered: