Unrecognized `swift_version` keypod spec lint validation error due to Xcode errorsCocoapods - podspec validates but can't be pushed to repoXcode 8 Beta 3 Use Legacy Swift issuexcodebuild: Returned an unsuccessful exit codeThe spec did not pass validation, due to 1 errorCocoa pod installation error: “ The target overrides the SWIFT_VERSION build setting ”publish pod repo encounter “xcodebuild: Returned an unsuccessful exit code”How to publish new official pod version?Why Spec lint throwing error Xcode build failed: Returned an unsuccesful exit code?How to create a custom pod that includes .framework static libraries?
Why does the weaker C–H bond have a higher wavenumber than the C=O bond?
Normalized Malbolge to Malbolge translator
Inspiration for failed idea?
What is the sound/audio equivalent of "unsightly"?
Can I lend a small amount of my own money to a bank at the federal funds rate?
Is there a better way to use C# dictionaries than TryGetValue?
Employing a contractor proving difficult
Is there a way to tell what frequency I need a PWM to be?
Is this position a forced win for Black after move 14?
What does GDPR mean to myself regarding my own data?
What checks exist against overuse of presidential pardons in the USA?
Are spot colors limited and why CMYK mix is not treated same as spot color mix?
How to prevent a hosting company from accessing a VM's encryption keys?
Looking for a plural noun related to ‘fulcrum’ or ‘pivot’ that denotes multiple things as crucial to success
Why can't you say don't instead of won't?
Does Mirrorwing Dragon's ability trigger when redirects are involved?
Drawing probabilities on a simplex in TikZ
How could a self contained organic body propel itself in space
In Endgame, wouldn't Stark have remembered Hulk busting out of the stairwell?
Why does AM radio react to IR remote?
Is there an in-universe explanation given to the senior Imperial Navy Officers as to why Darth Vader serves Emperor Palpatine?
Count the number of triangles
Spicing up a moment of peace
Cutting numbers into a specific decimals
Unrecognized `swift_version` key
pod spec lint validation error due to Xcode errorsCocoapods - podspec validates but can't be pushed to repoXcode 8 Beta 3 Use Legacy Swift issuexcodebuild: Returned an unsuccessful exit codeThe spec did not pass validation, due to 1 errorCocoa pod installation error: “ The target overrides the SWIFT_VERSION build setting ”publish pod repo encounter “xcodebuild: Returned an unsuccessful exit code”How to publish new official pod version?Why Spec lint throwing error Xcode build failed: Returned an unsuccesful exit code?How to create a custom pod that includes .framework static libraries?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I can’t push a new version of my pod to the CocoaPods specs repository.
Running pod trunk push MyPod.podspec results in the following error:
[!] The Pod Specification did not pass validation.
The following validation failed:
- Warnings: Unrecognized `swift_version` key.
Here’s my podspec:
Pod::Spec.new do |spec|
spec.name = "MyPod"
spec.version = "0.1.1"
spec.summary = "[REDACTED]"
spec.homepage = "[REDACTED]"
spec.license = "Apache License, version 2"
spec.author = "[REDACTED]"
spec.social_media_url = "[REDACTED]"
spec.module_name = "MyPod"
spec.swift_version = "5.0"
spec.platform = :ios, "8.0"
spec.source = :git => "https://github.com/[REDACTED].git", :tag => "v#spec.version"
spec.source_files = "MyPod/**/*.h,m,swift"
end
What am I doing wrong?
I first noticed these errors before updating to Swift 5 and Xcode 10.2.
swift cocoapods podspec
asked Mar 27 at 21:15
Yakov M.Yakov M.
2113 silver badges12 bronze badges
add a comment |
I can’t push a new version of my pod to the CocoaPods specs repository.
Running pod trunk push MyPod.podspec results in the following error:
[!] The Pod Specification did not pass validation.
The following validation failed:
- Warnings: Unrecognized `swift_version` key.
Here’s my podspec:
Pod::Spec.new do |spec|
spec.name = "MyPod"
spec.version = "0.1.1"
spec.summary = "[REDACTED]"
spec.homepage = "[REDACTED]"
spec.license = "Apache License, version 2"
spec.author = "[REDACTED]"
spec.social_media_url = "[REDACTED]"
spec.module_name = "MyPod"
spec.swift_version = "5.0"
spec.platform = :ios, "8.0"
spec.source = :git => "https://github.com/[REDACTED].git", :tag => "v#spec.version"
spec.source_files = "MyPod/**/*.h,m,swift"
end
What am I doing wrong?
I first noticed these errors before updating to Swift 5 and Xcode 10.2.
swift cocoapods podspec
asked Mar 27 at 21:15
Yakov M.Yakov M.
2113 silver badges12 bronze badges
add a comment |
I can’t push a new version of my pod to the CocoaPods specs repository.
Running pod trunk push MyPod.podspec results in the following error:
[!] The Pod Specification did not pass validation.
The following validation failed:
- Warnings: Unrecognized `swift_version` key.
Here’s my podspec:
Pod::Spec.new do |spec|
spec.name = "MyPod"
spec.version = "0.1.1"
spec.summary = "[REDACTED]"
spec.homepage = "[REDACTED]"
spec.license = "Apache License, version 2"
spec.author = "[REDACTED]"
spec.social_media_url = "[REDACTED]"
spec.module_name = "MyPod"
spec.swift_version = "5.0"
spec.platform = :ios, "8.0"
spec.source = :git => "https://github.com/[REDACTED].git", :tag => "v#spec.version"
spec.source_files = "MyPod/**/*.h,m,swift"
end
What am I doing wrong?
I first noticed these errors before updating to Swift 5 and Xcode 10.2.
swift cocoapods podspec
asked Mar 27 at 21:15
Yakov M.Yakov M.
2113 silver badges12 bronze badges
I can’t push a new version of my pod to the CocoaPods specs repository.
Running pod trunk push MyPod.podspec results in the following error:
[!] The Pod Specification did not pass validation.
The following validation failed:
- Warnings: Unrecognized `swift_version` key.
Here’s my podspec:
Pod::Spec.new do |spec|
spec.name = "MyPod"
spec.version = "0.1.1"
spec.summary = "[REDACTED]"
spec.homepage = "[REDACTED]"
spec.license = "Apache License, version 2"
spec.author = "[REDACTED]"
spec.social_media_url = "[REDACTED]"
spec.module_name = "MyPod"
spec.swift_version = "5.0"
spec.platform = :ios, "8.0"
spec.source = :git => "https://github.com/[REDACTED].git", :tag => "v#spec.version"
spec.source_files = "MyPod/**/*.h,m,swift"
end
What am I doing wrong?
I first noticed these errors before updating to Swift 5 and Xcode 10.2.
swift cocoapods podspec
swift cocoapods podspec
asked Mar 27 at 21:15
Yakov M.Yakov M.
2113 silver badges12 bronze badges
asked Mar 27 at 21:15
Yakov M.Yakov M.
2113 silver badges12 bronze badges
asked Mar 27 at 21:15
Yakov M.Yakov M.
2113 silver badges12 bronze badges
asked Mar 27 at 21:15
Yakov M.Yakov M.
2113 silver badges12 bronze badges
asked Mar 27 at 21:15
Yakov M.Yakov M.
2113 silver badges12 bronze badges
2113 silver badges12 bronze badges
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
It seems to be a server-side bug. It’s been reported on GitHub.
However, since it’s a warning, not an error (despite it’s in red font color, which is confusing), it can be ignored with the --allow-warnings argument.
answered Mar 27 at 21:47
Yakov M.Yakov M.
2113 silver badges12 bronze badges
add a comment |
Summary, to update a pod:
Update the version and the tag in podspec beforehand
Commit, push code to git
Create new tag with the current code, make sure it's the same tag as the one in podspec
git tag 0.1.1
git push origin 0.1.1
Call pod spec lint to check and pod trunk push to update it on repo master list
pod lib lint YourSDK.podspec
pod trunk push YourSDK.podspec
It appears that your podfile is using the tag v0.1.1, however the tag in your repository is 0.1.1 without the v. This would also cause linting to fail.
answered Mar 27 at 21:30
Abbas TorabiAbbas Torabi
2087 bronze badges
No, it’s not the case: “v” in version number is present both in the podspec and in the repo. Besides, the lint command says the pod passed validation; however, pushing to the trunk fails.
– Yakov M.
Mar 27 at 21:42
that's warning. so when you trunk push, allow warnings: pod trunk push MyPod.podspec --allow-warnings hope to help you
– Abbas Torabi
Mar 27 at 21:54
Ah, it’s a warning, indeed. Thank you @AbbasTorabi. I was confused by the red font color, and though it was an error which can’t be ignored by passing the--allow-warningsargument.
– Yakov M.
Mar 27 at 22:38
@YakovM. I'm glad that solved. you're welcome man
– Abbas Torabi
Mar 27 at 22:41
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55386569%2funrecognized-swift-version-key%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
It seems to be a server-side bug. It’s been reported on GitHub.
However, since it’s a warning, not an error (despite it’s in red font color, which is confusing), it can be ignored with the --allow-warnings argument.
answered Mar 27 at 21:47
Yakov M.Yakov M.
2113 silver badges12 bronze badges
add a comment |
It seems to be a server-side bug. It’s been reported on GitHub.
However, since it’s a warning, not an error (despite it’s in red font color, which is confusing), it can be ignored with the --allow-warnings argument.
answered Mar 27 at 21:47
Yakov M.Yakov M.
2113 silver badges12 bronze badges
add a comment |
It seems to be a server-side bug. It’s been reported on GitHub.
However, since it’s a warning, not an error (despite it’s in red font color, which is confusing), it can be ignored with the --allow-warnings argument.
answered Mar 27 at 21:47
Yakov M.Yakov M.
2113 silver badges12 bronze badges
It seems to be a server-side bug. It’s been reported on GitHub.
However, since it’s a warning, not an error (despite it’s in red font color, which is confusing), it can be ignored with the --allow-warnings argument.
answered Mar 27 at 21:47
Yakov M.Yakov M.
2113 silver badges12 bronze badges
edited Mar 28 at 6:10
answered Mar 27 at 21:47
Yakov M.Yakov M.
2113 silver badges12 bronze badges
answered Mar 27 at 21:47
Yakov M.Yakov M.
2113 silver badges12 bronze badges
answered Mar 27 at 21:47
Yakov M.Yakov M.
2113 silver badges12 bronze badges
2113 silver badges12 bronze badges
add a comment |
add a comment |
Summary, to update a pod:
Update the version and the tag in podspec beforehand
Commit, push code to git
Create new tag with the current code, make sure it's the same tag as the one in podspec
git tag 0.1.1
git push origin 0.1.1
Call pod spec lint to check and pod trunk push to update it on repo master list
pod lib lint YourSDK.podspec
pod trunk push YourSDK.podspec
It appears that your podfile is using the tag v0.1.1, however the tag in your repository is 0.1.1 without the v. This would also cause linting to fail.
answered Mar 27 at 21:30
Abbas TorabiAbbas Torabi
2087 bronze badges
No, it’s not the case: “v” in version number is present both in the podspec and in the repo. Besides, the lint command says the pod passed validation; however, pushing to the trunk fails.
– Yakov M.
Mar 27 at 21:42
that's warning. so when you trunk push, allow warnings: pod trunk push MyPod.podspec --allow-warnings hope to help you
– Abbas Torabi
Mar 27 at 21:54
Ah, it’s a warning, indeed. Thank you @AbbasTorabi. I was confused by the red font color, and though it was an error which can’t be ignored by passing the--allow-warningsargument.
– Yakov M.
Mar 27 at 22:38
@YakovM. I'm glad that solved. you're welcome man
– Abbas Torabi
Mar 27 at 22:41
add a comment |
Summary, to update a pod:
Update the version and the tag in podspec beforehand
Commit, push code to git
Create new tag with the current code, make sure it's the same tag as the one in podspec
git tag 0.1.1
git push origin 0.1.1
Call pod spec lint to check and pod trunk push to update it on repo master list
pod lib lint YourSDK.podspec
pod trunk push YourSDK.podspec
It appears that your podfile is using the tag v0.1.1, however the tag in your repository is 0.1.1 without the v. This would also cause linting to fail.
answered Mar 27 at 21:30
Abbas TorabiAbbas Torabi
2087 bronze badges
No, it’s not the case: “v” in version number is present both in the podspec and in the repo. Besides, the lint command says the pod passed validation; however, pushing to the trunk fails.
– Yakov M.
Mar 27 at 21:42
that's warning. so when you trunk push, allow warnings: pod trunk push MyPod.podspec --allow-warnings hope to help you
– Abbas Torabi
Mar 27 at 21:54
Ah, it’s a warning, indeed. Thank you @AbbasTorabi. I was confused by the red font color, and though it was an error which can’t be ignored by passing the--allow-warningsargument.
– Yakov M.
Mar 27 at 22:38
@YakovM. I'm glad that solved. you're welcome man
– Abbas Torabi
Mar 27 at 22:41
add a comment |
Summary, to update a pod:
Update the version and the tag in podspec beforehand
Commit, push code to git
Create new tag with the current code, make sure it's the same tag as the one in podspec
git tag 0.1.1
git push origin 0.1.1
Call pod spec lint to check and pod trunk push to update it on repo master list
pod lib lint YourSDK.podspec
pod trunk push YourSDK.podspec
It appears that your podfile is using the tag v0.1.1, however the tag in your repository is 0.1.1 without the v. This would also cause linting to fail.
answered Mar 27 at 21:30
Abbas TorabiAbbas Torabi
2087 bronze badges
Summary, to update a pod:
Update the version and the tag in podspec beforehand
Commit, push code to git
Create new tag with the current code, make sure it's the same tag as the one in podspec
git tag 0.1.1
git push origin 0.1.1
Call pod spec lint to check and pod trunk push to update it on repo master list
pod lib lint YourSDK.podspec
pod trunk push YourSDK.podspec
It appears that your podfile is using the tag v0.1.1, however the tag in your repository is 0.1.1 without the v. This would also cause linting to fail.
answered Mar 27 at 21:30
Abbas TorabiAbbas Torabi
2087 bronze badges
answered Mar 27 at 21:30
Abbas TorabiAbbas Torabi
2087 bronze badges
answered Mar 27 at 21:30
Abbas TorabiAbbas Torabi
2087 bronze badges
answered Mar 27 at 21:30
Abbas TorabiAbbas Torabi
2087 bronze badges
2087 bronze badges
No, it’s not the case: “v” in version number is present both in the podspec and in the repo. Besides, the lint command says the pod passed validation; however, pushing to the trunk fails.
– Yakov M.
Mar 27 at 21:42
that's warning. so when you trunk push, allow warnings: pod trunk push MyPod.podspec --allow-warnings hope to help you
– Abbas Torabi
Mar 27 at 21:54
Ah, it’s a warning, indeed. Thank you @AbbasTorabi. I was confused by the red font color, and though it was an error which can’t be ignored by passing the--allow-warningsargument.
– Yakov M.
Mar 27 at 22:38
@YakovM. I'm glad that solved. you're welcome man
– Abbas Torabi
Mar 27 at 22:41
add a comment |
No, it’s not the case: “v” in version number is present both in the podspec and in the repo. Besides, the lint command says the pod passed validation; however, pushing to the trunk fails.
– Yakov M.
Mar 27 at 21:42
that's warning. so when you trunk push, allow warnings: pod trunk push MyPod.podspec --allow-warnings hope to help you
– Abbas Torabi
Mar 27 at 21:54
Ah, it’s a warning, indeed. Thank you @AbbasTorabi. I was confused by the red font color, and though it was an error which can’t be ignored by passing the--allow-warningsargument.
– Yakov M.
Mar 27 at 22:38
@YakovM. I'm glad that solved. you're welcome man
– Abbas Torabi
Mar 27 at 22:41
No, it’s not the case: “v” in version number is present both in the podspec and in the repo. Besides, the lint command says the pod passed validation; however, pushing to the trunk fails.
– Yakov M.
Mar 27 at 21:42
No, it’s not the case: “v” in version number is present both in the podspec and in the repo. Besides, the lint command says the pod passed validation; however, pushing to the trunk fails.
– Yakov M.
Mar 27 at 21:42
that's warning. so when you trunk push, allow warnings: pod trunk push MyPod.podspec --allow-warnings hope to help you
– Abbas Torabi
Mar 27 at 21:54
that's warning. so when you trunk push, allow warnings: pod trunk push MyPod.podspec --allow-warnings hope to help you
– Abbas Torabi
Mar 27 at 21:54
Ah, it’s a warning, indeed. Thank you @AbbasTorabi. I was confused by the red font color, and though it was an error which can’t be ignored by passing the
--allow-warnings argument.– Yakov M.
Mar 27 at 22:38
Ah, it’s a warning, indeed. Thank you @AbbasTorabi. I was confused by the red font color, and though it was an error which can’t be ignored by passing the
--allow-warnings argument.– Yakov M.
Mar 27 at 22:38
@YakovM. I'm glad that solved. you're welcome man
– Abbas Torabi
Mar 27 at 22:41
@YakovM. I'm glad that solved. you're welcome man
– Abbas Torabi
Mar 27 at 22:41
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55386569%2funrecognized-swift-version-key%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
