feat: Optimization #Automatically delete APK cache after locally installing manager update

[Figim]

Feature description

The APK cache is not deleted after the manager is updated. The manager should delete the APK cache so that the application does not take up too much memory.

Motivation

Save memory😊

Acknowledgements

• I have checked all open and closed feature requests and this is not a duplicate.
• I have chosen an appropriate title.
• The feature request is only related to Morphe (Manager).

[optimatrix0]

To be honest, this is not the only issue. Sometimes a dependency changes, something in the patcher gets modified, and if data remains in the cache, the patching process may fail, freeze, or cause a glitch that makes the app crash and close automatically. This has already happened to me.

It would be great to have an option to automatically clear the cache, or at least allow users to manually clean potentially corrupted data within the settings. That way, the manager could stay consistently updated and reduce the risk of data corruption.

Ideally, there should be either automatic cache clearing or a built-in option in the settings for better management. I support this request as a more advanced Manager user, and also because of the bug I am reporting here related to this issue.

I also want to thank the person who created this request, as it addresses the same problem I was experiencing. I just wanted to add my perspective and complement the discussion.

To clarify why I believe this is cache-related: I tried updating Reddit to a newer experimental version (around 2026.08.0). During the update process, the Manager froze and kicked me back to my phone’s home screen. The only way I was able to fix it was by force-stopping the app and clearing the cache. After that, the patching process completed normally without any issues. Since the problem was resolved immediately after clearing the cache, it strongly suggests that corrupted or outdated cached data was the root cause.

I agree, when I used Morphe Manager for the first time I got corrupted cache I believe. I was changing custom branding name (app name), and I accidentally added the name in both fields (app name and icon name). This resulted in patch failing, I removed the accidental name from the icon name, I patched again. But this time patching got stuck so I cancelled, tried again, the same thing happened.

Then I force closed the Manager, cleared cache, made changes to the patch selection, and it patched successfully. So, accidentally adding the name for icon failed patching and corrupted cache.

Clearing cache should also take place if patching fails. When patching fails, it can make it so that the Manager gets stuck in an error loop, even when an item causing patching to fail was changed/removed, it won't clear the "stuck error loop" until user clears app cache.

[Tiagoquix]

I agree with both deleting the original APK and the patched APK. There shouldn't really be a need to keep those in cache after patching and installing the modified one.

[LisoUseInAIKyrios]

The original APK can be used for repatching. It is useful.

[MarcaDian]

In general, the manager should clear cacheDir during each fresh launch + Android itself clears the cache directory as needed

Only the folders with saved original and patched APKs are not cleared, another temporary folder used during patching is cleared after successful or unsuccessful patching and in other cases.