Relevant knowledge points of cocoapods

pod technological process

pod cache ~/Library/Caches/CocoaPods

Search and install Cocoapods A library on , The general implementation process is ：
1、 from search_index.json Find the corresponding version of the library in podspec File and download it to Specs/Release In the folder
2、 According to the podspec In the document source Medium git Address , Download the corresponding version of the library to Pods/Release In the folder
Push the locally developed libraries to Cocoapods Warehouse time , The general implementation process is ：
1、 perform pod spec lint XXX.podspec when , If you do not rely on other libraries , Will be in Specs/External The library in the file generates the corresponding version of podsepc file , And change the file name hash
2、 Will be podspec Download the corresponding library in the file to Pods/External In the folder
3、 If the published library depends on other Cocoapods When publishing libraries on , Will depend on the library podspec Download the file to Specs/Release In the folder , The dependent libraries are downloaded to Pods/Release In the folder

pod install Operation principle analysis

1. analysis dependency
2. Compare local Pod and podfile.lock The version in the file , If inconsistent, it will indicate that there is a risk .
3. contrast podfile Is there a change ,add/remove pod rely on
4. If there is , Two lists will be generated , One is need add Of pods, One is need remove Of pods.
5. If there is remove Of , Delete remove Of pods（ Will delete podfile.lock The version in depends on ）.
6. Add what you need pods rely on
7. here , If it's regular CocoaPods library ( be based on git), Will go first ：
8. Spec Find the corresponding Pods Folder
9. Find the corresponding tag
10. git clone Down the code and copy To Pod Under the table of contents
11. function pre-install hook
12. Generate Pod Project
13. Will be pod Add files to the project
14. Add corresponding framework、.a library 、bundle etc.
15. Link header file , Generate Target
16. function post-install hook
17. Generate podfile.lock , Then make a copy of the file mainfest.lock And put it in Pod In the folder .（ If appear The sandbox is not sync with the podfile.lock Such mistake , said manifest.lock and podfile.lock The documents are inconsistent ）, At this time, it is generally necessary to re run pod install command .
18. Configure the original project file (add build phase)
19. Added Embed Pods Frameworks
20. Added Copy Pod Resources

//  -  among ,pre-install hook and post-install hook It can be understood as a callback function , Is in podfile Li for install Before or after （ The project is generated but has not been written to disk ） Executable logic , The logic is ：
// -  Be careful ：pod install Give priority to  Podfile  Version information specified in , Second, follow  Podfile.lock  Install the corresponding dependent libraries according to the version information specified in .

pre_install do |installer|
    #  Do something before installation hook
end
post_install do |installer|
    #  Do something after installation hook
end

pod Operations in the command

1. Use pod update When ordered , Will podfile Copy the folder in the address of the source in to ~/.cocoapods/repos in ;
2. Use pod spec lint --sources=‘xxx’ When , Will source Copy the folders in the addresses of all sources specified in to ~/.cocoapods/repos in ;
3. pod spec lint --verbose --allow-warnings --use-libraries --skip-import-validation It will be local ~/.cocoapods/repos Verify this component in all sources in
4. Use pod repo push REPO_NAME SPEC_NAME.podspec When you give an order , Will SPEC_NAME.podspec Files added to ~/.cocoapods/repos/REPO_NAME/SPEC_NAME/pod Of documents version/SPEC_NAME.podspec in ;

Command parsing

1. pod install :
   1. according to Podfile Documents or Podfile.lock Download and import the corresponding third-party library , Check whether the resource configuration file needs to be updated , If there is an update , Then download the latest version .
2. pod update
   1. Pull the latest remote directory first , Update again according to the resources in the directory pod
   2. It doesn't care Podfile.lock Whether there is , Will read Podfile Frame information of the file . If your podfile Each library in has a version specified , without , So every time I pull the latest library .
3. pod update --no-repo-update
   1. Update the library only according to the local directory , No need to pull the remote .
4. pod update xxx
   1. Find a framework that updates the latest version of the specified library name
5. pod repo update
   1. Used to update local cocoapods Of spec Resource allocation information .
   2. Maybe you never use pod repo update You can also get the latest library , That's because you're using pod update Yes, it will be executed by default pod repo update , So you will find that if your pod Too many library references , Every time pod update It's very slow , If the network is not good, it is often broken , Because you are updating pod when , Also updated the resource directory .

Manifest.lock yes Podfile.lock Copy of , It's in Pods Inside the directory . It works like this , We usually don't put Pods Files are put into version management , But the Podfile.lock Put it in version management . In this case, whether the code needs to be updated after pulling pod, By comparing the local Manifest.lock And remote Podfile.lock Whether it is the same or not .