<article>
<div class="l">
<div class="l">
<section>
<div class="ie if ig ih ii">
<div class="">
<p>As an iOS developer, libraries make our development process, therefore our life easier. Thanks to these libraries, we shorten our development process and make it practical. I&#8217;ll try to describe the issues we&#8217;ll face when developing our own iOS library(s).</p>
<h2 id="fa67" class="pw-post-title ij ik il bn im in io ip iq ir is it iu iv iw ix iy iz ja jb jc jd je jf jg jh gp">In Short</h2>
</div>
<p id="3e48" class="pw-post-body-paragraph ji jj il jk b jl lb jn jo jp lc jr js jt ld jv jw jx le jz ka kb lf kd ke kf ie gp" data-selectable-paragraph="">We will develop a sample iOS library that you can use with Swift Package Manager (SPM) and CocoaPods.</p>
<p id="9af8" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">While supporting SPM vs CocoaPods, there are two important differences that we need to know. First, file structure between them is different. Second, you publish them different. We will address both in the following steps as we develop.</p>
<h2 id="7826" class="kg kh il bn ki kj kk kl km kn ko kp kq jt kr ks kt jx ku kv kw kb kx ky kz la gp" data-selectable-paragraph="">Create SPM Project for our iOS Library</h2>
<p id="a6d5" class="pw-post-body-paragraph ji jj il jk b jl lb jn jo jp lc jr js jt ld jv jw jx le jz ka kb lf kd ke kf ie gp" data-selectable-paragraph="">Open your XCode then create a new SPM library from path:</p>
<p id="aadb" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">XCode &gt; File &gt; New Project &gt; Multiplatform &gt;Swift Package</p>
<p data-selectable-paragraph=""><img class="alignnone wp-image-2786 size-full" src="https://ac.appcircle.io/wp-content/uploads/2022/05/10RoOLShplQ746WrLNDRTxg.png" alt="Create SPM Project for our iOS Library" width="1400" height="899" srcset="https://ac.appcircle.io/wp-content/uploads/2022/05/10RoOLShplQ746WrLNDRTxg.png 1400w, https://ac.appcircle.io/wp-content/uploads/2022/05/10RoOLShplQ746WrLNDRTxg-300x193.png 300w, https://ac.appcircle.io/wp-content/uploads/2022/05/10RoOLShplQ746WrLNDRTxg-1030x661.png 1030w, https://ac.appcircle.io/wp-content/uploads/2022/05/10RoOLShplQ746WrLNDRTxg-768x493.png 768w, https://ac.appcircle.io/wp-content/uploads/2022/05/10RoOLShplQ746WrLNDRTxg-705x453.png 705w" sizes="(max-width: 1400px) 100vw, 1400px" /></p>
<p>&nbsp;</p>
<p id="6827" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">Let’s examine the auto-generated files after creating your project.</p>
<p id="07cf" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph=""><strong>README</strong>: It is the file that allows you to show your library how to used by other developers.</p>
<p id="30ba" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph=""><strong>Package</strong>: It is the file where we define the basic settings of your SPM project. Settings such as Dependecy, test files are made here.</p>
<p id="d571" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph=""><strong>Sources Folder</strong>: It is the directory where we have swift files that we will develop.</p>
<p id="0e59" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph=""><strong>Tests Folder</strong>: It is the directory where our unit tests are.</p>
<p data-selectable-paragraph=""><div class="dynamic_cta">
                <img src="/images/icon-left.svg" alt="Left Icon" 
                     class="cta_icon cta_icon_left">
                <h2>Empower Your iOS Projects Now!</h2>
                <img src="/images/icon-right.svg" alt="Right Icon" 
                     class="cta_icon cta_icon_right">
                <a href="/platforms/ios-ci-cd" 
                   class="dynamic_cta_button">Learn More</a>
            </div></p>
