-
Notifications
You must be signed in to change notification settings - Fork 53
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
please increase versionCode #47
Comments
@IzzySoft Sure man! Thanks for the info |
Gladly given! Now your 3rd release was made, and |
Haha Sorry my bad 🤣 . Every time I forgot to update the version code. Thanks for the reminder 👍 |
Signed-off-by: Sanju S <spikeysanju98@gmail.com>
@IzzySoft It was fixed in the latest commit buddy ✅ . Thanks for the reminder. Have a great day! |
🤣 Please reopen again, you once more forgot defaultConfig {
applicationId "thecodemonks.org.nottzapp"
minSdkVersion 21
targetSdkVersion 30
versionCode 1
versionName "1.3.3" Remember:
|
@Spikeysanju my updater still gives me daily alerts because of the |
@Spikeysanju any chance? Btw it's irritating that the APK at release tag v1.3 still identifies as 0.1.3 😉 |
@Spikeysanju again you forgot: my updater just fetched a new version last night (we're at 1.4 now), and it still shows Maybe one year after reporting, can we get this finally fixed, please? Thanks! |
Thanks! That one looks good. Just downloaded it manually (as my updater was now fooled by the fact it already had processed that tag) and checked. Will become visible in about 1.5h from now (with the next sync). Will it now work well for the next releases, too? 😃 |
Yeah sure, I hope I will remember this for sure next time 😄. Have a great day buddy! |
You too, friend! And should you forget again, I'll come and remind you 😆 |
could you please increase
versionCode
when making a new release? That's what Android tells the versions apart by – so as today's release still hasversionCode: 1
Android won't consider it as an update for those having the previous version installed. Thanks!The text was updated successfully, but these errors were encountered: