My pleasure 😊

Thanks, Javier 😊

Thanks bro. 😅 Namaste 🙏

I’m glad you liked it 😊

I’m flattered, thanks 😊

Great question, Shawn. You’d need to add the dependency to your podspec file... spec.dependency "Alamofire", "~> 1.0.0" (Where 1.0.0 is the version you want to utilize) By doing this, Alamofire will be installed automatically whenever you try to install your pod using cocoapods. Apart from this tho, I believe an easy way to get the dependency available directly within your framework is to use Carthage. This article easily describes the process. medium.com/captain-ios-experts/advanced-swift-ch-2-using-third-party-framework-inside-custom-swift-framework-133cefd76fcd

Thanks, Nitin. By updating pods, do you mean creating a new version for your custom pod, or updating your third party dependencies in a regular project?

​@@EmmanuelOkwara Yes Emmanuel. I think that should be the second and mandatory part of this video. People watching it should be interested to know how to update the pod they just created.

You make good point. The process is really similar tho. Make your changes Increment your version Lint and upload

You are correct. I’ll create an updated video to explain this.

Thanks, Ravi. Good question. If you want to test your framework on a real device using the method demonstrated in 5:00, you would need to build the framework using either a real or the Generic iOS Device and use the output in your project. An alternative is to build it as a Universal Framework which will allow you to use the framework on both simulator and device. From the video tho, we took the Cocoapod route to install our Framework as demonstrated in 22:11. This way, we don't need to manually make it "Universal". If you attempt to run the app using either a Simulator or a Device, it should work fine.

Thanks for the reply Emmanuel. How can we hide the source code, since we are giving the git repo link to others. They can see the source code right?

Yes the source code is currently public. If you want to keep it private, you can consider making the git repo private and publishing the framework as a private pod. This method will require an additional repo to host your Podspec file.

Great question, Sanjay. What I’ve done personally is to add the dependency into the framework using Carthage(just so that it’s available within our custom framework). When I want to distribute to cocoapods, I add it as a dependency in our podspec. E.g spec.dependency 'Alamofire', '~> 1.0'

Nothing special. Just the regular 4 finger swipe, or 3 fingers depending on your configuration. 😊

Thanks for the info, Cosmin. Did you figure out a workaround?

It’s pretty similar to sharing a public pod. You’ll just need to also share the source url to the private repo so that cocoapods knows where to find the code. Meaning that when you want to install a private pod you’ll also need to add source ‘link_to_repo’ At the top of your file before writing pod ‘name_of_pod’

I appreciate the feedback and apologize for the negative experience. I’ve taken note and will prevent this from happening in subsequent videos. 🤗

@@EmmanuelOkwara sorry for comment and keep doing a great content !

There’s no need for an apology Nizzam 😊 I really do appreciate the feedback. If you have other ideas of ways you feel my tutorials/videos can be improved, I’m all ears. Feedback helps us get better 💯