<h2 id="5845" class="kg kh il bn ki kj kk kl km kn ko kp kq jt kr ks kt jx ku kv kw kb kx ky kz la gp" data-selectable-paragraph="">Edit Library Settings</h2>
<p id="ec01" class="pw-post-body-paragraph ji jj il jk b jl lb jn jo jp lc jr js jt ld jv jw jx le jz ka kb lf kd ke kf ie gp" data-selectable-paragraph="">Our library will support iOS (You can also support macOS in your own projects, if you want), it will not include testing and will support swift 5.0 above.</p>
<p id="2ba4" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">First, we will delete the .testTarget field in the targets segment in the Package. We are deleting the Test file because it will cause unnecessary complexity to include the files we do not use in our project.</p>
<p id="309a" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">To determine the minimum swift version, we set the swiftLanguageVersions key with .v5.</p>
<p id="0998" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">We determined the path where the development files of the project are located in Target.</p>
<p id="dae0" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">As a last step, we provide our minimum iOS 11 support by adding .iOS(v11) to the platforms key to determine the platform on which our library will run.</p>
<p id="c04f" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">In the final, your Package file will look like this:</p>
<p data-selectable-paragraph=""><script src="https://gist.github.com/bdac4d1b67f7f4296be55cf402ab6723.js"></script></p>
<h2 id="6bf4" class="kg kh il bn ki kj kk kl km kn ko kp kq jt kr ks kt jx ku kv kw kb kx ky kz la gp" data-selectable-paragraph="">Development Time</h2>
<p id="12de" class="pw-post-body-paragraph ji jj il jk b jl lb jn jo jp lc jr js jt ld jv jw jx le jz ka kb lf kd ke kf ie gp" data-selectable-paragraph="">Now it’s time to make our library functional. This library will enable us to turn the flash of our phone on and off with a single function.</p>
<p id="1150" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">After deleting our default swift file under AppCircleSampleProject, we add our own swift file.</p>
<p data-selectable-paragraph=""><script src="https://gist.github.com/4db0f6ebf97e2c97550f81dd81a9992c.js"></script></p>
<p id="686c" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">It enables the classes that provide the FlashUsable protocol to turn the flash on and off if the flash is accessible.</p>
<p id="83cd" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">The reason why we use #if os(iOS) at the beginning of our Swift file is that our SPM package can support other platforms, but UIKit is only used on the iOS platform. In order to eliminate this error.</p>
<p id="4a7e" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">Our last step is to share our SPM library as a public repo on GitHub. Now our SPM package is ready to use. My sample repo link that I have prepared for you =&gt; <a class="au lu" href="https://github.com/ferhanakkan/AppCircleSampleProject" target="_blank" rel="noopener ugc nofollow">https://github.com/ferhanakkan/AppCircleSampleProject</a></p>
<h2 id="dad5" class="kg kh il bn ki kj kk kl km kn ko kp kq jt kr ks kt jx ku kv kw kb kx ky kz la gp" data-selectable-paragraph="">Adding CocoaPods Support to our iOS Library</h2>
<p id="15f2" class="pw-post-body-paragraph ji jj il jk b jl lb jn jo jp lc jr js jt ld jv jw jx le jz ka kb lf kd ke kf ie gp" data-selectable-paragraph="">After providing our SPM support, it’s time to give our CocoaPods support. For this, we will first create our CocoaPods project in a different file directory.</p>
<p id="4aff" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">If CocoaPods is not installed on your computer, install it with the command.</p>
<p data-selectable-paragraph=""><code class="language-bash">sudo gem install cocoapods</code></p>
<p data-selectable-paragraph="">After the installation process is complete, create your CocoaPods project in the directory you choose with the following command line. While creating your project, you will receive certain questions about the project details and you can answer them as follows.</p>
<p data-selectable-paragraph=""><code class="language-bash">pod lib create ProjectName</code></p>
<p data-selectable-paragraph=""><script src="https://gist.github.com/cc2e137e7ab13cff507a4355776a3618.js"></script></p>
<p id="49df" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">There are 3 files we need to get from the Cocoapods project we have created, these are:</p>
<ul>
<li id="cb6a" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp">ProjectName.podspec</li>
<li class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp">Example folder</li>
<li class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp">LICENSE</li>
</ul>
<p id="55f4" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">We need to move these 3 files to the file where our SPM package is.</p>
<p id="6f7f" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">You can delete the remaining CocoaPods project files. Now is the time to let CocoaPods side see the our developments on the SPM side. For this, we need to open our Podspec file via XCode.</p>
<p data-selectable-paragraph=""><script src="https://gist.github.com/b4b7c4358628b9799ef7ee548df1da04.js"></script></p>
<p id="7d29" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">We are now making the arrangements we have made in the Package file for SPM settings via the Podspec file for CocoaPods. While publishing your library on the CocoaPods side, validation is done by looking at your Podspec file. The most important change we have made here is that we changed the path of s.source_files so that it goes to the file directory where the developments are. Now both SPM and CocoaPods packages use common development files. All files under the Sources/AppCircleSampleProject folder are considered development files.</p>
<p id="8b3b" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">Now we have completed our Cocoapods support. What remains after that is some polishing and publishing our library.</p>
<h2 id="4163" class="kg kh il bn ki kj kk kl km kn ko kp kq jt kr ks kt jx ku kv kw kb kx ky kz la gp" data-selectable-paragraph="">Polishing</h2>
<p id="85f7" class="pw-post-body-paragraph ji jj il jk b jl lb jn jo jp lc jr js jt ld jv jw jx le jz ka kb lf kd ke kf ie gp" data-selectable-paragraph="">What is expected by the users when they look at the libraries is to easily understand the README without examining the source code inside. So feel free to spend your time on your README files. The next step as you know is to edit the sample project that comes with CocoaPods to show how your library should be used. As another important note if your library serves the UI side, you should not forget that you need to provide both programmatic and Xib support.</p>
<p id="0d2a" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">I will have the README file and the sample project in our repo that I have created, you can take it as an example from there.</p>
<p id="a312" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">In order to access your library in your sample project, you may need to enter the example in your project file and change the path in the Podfile depending on the version of CocoaPods you are using. The reason we do this is because we change the directory of our project’s development files.</p>
<p data-selectable-paragraph=""><script src="https://gist.github.com/a6d0a6e2e42520fe99725e57443a071a.js"></script></p>
<h2 id="02fb" class="kg kh il bn ki kj kk kl km kn ko kp kq jt kr ks kt jx ku kv kw kb kx ky kz la gp" data-selectable-paragraph="">Publishing Our iOS Library</h2>
<p id="2ce7" class="pw-post-body-paragraph ji jj il jk b jl lb jn jo jp lc jr js jt ld jv jw jx le jz ka kb lf kd ke kf ie gp" data-selectable-paragraph="">After this exhausting process, there are only a few steps left to share our iOS library. On the SPM side, just post your code to your GitHub repo. Developers will be able to access your library when they enter your SPM link via XCode. But for the CocoaPods side, we need to do a few more actions.</p>
<p id="22b9" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">As the first step, we enter our GitHub repo and click on tags. We create a New Release from here and enter the title according to the version number in our Podspec file and commit. After making the create release, the GitHub part is over, it’s time in the terminal.</p>
<p id="e2c8" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">After coming to the project location via terminal, save your e-mail address with the command line. You will receive a confirmation mail.</p>
<p data-selectable-paragraph=""><code class="language-bash">pod trunk register &#039;your e-mail address&#039;</code></p>
<p data-selectable-paragraph="">After confirming your mail, it’s time to see if our project is suitable for publishing. I recommend you to edit the warnings, either you gave a path error or an unreachable link. Using “ — allow-warnings” will cause you to encounter a possible error in the future.</p>
<p data-selectable-paragraph=""><code class="language-bash">pod lib lint</code></p>
<p data-selectable-paragraph="">If you are ready to publish your validated CocoaPods library, run the command line and your library is now available to all developers.</p>
</div>
<div class="ie if ig ih ii">
<p data-selectable-paragraph=""><code class="language-bash">pod trunk push</code></p>
<p data-selectable-paragraph=""><script src="https://gist.github.com/627f914a8f4494d35ae8059e3de1863f.js"></script></p>
<p id="2159" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">My sample repo =&gt; <a class="au lu" href="https://github.com/ferhanakkan/AppCircleSampleProject" target="_blank" rel="noopener ugc nofollow">https://github.com/ferhanakkan/AppCircleSampleProject</a></p>
<p id="e6e3" class="pw-post-body-paragraph ji jj il jk b jl jm jn jo jp jq jr js jt ju jv jw jx jy jz ka kb kc kd ke kf ie gp" data-selectable-paragraph="">Congratulations! Your iOS library has now been published to both SPM and CocoaPods.</p>
</div>
</section>
</div>
</div>
</article>


Elevate your iOS library projects with seamless CI/CD tool!

Creating an iOS Library the Right Way (SPM and CocoaPods)

Related Posts

Secure and Simplify iOS Code Signing with Appcircle

What is Xcode Cloud, and Why Consider Alternatives?

Automate Your Mobile Code Reviews with Danger CI

Deploy iOS and Android Apps to AWS Device Farm and Run Tests

Creating an iOS Library the Right Way (SPM and CocoaPods)

Related Posts

Secure and Simplify iOS Code Signing with Appcircle

What is Xcode Cloud, and Why Consider Alternatives?

Automate Your Mobile Code Reviews with Danger CI

Deploy iOS and Android Apps to AWS Device Farm and Run Tests

Subscribe to Appcircle Circle