💉 Release of ReVanced Patcher v22

ReVanced Patcher is approaching a new major release. The new version introduces a greatly improved API, most notably replacing the existing fingerprint system with a simpler and more flexible matching API. In addition, several APIs, such as patches, patch options, and the patcher itself, have been refined.

Notable changes

• Introduction of a new matching API replacing the fingerprint system
• Minor adjustments to the patches API
• Replacement of key and title fields with a unified name field for patch options
• New DSL-based API for the patcher

Release schedule

The dates below are estimates and may change if necessary. This announcement will be updated accordingly should the schedule be adjusted.

• February 7, 2026: ReVanced Patcher v22 merged into the dev branch
• February 20, 2026: Official release of ReVanced Patcher v22
• February 28, 2026 (17:00 UTC): ReVanced Manager switches to ReVanced Patcher v22
• May 7, 2026: Final deadline for migrating away from deprecated APIs

What this means for end users

ReVanced Manager starts using ReVanced Patcher v22 at a fixed date and time to allow third-party patch developers to update their patches at the same time.
ReVanced's patches may be instable for a couple release cycles due to bugs from updating to ReVanced Patcher v22. Users may want to wait for a few updates before using the new version.

Users running older versions of ReVanced Manager will receive an update prompt once the transition occurs. At that point, patch developers are expected to have updated their patches to ensure compatibility with ReVanced Patcher v22.

What this means for patch developers

ReVanced Patcher v22 does not guarantee backward compatibility with patches targeting v21. Patch developers must update their code to remain compatible. Most of the APIs have been deprecated but some require breaking changes to work with v22. The deprecated APIs will continue to work for a limited time, but developers are given enough time to update to the new APIs to ensure continued compatibility.

Quick migration guide

The fastest way to migrate existing patches is to merge the official ReVanced Patches template into your patches repository. This updates dependencies, compiler options, and build configuration automatically. After doing so, you can skip directly to step 4.

1. Update the ReVanced Patches Gradle plugin in settings.gradle.kts:
   
   

   plugins {
       id("com.revanced.patches") version "1.0.0-dev.8"
   }

   
   
2. Update the ReVanced Patcher dependency to version 22.0.0 or newer in your Gradle version catalog:
   
   

   [versions]
   revanced-patcher = "22.0.0"

   
   
3. Update compiler options in your patches module s build.gradle.kts:
   
   

   kotlin {
       compilerOptions {
           freeCompilerArgs.addAll(
               "-Xexplicit-backing-fields",
               "-Xcontext-parameters"
           )
       }
   }

   
   
4. Update API usages. Build the project and address any compiler errors. Common changes include:
   
   
   • Migration away from typealiased mutable types to fix toMutable errors
   • Updating Patch<*> to Patch (generic parameter removed)

If the project builds successfully, your patches are compatible with ReVanced Patcher v22. You may now wait for ReVanced Manager to switch to v22 and release your updates accordingly. Optionally, you can further future-proof your patches by removing remaining deprecated API usages.

For more references, check the official ReVanced Patcher documentation and the ReVanced Patches repository.

If you have any questions or need help updating, feel free to ask in the ReVanced Discord server (preferred) or at patcherv22@revanced.app.