CocoaPods on kunat.dev https://kunat.dev/tags/cocoapods/ Recent content in CocoaPods on kunat.dev Hugo -- 0.147.5 en-us 2025 kunat.dev Wed, 11 Jun 2025 19:11:09 +0200 How to Use Xcode 16's Buildable Folders with CocoaPods https://kunat.dev/notes/xcode16-folders-pods/ Wed, 11 Jun 2025 19:11:09 +0200 https://kunat.dev/notes/xcode16-folders-pods/ <p>A few months ago, I decided to try Xcode&rsquo;s new <a href="https://dimillian.medium.com/why-you-should-use-xcode-16-buildable-folders-instead-of-groups-6f438611914d" target="_blank" >buildable folders</a> feature in my project. However, right after converting all my groups to folders, I discovered that CocoaPods had stopped working. Attempting to install project dependencies resulted in the following error:</p> <div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>$ pod install </span></span><span style="display:flex;"><span> </span></span><span style="display:flex;"><span>❌ ArgumentError - <span style="color:#f92672">[</span>Xcodeproj<span style="color:#f92672">]</span> Unable to find compatibility version string <span style="color:#66d9ef">for</span> object version <span style="color:#e6db74">`</span>70<span style="color:#e6db74">`</span>. </span></span></code></pre></div><p>At the time, I updated CocoaPods to the latest version, confirmed my project format was set to the latest Xcode version (16.3), and tried again. When the issue persisted, I assumed CocoaPods was incompatible with buildable folders and that I would need to migrate to Swift Package Manager (SPM) to use them. This conclusion seemed to be confirmed by several closed GitHub issues where the suggested workaround was to manually convert folders back to groups.</p> A few months ago, I decided to try Xcode’s new buildable folders feature in my project. However, right after converting all my groups to folders, I discovered that CocoaPods had stopped working. Attempting to install project dependencies resulted in the following error:

$ pod install

❌ ArgumentError - [Xcodeproj] Unable to find compatibility version string for object version `70`.

At the time, I updated CocoaPods to the latest version, confirmed my project format was set to the latest Xcode version (16.3), and tried again. When the issue persisted, I assumed CocoaPods was incompatible with buildable folders and that I would need to migrate to Swift Package Manager (SPM) to use them. This conclusion seemed to be confirmed by several closed GitHub issues where the suggested workaround was to manually convert folders back to groups.

However, it turns out you don’t have to wait to use Xcode’s buildable folders with CocoaPods! The solution is surprisingly simple: set the Project Format in your project’s settings to Xcode 16.0. Any other selection will trigger the Xcodeproj error.

hello there

With that single change, you can start taking full advantage of Xcode’s buildable folders in your CocoaPods projects!

References

]]>