I know we can check the app info page for this, but it'd be a nice QoL feature to somehow indicate what the last successfully patched version of an app was. This removes the need to switch back and forth between settings and termux repeatedly when updating multiple apps.
This could be implemented either as a note at the top of the APK selection screen (e.g. "Last patched version: xx.xx.xx"), or some kind of indicator on the APK list itself (e.g. "* 19.04.37").
Perhaps the simplest way to do this would be to look at the directories that exist within /revancify-data/apps/, but this has the disadvantage that (as it was recently pointed out to me) the current intended behavior is to delete the existing directory for any package name prior to attempting to patch a different version of that package. If this behavior were changed to delete the old directory only after verifying the creation of a new APK, then this would be a more reliable way to track what the last patched version of any app is.
I know we can check the app info page for this, but it'd be a nice QoL feature to somehow indicate what the last successfully patched version of an app was. This removes the need to switch back and forth between settings and termux repeatedly when updating multiple apps.
This could be implemented either as a note at the top of the APK selection screen (e.g. "
Last patched version: xx.xx.xx"), or some kind of indicator on the APK list itself (e.g. "* 19.04.37").Perhaps the simplest way to do this would be to look at the directories that exist within
/revancify-data/apps/, but this has the disadvantage that (as it was recently pointed out to me) the current intended behavior is to delete the existing directory for any package name prior to attempting to patch a different version of that package. If this behavior were changed to delete the old directory only after verifying the creation of a new APK, then this would be a more reliable way to track what the last patched version of any app is.