New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
versionCode is not increased #25
Comments
Hello @IzzySoft Thank you for the issue, i totally forgot to change it 😥 |
Thanks! Then it'll solve itself with the update. And if you remember in the future, the issue won't arise again 😜 |
hahah I'll sure do |
MayI remind you to do it "really sure? Your latest release (from August 25) still confusing my updater, as it still identifies with a version not matching the tag name: tag = v1.1.0, app = v1.0 and |
Well, I doubt it will ever be done. Updates are disabled for your app in my repo until solved. Please give me a ping then so I can check and re-enable them, @MathRoda |
Thanks! Will the next release have a signed APK attached again then? v2.0.0 only has an |
Hi @MathRoda, sad news. I had to remove DashCoin from my repo for now. Not because the APK at the latest release (v2.3.0) still/again does not match its
That exceeds the numbers tolerated in my repo, so I can no longer keep it up there. Should you have a "liberated" build available, I gladly see that I can re-establish it, just let me know then – but for now, with the next sync around 7 pm UTC it will disappear from my repo. Sorry for that. |
While your latest release is tagged v1.1.0, your
build.gradle
still hasversionCode:1
andversionName: "1.0"
. Could you please adjust that for future releases? For some background:versionCode
: what Android uses to tell versions apart. Two APKs with the sameversionCode
are considered being the same. No update notification/offer will be made. So today's update reached my repo, but existing users won't notice 😱versionName
: what the user gets to see. If that stays the same, users can never tell which version they're running. Not only bad for their updates, but also for their issue filings 😉Thanks in advance for taking care!
The text was updated successfully, but these errors were encountered: