[Jman-Github]

Summary

Add Reseam patching support through an optional runtime plugin, including signed .reseam bundles, custom Git repository imports, and patching split APKs without merging them.

The integration uses URV’s existing patching screens, logs, progress tracking, resource graphs, and batch flows while accounting for Reseam’s native engine and separate APK components.

This also improves split APK download handling, preserves unmerged downloads for later patching, extends CI coverage to the new plugin, and removes the legacy release and changelog transition logic.

Reseam runtime plugin

• Add an optional Reseam runtime plugin versioned 1.0.0, using Reseam SDK 0.20.1.
• Use the same icon as the ReVanced v21 runtime plugin.
• Distribute the plugin separately through release assets for download and import.
• Detect Reseam bundles using the .reseam extension and bundle format markers.
• Load bundle identity, patches, compatibility information, and options through the SDK.
• Verify signed catalogs and retain signer identity checks for bundle updates.
• Support dependency bundles and reject conflicting duplicate sources.
• Report incompatible bundles with clearer runtime version errors.

Repository imports

• Support repository links from custom Git hosts, including git.reseam.app.
• Discover compatible release assets from Forgejo/Gitea and self-hosted GitLab repositories.
• Support Reseam bundle indexes alongside existing repository import methods.
• Recognize .reseam assets when importing GitHub releases.
• Preserve existing ReVanced and Morphe bundle handling.

Split APK patching and installation

• Pass the base APK and selected split components directly to Reseam without merging them.
• Identify the base component from its manifest and normalize its filename for the SDK.
• Respect split selection, native library stripping, and unused split preferences.
• Remove the SDK’s signing block before applying URV’s configured signing identity.
• Sign every output component with the same key and package the result as a split APK archive.
• Use the session-based split installer when System Installer is selected.
• Support split output through the built-in Shizuku installer and compatible root installation paths.
• Prevent unsupported rooted mount operations for split output.

Patching progress and diagnostics

• Integrate Reseam events with URV’s existing patching steps and logs.
• Show progress while inspecting and extracting split components.
• Prevent repeated preparation events from restarting displayed progress.
• Track writing and output preparation without moving completed progress backwards.
• Display readable patch names while retaining stable identifiers for selections.
• Include native process memory alongside existing resource telemetry.
• Report storage exhaustion with clearer failure details.

Download handling and performance

• Preserve downloaded split APK archives for later Reseam patching.
• Identify saved downloads as APK or Split APK in the downloads screen.
• Preserve the appropriate file extension when exporting downloaded or patched apps.
• Inspect split manifests without extracting every APK first.
• Reuse validated download metadata during patch preparation to avoid duplicate inspection.

Cleanup and runtime consistency

• Clean up Reseam workspaces and temporary split files after success, failure, or cancellation.
• Include abandoned Reseam workspaces in existing scratch cleanup.
• Integrate process lifecycle handling with URV’s existing runtime infrastructure.
• Share common runtime plugin helpers with the ReVanced v21 plugin.
• Preserve existing ReVanced v21 behavior while making those helpers reusable.

Artifact

https://github.com/Jman-Github/Universal-ReVanced-Manager/actions/runs/40064559761/artifacts/12548429254

Note

PR build data and regular release data are kept separate to prevent conflicts when switching between release builds and PR artifacts. Because of this, when you install a PR artifact, your app data will appear to be reset. It’s only a clean slate for that specific PR build. Your previous data is still preserved, and once you reinstall the release build you were using before, that data will be restored.

Validation

• git diff --check passed.
• .\gradlew.bat assembleRelease passed.
• Focused JVM tests passed for runtime integration, bundle imports, split archives, saved downloads, and progress tracking.
• Verified third-party bundle loading with Reseam SDK 0.20.1.
• Workflow syntax and artifact checks passed.
• Seven shell regression suites passed under Ubuntu WSL.
• End-to-end patching and installation on an Android device.
• Feedback and verification from users on the Reseam integration.