#Customizing release version for android

1 messages · Page 1 of 1 (latest)

dusk spruce
#

Hi shorebird team!

It seems the shorebird release version for android is determined by versionName and versionCode. Currently android has an anti downgrade protection on versionCode i.e. it needs to be larger if I want to update the current app (https://developer.android.com/studio/publish/versioning#versioningsettings).
Is it possible to override this rule for release version, because currently I need to find this version if I want to create a patch.

I use this in part of my CI and there I just use git tags to know what release version to make the patch from, but currently I need to find the full release version is instead of just knowing that it is always <tag>+1.
Please let me know if I misunderstood something about the concept.

Android Developers
Version your app  |  Android Studio  |  Android Developers

Versioning is a critical component of your app upgrade and maintenance strategy.

edgy galleon
#

Sorry for the delay. I'm not sure I understand what you're asking for. Why do you need to downgrade the version code?

dusk spruce
#

I don't want to downgrade the android version code, I would like to create a shorebird release-version that isn't dependent on the version code.

edgy galleon
#

Shorebird uses the app's release version to identify the release, so I'm not sure what you want to do is possible. Can I ask why you want this?

crystal orbit
dusk spruce
# edgy galleon Shorebird uses the app's release version to identify the release, so I'm not sur...

Currently I pass e.g. 10.0.5+1938 to my pipeline that then uses this release version to know what to create a patch from. Currently my solution for finding this release version is to log into shorebird.dev and fetch it manually. Currently I only see two other solutions to this problem which would be:

  • Store this version code in my backend and then fetch it based on my git tag (10.0.5).
  • Fetch the release aab/apk and read the version code from that.

What would be preferred is that I can just simply say my release version is 10.0.5 which would eliminate all the backend work for me.

Again it could be that I miss a very obvious solution to this.