Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

pod repo lint error: [!] An unexpected version directory `<a dir>` was encountered for the `<Parent Dir>` Pod in the `<Parent Dir>` repository

I am tryin to lint my pod spec and getting the following error.

[!] An unexpected version directory 'ios' was encountered for the 'Classes' Pod in the 'Classes' repository.

My source folders are set as follows:

Classes - ios - osx

Podspec has source files as:

s.source_files = 'Classes/**/*.*'

Any ideas what is causing this error?

like image 210
Ants Avatar asked Jun 16 '14 01:06

Ants


People also ask

What happens if no pod_names are specified?

If no POD_NAMES are specified, it updates all the Pods, ignoring the contents of the Podfile.lock. This command is reserved for the update of dependencies; pod install should be used to install changes to the Podfile. The sources from which to update dependent pods. Multiple sources must be comma-delimited. Pods to exclude during update.

What happens if I delete a pod version?

WARNING: It is generally considered bad behavior to remove versions of a Pod that others are depending on! Please consider using the deprecate command instead. Deletes the specified pod version from trunk and the master specs repo. Once deleted, this version can never be pushed again.

What are the command to force a pod Repo update?

Commands --repo-update Force running pod repo update before ins ... --deployment Disallow any changes to the Podfile or t ... --clean-install Ignore the contents of the project cache ... --project-directory=/project/dir/ The path to the root of the project dire ...

What happens if path is not provided for a podspec?

If PATH is not provided, defaults to the current directory. Before pushing the podspec to cocoapods.org, this will perform a local lint of the podspec, including a build of the library.


1 Answers

OK I was having a bad day. Should have been using:

pod spec lint .

like image 71
Ants Avatar answered Sep 21 '22 22:09

Ants