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

Extracting version numbers breaks on Xcode 11 #31

Open
idrougge opened this issue Nov 5, 2019 · 2 comments
Open

Extracting version numbers breaks on Xcode 11 #31

idrougge opened this issue Nov 5, 2019 · 2 comments
Labels
type: bug Something isn't working

Comments

@idrougge
Copy link

idrougge commented Nov 5, 2019

After upgrading to to version 11, Xcode moved the version numbers from Info.plist into the project file. This leads to this new confusing header from SwiftInfo:

SwiftInfo results for SuperApp $(MARKETING_VERSION) ($(CURRENT_PROJECT_VERSION)) - Release:

@rockbruno
Copy link
Owner

That really sucks... I haven't seen this because we keep our versions in a separate file, but for now, a way to avoid this is to parse and send the version values manually in the project info:

let projectInfo = ProjectInfo(xcodeproj: "./iFood/iFood.xcodeproj",
                              target: "iFoodApp",
                              configuration: isInPullRequestMode ? "Testing": "Release",
                              plistPath: "./iFood/Resources/Info.plist",
                              versionString: versionString,
                              buildNumber: buildNumber)

@rogerluan rogerluan added the type: bug Something isn't working label Jun 17, 2020
@rogerluan
Copy link
Contributor

We also keep the app version and build number in a separate file, but SwiftInfo could do this heavy lifting for the user probably. In our case, we use an identifier in those fields, and set a value in INFOPLIST_PREFIX_HEADER in the Build Settings pointing to the file where those identifiers are kept. SwiftInfo could read this value (a filepath), open the file and look for the identifiers, to find its value 😇
Just not sure if this fix would be "generic enough" - it'd work in our project, but idk if other projects have other types of setup that don't use INFOPLIST_PREFIX_HEADER 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants