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.

Sign up for GitHub

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

Jump to bottom

Is there a way to make the version and build number in macos/Runner.xcworkspace automatically match the version and build number from pubspec.yaml? #148407

Closed
stephane-archer opened this issue May 15, 2024 · 3 comments
Closed

Is there a way to make the version and build number in macos/Runner.xcworkspace automatically match the version and build number from pubspec.yaml? #148407

stephane-archer opened this issue May 15, 2024 · 3 comments
Labels
r: solved Issue is closed as solved

Comments

@stephane-archer
Copy link

Use case

Is there a way to make the version and build number in macos/Runner.xcworkspace automatically match the version and build number from pubspec.yaml?

Proposal

Is there a way to make the version and build number in macos/Runner.xcworkspace automatically match the version and build number from pubspec.yaml?
@darshankawar darshankawar added the in triage Presently being triaged by the triage team label May 16, 2024
@darshankawar
Copy link
Member

@stephane-archer
The version and build seems to be fetched from info.plist file currently, but not sure if that is related to pubspec.yaml or from local.properties file wherein flutter.versionName and versionCode are being passed that you can check and confirm ?

@darshankawar darshankawar added the waiting for customer response The Flutter team cannot make further progress on this issue until the original reporter responds label May 16, 2024
@stephane-archer
Copy link
Author

from what I can observe if you leave the version and build number blank in macos/Runner.xcworkspace, the pubspec.yaml version and build number are used.

@github-actions github-actions bot removed the waiting for customer response The Flutter team cannot make further progress on this issue until the original reporter responds label May 16, 2024
@darshankawar darshankawar added r: solved Issue is closed as solved and removed in triage Presently being triaged by the triage team labels May 17, 2024
@github-actions GitHub Actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 31, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
r: solved Issue is closed as solved
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stephane-archer @darshankawar