You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just wondering: I meanwhile have 3 APKs claiming to be v0.1.3 and versionCode: 726103, released a week apart in sequence. Is this intended? If versionCode remains unchanged, Android does not recognize the APK being an update (but considers it the same version). Also it might be confusing should you get bug reports: how can you tell which version they apply to?
While talking releases: Did you plan to tag your releases and attach the corresponding APKs there? Would 1) make them easier to detect, 2) allow you relating "release notes", and 3) help you keeping the repo "slim" as you can avoid the "binary history" of the APKs 😉
The text was updated successfully, but these errors were encountered:
Ok, you right, I'll do it when I find some time this week, I will organize it little bit better . Actually I will update to higher version, planning to add Shared Preferences in order to store settings for the app so after updates everything stays as it was before update.
Just wondering: I meanwhile have 3 APKs claiming to be v0.1.3 and
versionCode: 726103
, released a week apart in sequence. Is this intended? IfversionCode
remains unchanged, Android does not recognize the APK being an update (but considers it the same version). Also it might be confusing should you get bug reports: how can you tell which version they apply to?While talking releases: Did you plan to tag your releases and attach the corresponding APKs there? Would 1) make them easier to detect, 2) allow you relating "release notes", and 3) help you keeping the repo "slim" as you can avoid the "binary history" of the APKs 😉
The text was updated successfully, but these errors were encountered: