CocoaPods/CocoaPods · error · Informative
No podspec found for `#{name}` in #{podspec}
Error message
No podspec found for `#{name}` in #{podspec} What it means
Error "No podspec found for `#{name}` in #{podspec}" thrown in CocoaPods/CocoaPods.
Source
Thrown at lib/cocoapods/sandbox.rb:293
# @param [String, Pathname, Specification] podspec
# The contents of the specification (String) or the path to a
# podspec file (Pathname).
#
# @return [void]
#
#
def store_podspec(name, podspec, _external_source = false, json = false)
file_name = json ? "#{name}.podspec.json" : "#{name}.podspec"
output_path = specifications_root + file_name
spec =
case podspec
when String
Sandbox.update_changed_file(output_path, podspec)
Specification.from_file(output_path)
when Pathname
unless podspec.exist?
raise Informative, "No podspec found for `#{name}` in #{podspec}"
end
FileUtils.copy(podspec, output_path)
Specification.from_file(podspec)
when Specification
raise ArgumentError, 'can only store Specification objects as json' unless json
Sandbox.update_changed_file(output_path, podspec.to_pretty_json)
podspec.dup
else
raise ArgumentError, "Unknown type for podspec: #{podspec.inspect}"
end
# we force the file to be the file in the sandbox, so specs that have been serialized to
# json maintain a consistent checksum.
# this is safe to do because `spec` is always a clean instance
spec.defined_in_file = output_path
unless spec.name == name
raise Informative, "The name of the given podspec `#{spec.name}` doesn't match the expected one `#{name}`"View on GitHub (pinned to b80e113e28)
When it happens
Trigger: Thrown at lib/cocoapods/sandbox.rb:293 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of CocoaPods/CocoaPods@b80e113e28 (2026-08-21).
Data as JSON: /api/errors/88f1e054d68d35dc.
Report an issue: GitHub.