[Jman-Github]

Summary

Fixed inconsistent bundle, split-selection, and installation feedback across the manager.

Closes #601, #605, #610, #613, #618, #632, #633, #666, #671, #672, #676, #680, #704, and #673

Changes

• Preserve bundle-name casing and identify the release channel in import notifications.
• Use correct singular/plural wording for bundle progress, removed patches, and update badges.
• Prevent cancelled APK preparation from displaying a failure dialog.
• Remove outdated split-selection guidance and align the Cancel button.
• Add merger installation cancellation and match the patcher's success dialog.
• Distinguish patched and merged app installation toasts.
• Center the memory-limit dialog title and consistently prefix displayed versions with v.
• Fix keystore converter error wrapping so supported extensions flow naturally with the message.

Testing

Required device testing:

• Import/update one bundle and multiple bundles; verify counts and singular/plural wording in both dashboard and settings banners (feat: String improvements #601, feat: Importing bundle notification improvements #633).
• Remove one saved patch and multiple saved patches; verify the dialog wording (feat: Support patches removed dialog singular/plural #605).
• Cancel APK preparation while reading a large APK or split archive; confirm no failure dialog appears and retry works (feat: Remove dialog #610).
• Open split selection from both patcher and merger; verify the outdated default-selection sentence is absent and Cancel is left-aligned (feat: Remove sentence #613, feat: Move Cancel button #618).
• Import bundles through settings and discovery; verify name casing, “patch bundle,” and latest/pre-release/release labels (feat: Importing bundle notification improvements #632).
• Install patched and merged APKs; verify progress toasts, successful installation toasts, and the merger's centered success dialog (feat: Consistency improvements #666, feat: Consistency improvement #671, feat: Update toast messages #672).
• Cancel merged APK installation and retry. Cover internal, external, Shizuku, and root Play Store installers where supported; verify cleanup and recovery.
• Trigger the unsupported-keystore toast; verify the existing message has no forced line break (feat: Make it single sentence #673).
• Open the memory-limit dialog; verify its title is centered (feat: Centre dialog title #676).
• Verify the update badge with one outdated bundle and multiple outdated bundles, including a mix of current and outdated bundles (feat: Support singular/plural #680).
• Verify a single v prefix in Settings, About, installed app details, and every applied bundle version (feat: Consistency improvements #704).
• Verify that when an unsupported file is selected in the keystore converter, the error text wraps (feat: Make it single sentence #673).

Artifact

https://github.com/Jman-Github/Universal-ReVanced-Manager/actions/runs/35447535383/artifacts/10586492032

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

• assembleRelease passed.
• git diff --check passed.

[Kuddus73]

I could test the points above if you provide the latest artifact.

One note, it would be better to number the testing points, like "1. Import/update one...", "2. Remove one saved...", so they are easier to refer to if needed.

[Jman-Github]

I could test the points above if you provide the latest artifact.

The artifact is linked under Artifact in the PR description above. If you're able to test it and let me know if the corresponding issues have been resolved, that would be great.

One note, it would be better to number the testing points, like "1. Import/update one...", "2. Remove one saved...", so they are easier to refer to if needed.

There listed as they currently are so they can be checked off as testing goes.

[Kuddus73]

I could test the points above if you provide the latest artifact.

The artifact is linked under Artifact in the PR description above.

The current artifact link is from 5 days ago, but the last commit was 19 hours ago, that is why I thought it was not the latest artifact.

[Jman-Github]

The current artifact link is from 5 days ago, but the last commit was 19 hours ago, that is why I thought it was not the latest artifact.

Understandable confusion, and my bad for not clarifying. Those recent commits are just merge conflict fixes from dev. When other PRs were merged into dev, they caused a few changelog conflicts that needed to be resolved.

The artifact linked above is still the latest one and is the version you should be using.

[Kuddus73]

1st bug:

On pr.710, once again, I cannot go back to dev 22:

Tried also updating via the manager:

2nd bug:

The manager crashes if you try to uninstall an app via the manager:

Screen_Recording_20260918_225722_Nova.Launcher.mp4

Crash log: crash_log.txt

6th point (#666):

The patcher's toast message keeps appearing, disappearing and reappearing (like "pulsing") until the app is installed:

Screen_Recording_20260918_222402.mp4

The merger's toast message does not do that, it only appears once:

Screen_Recording_20260918_221050.mp4

For consistency, make the merger's toast message pulse until the app is installed like the patcher's.

2nd point (#605):

I do not think I can test this, as it is quite rare for a patch to be removed and even rarer for multiple patches to be removed.

10th point (#680):

Same with this, as it is not possible to know when bundles get updated.

7th point:

No idea what to do, do not even have Shizuku or root.

The rest of the points are fine.

[Jman-Github]

Thanks for your help! Tested the fix and everything else that you couldn't test yourself, and it all works as intended.