-
-
Notifications
You must be signed in to change notification settings - Fork 209
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
fix: clear FingerprintResolutionLookupMaps
before patching
#210
Conversation
Right now, if we abort the patching process after merging integrations, we need to restart the app to start another patching process. This PR aims to allow clearing the maps from previous patching session so that new session can be started at any time.
Alternatively the patcher can clear the maps in the main patch routine. Then the clear method does not need to be exposed and manager won't need any changes. |
Instead: revanced-patcher/src/main/kotlin/app/revanced/patcher/fingerprint/method/impl/MethodFingerprint.kt Line 102 in c65c3df
Replace that line with clearFingerprintResolutionLookupMaps() That'll fix the issue |
Yes. Since the maps needs to be cleared just for patching process for now, this is a good solution. |
FingerprintResolutionLookupMaps
before patchingFingerprintResolutionLookupMaps
before patching
Thank you for contributing to ReVanced. Join us on Discord if you want to receive a contributor role. |
## [12.1.1-dev.1](v12.1.0...v12.1.1-dev.1) (2023-08-03) ### Bug Fixes * clear method lookup maps before initializing them ([#210](#210)) ([746544f](746544f))
## [12.1.1](v12.1.0...v12.1.1) (2023-08-03) ### Bug Fixes * clear method lookup maps before initializing them ([#210](#210)) ([746544f](746544f))
Right now, if we abort the patching process after merging integrations, we need to restart the app to start another patching process.
This PR aims to clear the maps from previous patching session so that new session can be started at any time.