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

Version string '5.0.0-beta.4' in info.plist is causing TestFlight upload failure #2797

animeshd opened this Issue Apr 12, 2019 · 2 comments


None yet
2 participants
Copy link

commented Apr 12, 2019

ℹ Please fill out this template when filing an issue.
All lines beginning with an ℹ symbol instruct you with what info we expect. You can delete those lines once you've filled in the info.

Per our *CONTRIBUTING guidelines, we use GitHub for
bugs and feature requests, not general support. Other issues should be opened on Stack Overflow with the tag alamofire.

Please remove this line and everything above it before submitting.

What did you do?

TestFlight upload of my app which imports Alamofire via carthage
github "Alamofire/Alamofire" "5.0.0-beta.4"

What did you expect to happen?

Upload success and app show up on TestFlight as a new version.

What happened instead?

Got error
[11:33:55]: [iTMSTransporter] [2019-04-11 11:33:54 PDT] <main> ERROR: ERROR ITMS-90060: "This bundle is invalid. The value for key CFBundleShortVersionString '5.0.0-beta.4' in the Info.plist file must be a period-separated list of at most three non-negative integers. Please find more information about CFBundleShortVersionString at"

Alamofire Environment

Alamofire version: 5.0.0-beta.4
Xcode version: 10.2
Swift version: 5.0
Platform(s) running Alamofire:
macOS version running Xcode: 10.14.4

Demo Project

ℹ Please link to or upload a project we can download that reproduces the issue.


This comment has been minimized.

Copy link

commented Apr 12, 2019

The problematic value is picked up from [here]


TestFlight upload was working fine for release named 5.0.0.beta.1


This comment has been minimized.

Copy link

commented Apr 12, 2019

#2799 should resolve this issue. I'm going to close this issue out for now. Please direct all further comments to #2799.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.