oSumAtrIX
oSumAtrIX
An action secret should be added to this repository to support this build configuration: https://github.com/revanced/revanced-integrations/blob/7fe30d550ed2b21c09120600a8068e94143ca9cc/app/build.gradle#L20
# Issue: Patches can have resources. On Android, this will not be possible. # Solution Introduce a patch bundle format. Can be a ZIP file with the dex'ed resources for...
# Problem Currently, a failing patch can be destructive. This means if a patch fails it could cause problems on the patched application. # Solution This can be solved by...
## 🐞 Issue Currently, annotations are being used to give patches and fingerprints metadata. This approach proved to be unsuited for our case and should be subject to removal. ##...
A proposal was made by @Lucaskyy to fork dexlib2 and make all fields mutable by default. The gain of that would be, that we do not have to create a...
## Problem Currently, the patcher iterates twice through all instructions if a signature contains both opcodes and strings. ## Solution The opcodes should be iterated once if both opcodes and...
# Description Currently, `MethodResolver` iterates through all classes to find the methods matching the required signatures. Due to recent api changes, the `resolve` method is being called multiple times. Before...
Patch bundles should have metadata such as a name, origin, or licenses. This metadata can be useful to categorize patches into a bundle in the context of the patcher.
The `MethodSignature` uses a list for the parameter field. Instead, a string should be used. This will require migrating over existing signatures.