square / cocoapods-check Goto Github PK

The main pod install command supports a --project-directory=/project/dir/ (as do a lot of the other core ones like update and outdated). It'd be nice if this plugin also supported that option since you could then run the check & install (if needed) from the same paths.

After executing pod check I got this error

Hey there, love the plugin, I'd like to integrate it into the CocoaPods Mac app as a part of CocoaPods/CocoaPods-app#260 - any chance I can get a rubygems of the 0.2.1 release?

Or if you're happy in production with it - a 1.0? 🌴

I ran into a problem running pod check in our CircleCI build environment. I had updated a pod in my local build, and then the /Pods directory on the build server was out of date (had the wrong version of the pod in the Manifest.lock).

If I did a diff on the two files, I had a different version number on the pod and a different checksum. If I ran pod check (v1.0.0 and cocoapods v1.0.1) it said Pods are up to date. My current work around is to do the diff myself, and run pod install if the files differ - it looks to me like this should be handled in /lib/pod/command/check.rb but it doesn't seem to be working.

This issue might be related to #1 but it also relates to actual version mismatches, not just the checksum.

React Native recently introduced unimodules which automatically installs the required Pods from node_modules for a project. It seems like this causes pod check to fail even though pod install works perfectly fine. Check the ios/Podfile configuration here: https://docs.expo.io/bare/installing-unimodules

% pod check --verbose

[!] Invalid `React-Fabric.podspec` file: No such file or directory @ rb_sysopen - ../scripts/generate-rncore.sh.

 #  from /Users/admin/Documents/Repos/thefit-app/node_modules/react-native/ReactCommon/React-Fabric.podspec:33
 #  -------------------------------------------
 #    s.source                 = source
 >    s.prepare_command        = File.read("../scripts/generate-rncore.sh")
 #    s.source_files           = "dummyFile.cpp"
 #  -------------------------------------------

Has anyone encountered this, any tips on how we could solve it?

For folks that have cocoapods installed via homebrew instead of as a ruby gem directly it'd be nice to be able to use this as well

Hi there, super excited to try this plug-in but I'm having a slight issue, that seems related to closed issue #6. I'm receiving "Unknown command: 'check'" after install with cocoapods v1.5.3 installed.

Any suggestions? Many thanks for any and all help!

Environment:

• Any Xcode
• Xcode project with Cocoapods integrated

Steps:

1. Run "pod check" command,
2. ensure it returns successfully
3. Create an ad-hoc configuration in Xcode project
4. Run pod check once again

ER:
pod check fails, because new AdHoc configuration requires new Pods-AppName.adhoc.xcconfig file to be generated and integrated into the target.

AR:
"pod check" completes successfully.

I just ran into a situation where the Pod versions were all the same, but the checksums were different:

offa:~/Development/register % diff Podfile.lock Pods/Manifest.lock
490c490
< PODFILE CHECKSUM: e52d0cabb3d882c9d1173c646d2593d38d400452

---
> PODFILE CHECKSUM: b0407649c4f51e74c0a64aae5153b594c2327362

The build failed with 'sandbox not in sync', but pod check didn't report any differences. I guess the right behavior is to report this as a difference.

Noticed, that without --ignore-dev-pods pod check seems to always generate the output indicating that ~React-Codegen is ought to be updated, even when subsequent pod install produces no changes to Podfile.lock. I can get it to ignore --ignore-dev-pods but since its a RN project, will ignore pretty much all of the auto-linked pods, which are almost all of our pods.

This can be because React-Codegen is, well, autogenerated. Is there any option to ignore a particular pod from check?