[GH-ISSUE #41] please increase versionCode with each release #32

Open
opened 2026-02-26 12:35:16 +03:00 by kerem · 4 comments
Owner

Originally created by @IzzySoft on GitHub (Jul 14, 2024).
Original GitHub issue: https://github.com/cbeuw/Cloak-android/issues/41

Looks like you forgot to increase versionCode with the latest release – like the previous one, it still uses 22 there. versionCode is what Android uses internally to tell versions apart – so whoever has the previous release installed won't get an update notification for the current one as Android will think it is already there.

Thanks in advance!

Originally created by @IzzySoft on GitHub (Jul 14, 2024). Original GitHub issue: https://github.com/cbeuw/Cloak-android/issues/41 Looks like you forgot to increase `versionCode` with the latest release – like the previous one, it still uses `22` there. `versionCode` is what Android uses internally to tell versions apart – so whoever has the previous release installed won't get an update notification for the current one as Android will think it is already there. Thanks in advance!
Author
Owner

@linsui commented on GitHub (Jul 17, 2024):

It only has changes for F-Droid and reproducible. :) But I guess you can use fastlane metadata in this repo now.

<!-- gh-comment-id:2233060773 --> @linsui commented on GitHub (Jul 17, 2024): It only has changes for F-Droid and reproducible. :) But I guess you can use fastlane metadata in this repo now.
Author
Owner

@IzzySoft commented on GitHub (Jul 17, 2024):

What does that have to do with versionCode, @linsui? A new release does not necessarily need Fastlane – but it must have the versionCode increased – which cannot be "healed" via Fastlane 😜

That said: look at full_description.txt here and compare it with the description at IoD, then you know why I have it disabled. Hint: fulldesc lacks the details 😉

<!-- gh-comment-id:2233201333 --> @IzzySoft commented on GitHub (Jul 17, 2024): What does that have to do with `versionCode`, @linsui? A new release does not necessarily need Fastlane – but it must have the `versionCode` increased – which cannot be "healed" via Fastlane :stuck_out_tongue_winking_eye: That said: look at `full_description.txt` here and compare it with the description at IoD, then you know why I have it disabled. Hint: fulldesc lacks the details :wink:
Author
Owner

@linsui commented on GitHub (Jul 17, 2024):

What does that have to do with versionCode, @linsui? A new release does not necessarily need Fastlane – but it must have the versionCode increased – which cannot be "healed" via Fastlane 😜

You can ignore the new tags since it doesn't have any new features but only some build script tweak for reproducible build. :)

That said: look at full_description.txt here and compare it with the description at IoD, then you know why I have it disabled. Hint: fulldesc lacks the details 😉

So would you like to PR your version? :)

<!-- gh-comment-id:2233243000 --> @linsui commented on GitHub (Jul 17, 2024): > What does that have to do with versionCode, @linsui? A new release does not necessarily need Fastlane – but it must have the versionCode increased – which cannot be "healed" via Fastlane 😜 You can ignore the new tags since it doesn't have any new features but only some build script tweak for reproducible build. :) > That said: look at full_description.txt here and compare it with the description at IoD, then you know why I have it disabled. Hint: fulldesc lacks the details 😉 So would you like to PR your version? :)
Author
Owner

@IzzySoft commented on GitHub (Jul 17, 2024):

You can ignore the new tags

Does F-Droid's updater also ignore tags which correspond to the definition in the YAML now? 😉 But let's drop this topic, linsui – that was not advice to you but rather to Andy.

So would you like to PR your version? :)

If it's welcome, of course. So @cbeuw do you want to have it? See here for what it entails.

<!-- gh-comment-id:2233755882 --> @IzzySoft commented on GitHub (Jul 17, 2024): > You can ignore the new tags Does F-Droid's updater also ignore tags which correspond to the definition in the YAML now? :wink: But let's drop this topic, linsui – that was not advice to you but rather to Andy. > So would you like to PR your version? :) If it's welcome, of course. So @cbeuw do you want to have it? [See here](https://apt.izzysoft.de/packages/com.github.shadowsocks.plugin.ck_client) for what it entails.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Cloak-android#32
No description provided.