revanced-manager icon indicating copy to clipboard operation
revanced-manager copied to clipboard

bug: v0.1.0,v0.1.1 cannot be installed over v0.0.57

Open psydvl opened this issue 1 year ago • 12 comments

Type

Other

Bug description

v0.0.57 have version code 57 ~~1000001800~~ v0.1.0 have version code 1 ~~1000001798~~ So, for android, v0.1.0 is downgrade, but not update

Steps to reproduce

  1. Install v0.0.57
  2. Try to update with v0.1.0
  3. Face update error

Android version

Any

Manager version

v0.0.57

Target package name

Not related

Target package version.

Not related

Installation type

Non-root

Patches selected.

Not related

Device logs (exported using Manager settings).

None

Installer logs (exported using Installer menu option) [unneeded if issue is not during patching].

No response

Screenshots or videos

No response

Solution

No response

Additional context

No response

Acknowledgements

  • [X] I have searched the existing issues and this is a new and no duplicate or related to another open issue.
  • [X] I have written a short but informative title.
  • [X] I filled out all of the requested information in this issue properly.
  • [X] The issue is related solely to the ReVanced Manager and not related to patching errors or patches

psydvl avatar Apr 20 '23 20:04 psydvl

Try uninstalling 0.0.57, then install 0.1.0.

Julius8900 avatar Apr 20 '23 20:04 Julius8900

Try uninstalling 0.0.57, then install 0.1.0.

It's a crutch, not a solution: You need then backup+restore patches and keystore, and reclick not backupable settings

psydvl avatar Apr 20 '23 21:04 psydvl

I was wrong about version code The one in AndtoidManifest should be different too

Screenshot_2023-04-21-00-50-42-63_824de691399edbc594a434a2aa0f3de5.jpg

Screenshot_2023-04-21-00-50-24-04_824de691399edbc594a434a2aa0f3de5.jpg

psydvl avatar Apr 20 '23 21:04 psydvl

Do you know any possible solutions?

Aunali321 avatar Apr 20 '23 22:04 Aunali321

https://stackoverflow.com/questions/53570575 NB: versionCode can be the same over releases, but shouldn't be lower for next one

psydvl avatar Apr 20 '23 22:04 psydvl

Yeah, but that's not a good solution, we have no use for versionCode anymore and throwing a random permanent versionCode like 57 or anything above (like 100 just for the sake of it) is a terrible solution

Ushie avatar Apr 20 '23 22:04 Ushie

Is there a way to do this without explicitly stating versionCode anymore?

Ushie avatar Apr 20 '23 22:04 Ushie

Hey! thanks for your tip, I read the android docs about this and we'll go through with bumping the versionCode to 58 SmartSelect_20230421_012406_Chrome

Ushie avatar Apr 20 '23 22:04 Ushie

Or alternatively, set the version code to the current date/GMT date/UNIX timestamp automatically such that the new version would never have a lower versionCode

SodaWithoutSparkles avatar Apr 21 '23 07:04 SodaWithoutSparkles

Try uninstalling 0.0.57, then install 0.1.0.

It's a crutch, not a solution: You need then backup+restore patches and keystore, and reclick not backupable settings

Just a heads up, at least for me, settings and selections persisted uninstalling the old app and installing the new version

Masamune3210 avatar Apr 21 '23 14:04 Masamune3210

Try uninstalling 0.0.57, then install 0.1.0.

It's a crutch, not a solution: You need then backup+restore patches and keystore, and reclick not backupable settings

Just a heads up, at least for me, settings and selections persisted uninstalling the old app and installing the new version

Probably not for keystores

wolf-yuan-6115 avatar Apr 22 '23 17:04 wolf-yuan-6115

Yeah, I have tried. Even if you have the cloned the orginal keystore in android/data, you could not put it back and expect it to work.

SodaWithoutSparkles avatar Apr 22 '23 17:04 SodaWithoutSparkles