Skip to content
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: Patching YouTube 19.04.37 causes crash #1715

Closed
4 tasks done
RunDevelopment opened this issue Mar 2, 2024 · 9 comments
Closed
4 tasks done

bug: Patching YouTube 19.04.37 causes crash #1715

RunDevelopment opened this issue Mar 2, 2024 · 9 comments
Labels
Bug report Something isn't working Waiting on author Further information is requested

Comments

@RunDevelopment
Copy link

RunDevelopment commented Mar 2, 2024

Bug description

After downloading the YT 19.04.27 full APKfrom APKPure and trying to apply the default patches, Revanced manager crashes while trying to apply patches.

The last patch I saw it apply before the crash was Hide Seekbar. After that, some more messaged flew by, but they were too fast to read. It then printed a stack trace and crashed. I grabbed a screenshot of the visible part of the stack trace.

Version of ReVanced Manager and version & name of application you tried to patch

ReVanced Manager: 1.18.0
App: Youtube 19.04.37 (suggested version)

Installation type

Non-root

Device logs

revanced-manager_logcat_20240302022222933724.log

I had to zip and attach the logs, because they were too long for Github.

Patcher logs

Due to the app crashing, I cannot export any logs. The best I have a screenshot of the last frame of the app.

image

Acknowledgements

  • This request is not a duplicate of an existing issue.
  • I have chosen an appropriate title.
  • All requested information has been provided properly.
  • The issue is solely related to the ReVanced Manager
@RunDevelopment RunDevelopment added the Bug report Something isn't working label Mar 2, 2024
@oSumAtrIX
Copy link
Member

Please capture logs using logcat and grep for AndroidRuntime.

@oSumAtrIX oSumAtrIX added the Waiting on author Further information is requested label Mar 2, 2024
@RunDevelopment
Copy link
Author

When you say "logs" I assume you mean patcher logs? If so, I never debugged an app crash on a phone before (or anything on android). So is there any documentation on using those tools?

@sssh7710

This comment was marked as off-topic.

@oSumAtrIX oSumAtrIX closed this as not planned Won't fix, can't repro, duplicate, stale Mar 3, 2024
@oSumAtrIX oSumAtrIX reopened this Mar 3, 2024
@oSumAtrIX

This comment was marked as off-topic.

@RunDevelopment

This comment was marked as off-topic.

@oSumAtrIX

This comment was marked as off-topic.

@ReVanced ReVanced locked as resolved and limited conversation to collaborators Mar 3, 2024
@oSumAtrIX
Copy link
Member

oSumAtrIX commented Mar 3, 2024

Just noticed that the original author was not the one who responded with a crashlog that my response was meant for.
My response fixes the issue that appeared in the commenters logs and thus it seems we both got confused.

Reopening therefore, sorry for the confusion!

@RunDevelopment regarding the logs, you can use logcat to grab logs via ADB.

logcat | grep AndroidRuntime

@oSumAtrIX oSumAtrIX reopened this Mar 3, 2024
@ReVanced ReVanced unlocked this conversation Mar 3, 2024
@RunDevelopment

This comment was marked as resolved.

@oSumAtrIX

This comment was marked as resolved.

@oSumAtrIX oSumAtrIX closed this as not planned Won't fix, can't repro, duplicate, stale Mar 3, 2024
@ReVanced ReVanced locked as too heated and limited conversation to collaborators Mar 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug report Something isn't working Waiting on author Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants