Skip to content
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

[Android] In-app build version and package manifest don't match #10837

Open
Leopard20 opened this issue Mar 29, 2018 · 5 comments
Open

[Android] In-app build version and package manifest don't match #10837

Leopard20 opened this issue Mar 29, 2018 · 5 comments

Comments

@Leopard20
Copy link
Contributor

Leopard20 commented Mar 29, 2018

Not a big issue, but I don't know why the in-app build version doesn't match the actual version of the package.
For example, build 804 version in AndroidManifest.xml is 1.5.4-790 instead of 1.5.4-804.
But the in-app reported version is 1.5.4-804.
It's a bit confusing to some people, don't you think?

@Leopard20 Leopard20 changed the title [Android] In-app build version and package manifest don't match [Android] In-app build version and package manifest version don't match Mar 29, 2018
@Leopard20 Leopard20 changed the title [Android] In-app build version and package manifest version don't match [Android] In-app build version and package manifest don't match Mar 29, 2018
@hrydgard
Copy link
Owner

Seems like some artifact of how the buildbot checks out the repo, what do you think @Orphis ?

@Florin9doi
Copy link
Contributor

Florin9doi commented Oct 6, 2018

In game version name uses git describe --always (git-version.cmake >> git-version.cpp)
and AndroidManifest uses androidGitVersion.
Those 2 ways of getting version name produces different results:

ppsspp> git describe --always
v1.6.3-542-g208b0d8a4

ppsspp> gradlew --quiet androidGitVersion
Overriding Android Version Name, Code: 1.6.3-531-0008-dirty 16030531
androidGitVersion.name  1.6.3-531-0008-dirty
androidGitVersion.code  16030531

@unknownbrackets
Copy link
Collaborator

That's weird, maybe it's ignoring certain commits in its counting? The code looks like it should skip that without onlyIn, though.

Ultimately, we want the build version to be the same across all platforms, so I'd assert that androidGitVersion is the one that is "wrong" here.

-[Unknown]

@Florin9doi
Copy link
Contributor

Florin9doi commented Oct 6, 2018

I'm thinking about the commits made before tag, but merged after tag.
For the last few apks the difference is constant: 11

@hrydgard
Copy link
Owner

I'm pushing this one forward, not critical enough (but definitely annoying!)

@hrydgard hrydgard modified the milestones: v1.8.0, v1.9.0 Feb 25, 2019
@hrydgard hrydgard modified the milestones: v1.9.0, v1.10.0 Aug 22, 2019
@hrydgard hrydgard modified the milestones: v1.10.0, v1.11.0 Apr 26, 2020
@hrydgard hrydgard modified the milestones: v1.11.0, Future Aug 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants