<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Pratik Kate on Medium]]></title>
        <description><![CDATA[Stories by Pratik Kate on Medium]]></description>
        <link>https://medium.com/@pratikkate?source=rss-4f9533a16fd2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GtqqPaQGQ23znT1cviEiHw.jpeg</url>
            <title>Stories by Pratik Kate on Medium</title>
            <link>https://medium.com/@pratikkate?source=rss-4f9533a16fd2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 17:24:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pratikkate/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Xcode Didn’t Kill xcodeproj. pbxproj Is Becoming JSON. ]]></title>
            <link>https://pratikkate.medium.com/xcode-didnt-kill-xcodeproj-pbxproj-is-becoming-json-4cc73a24714f?source=rss-4f9533a16fd2------2</link>
            <guid isPermaLink="false">https://medium.com/p/4cc73a24714f</guid>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[xcode-27]]></category>
            <category><![CDATA[apple]]></category>
            <dc:creator><![CDATA[Pratik Kate]]></dc:creator>
            <pubDate>Fri, 18 Sep 2026 10:11:39 GMT</pubDate>
            <atom:updated>2026-09-18T10:13:10.200Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HsbSkRPxtGmENk6HOP10Ug.png" /></figure><p>Right-click MyApp.xcodeproj → Show Package Contents. That’s the whole story. Xcode 27.2 (beta) swapped the config file in that folder. It did not invent a new project type.</p><p>Apple’s page: <a href="https://developer.apple.com/documentation/xcode/updating-your-xcode-project-configuration-file-format">Updating your Xcode project configuration file format</a>.</p><h3>Three names people are already mixing up 📦</h3><p>MyApp.xcodeproj — the bundle. Still the thing in Finder, git, and xcodebuild -project.</p><p>project.pbxproj — the old guts. OpenStep plist. UUID graph. Merge hell.</p><p>project.xcproj — the new guts. Hierarchical JSON.</p><p>There is no .xcodeproject file. If a screenshot or a tweet used that word, they meant project.xcproj <em>inside</em> .xcodeproj.</p><p>New projects in 27.2 already write JSON. An app you created last year keeps pbxproj until you convert it. Nothing auto-migrates on first open.</p><h3>What actually got quieter in git 🔀</h3><p>One Swift file used to land in four places, each with a fresh 24-character ID. You add SettingsView.swift, I add ProfileView.swift, git thinks we rewrote the project.</p><p>JSON puts membership on the file:</p><pre>{<br>  &quot;path&quot;: &quot;CatalogView.swift&quot;,<br>  &quot;target-membership&quot;: [&quot;MyApp/compile-sources&quot;]<br>}</pre><p>That’s “compile this in MyApp.” No extra PBXBuildFile object.</p><p>Settings stop cloning themselves for every configuration. When Debug and Release disagree, the condition is the key:</p><pre>&quot;SWIFT_OPTIMIZATION_LEVEL[config=Debug]&quot;: &quot;-Onone&quot;<br>&quot;SWIFT_OPTIMIZATION_LEVEL[config=Release]&quot;: &quot;-O&quot;</pre><p>IDs are not gone. Targets and the .app still have them. Individual sources mostly don’t. That’s why diffs shrink (one demo went ~300 → 123 lines) without the project becoming a different app.</p><h3>Easy to miss (this is the useful part) 👀</h3><p>🛑 <strong>Xcode 26 cannot open a JSON project.</strong> Hard stop. One person on 26 means the repo stays on pbxproj.</p><p>🎛️ <strong>27.0 can open JSON. 27.2 is what shows the convert menu.</strong> File inspector (⌥⌘1) → Project Document → Project Format → JSON. If you don’t see JSON, you’re not on 27.2.</p><p>🛠️ <strong>xcodebuild did not change.</strong> You still pass the bundle:</p><pre>xcodebuild -project MyApp.xcodeproj -scheme MyApp</pre><p>📌 <strong>Schemes, workspaces, </strong><strong>xcshareddata stay put.</strong> Conversion deletes project.pbxproj and adds project.xcproj. Undo is those two git changes, or the same dropdown back to the old format.</p><p>⚙️ <strong>.xcconfig is still </strong><strong>.xcconfig.</strong> JSON stops Debug/Release from duplicating the same setting <em>inside the project file</em>. It is not a replacement for shared config files.</p><p>🔄 <strong>Generated projects will fight you.</strong> If XcodeGen or Tuist emits the .xcodeproj, a hand convert gets overwritten on the next generate. Wait until the generator writes xcproj, or don’t convert.</p><p>🙈 <strong>Anything that greps </strong><strong>project.pbxproj goes blind.</strong> CocoaPods, the xcodeproj gem, Fastlane project patches, Bazel rules_xcodeproj, CI sed on objectVersion. Apple published <a href="https://github.com/apple/xcode-project-format">apple/xcode-project-format</a> so those tools have a Swift model. They have not shipped on it.</p><p>⚠️ <strong>objectVersion 70 / 77 / 100 is a different fight.</strong> That’s still the <em>old</em> pbxproj world (Xcode 16 folders, Xcode 26 bumps). JSON is a new file, not a new number in the plist.</p><p>🧪 <strong>27.2 is beta.</strong> There’s already an autocomplete crash in the notes. Keep 27.0 installed. Convert on a branch, clean build, run tests. If the team mixes 27.0 and 27.2, have someone on 27.0 open it before you merge.</p><h3>Blue folders were 2024. JSON is 2026. 📁</h3><p>Xcode 16 synchronized folders (blue) already fixed “I added a file.” Xcode reads the directory. pbxproj doesn’t list every .swift.</p><p>JSON fixes the rest: settings, targets, who compiles what.</p><p>You can use both. That’s the small project file: blue folder + project.xcproj.</p><p>Unknown ISA PBXFileSystemSynchronizedRootGroup on pod install was the folder change. Don’t “fix” JSON by converting folders to groups, and don’t skip JSON because you already went blue. 👀</p><h3>Convert when the tools can see the file ✅</h3><p>Tiny sample app, SPM only, everyone on 27? Flip it. Takes twenty seconds.</p><ol><li>Select the project (blue icon at the top of the navigator).</li><li>File inspector → Project Format → JSON → Continue.</li><li>Confirm git only touched project.pbxproj → project.xcproj.</li></ol><p>Work app with CocoaPods, a generator, or Xcode 26 in the mix? Stay on pbxproj. It still works in Xcode 27. Apple did not put a timer on it.</p><p>If merge conflicts are the only itch and you don’t want a format war, convert leftover yellow groups to synchronized folders first. That’s free, and it isn’t this change.</p><p>Same icon. Different file inside. Don’t convert until the thing that reads your project can spell xcproj. 🧃</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4cc73a24714f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CocoaPods Isn’t Dead. Trunk Is Freezing. ]]></title>
            <link>https://pratikkate.medium.com/cocoapods-isnt-dead-trunk-is-freezing-feefdd872e74?source=rss-4f9533a16fd2------2</link>
            <guid isPermaLink="false">https://medium.com/p/feefdd872e74</guid>
            <category><![CDATA[spm]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[cocoapods]]></category>
            <dc:creator><![CDATA[Pratik Kate]]></dc:creator>
            <pubDate>Wed, 19 Aug 2026 11:23:48 GMT</pubDate>
            <atom:updated>2026-08-19T13:52:31.963Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>December 2026 is a freeze, not a funeral and huge apps don’t need a weekend rewrite.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WyeM9gH1qGpYJ13WJbw-qw.png" /></figure><p>There’s a weird split in iOS chats right now.</p><p>One person: “CocoaPods is dead. Migrate everything.”<br>Someone else: “Chill. pod install still works.”</p><p>Both feel true. That’s the confusion.</p><h3>What’s actually happening 📅</h3><p>On December 2, 2026, CocoaPods trunk goes permanently read-only.<br>There’s a dry run Nov 1–7, 2026, then the real freeze.</p><p>After that:</p><ul><li>❌ no new pods on trunk</li><li>❌ no new versions on trunk</li><li>✅ existing versions can still install</li><li>✅ pod install still works</li></ul><blockquote>Source:<a href="https://blog.cocoapods.org/CocoaPods-Specs-Repo/"> CocoaPods Trunk Read-only Plan</a></blockquote><p>Some vendors freeze <em>before</em> trunk does, Take an example of Firebase.</p><p>🔥 Firebase stops publishing new Apple SDK versions to CocoaPods in October 2026 — about two months before Dec 2.<br>(<a href="https://firebase.google.com/docs/ios/cocoapods-deprecation">Firebase migration guide</a>)</p><h3>The mix-up everyone keeps making 🤯</h3><p>CocoaPods the tool is not disappearing. Trunk — the public registry most of us use for pod ‘Alamofire’ — stops getting restocked.</p><p>Think of it is as grocery store, not apocalypse: <em>Open for business. No new deliveries after December.</em></p><p>Your old packages stay on the shelf. Fresh updates stop arriving through that aisle.</p><h3>Will builds break on Dec 3? 🛠️</h3><p>Probably not.<br>If it’s already in your Podfile.lock, it should keep resolving.</p><p>What dies is this habit: <em>“We’ll just bump the pod when they publish on CocoaPods.”</em></p><p>Builds can survive. Blind trust in trunk updates won’t.</p><h3>Cross-platform reality check 📱</h3><p>React Native still resolves iOS dependencies through CocoaPods; SPM is not a finished path there.</p><pre>$ yarn ios<br>› Compiling react-native Pods…<br>$ cd ios &amp;&amp; pod install<br>Analyzing dependencies<br>Downloading dependencies<br>Installing React-Core (0.7x.x)<br>Installing RCT-Folly (202x.xx.xx.x)<br>Installing ***SDK (x.x.x)<br>Generating Pods project<br>Pod installation complete! There are 42 dependencies from the Podfile<br>** BUILD SUCCEEDED **</pre><p>So don’t tell RN teams to deintegrate on a weekend 👀.</p><h3>Huge app? Git pins first, SPM in waves ✅</h3><p>For a tiny project, “move everything to SPM now” is fine.<br>For a big app with dozens of pods, vendor SDKs, extensions, and a nonstop release train? A hard cutover is how you create outages.</p><p>A saner plan:</p><ol><li>Keep CocoaPods where you still need it</li><li>Pin public pods to official git + tag</li><li>Move to SPM gradually when timeline allows</li><li>Leave messy binary/vendor SDKs until there’s a real path</li></ol><pre>pod &#39;Alamofire&#39;, :git =&gt; &#39;https://github.com/Alamofire/Alamofire.git&#39;, :tag =&gt; &#39;5.9.1&#39;</pre><p>Same library. Less dependence on trunk.</p><p>Git-backed CocoaPods buys time.<br>SPM is still the better long-term direction.<br>Both can be true.</p><p>Git pins are a bridge, not forever — especially if a SDK has no public git, or you’re stuck on ancient versions.</p><p>If Any Stakeholder’s asks, say this: <em>We won’t rewrite dependency management overnight. We’ll stop leaning on trunk, keep shipping, and migrate to SPM in waves.</em></p><h3>Takeaway 🎯</h3><p>CocoaPods isn’t flipping a kill switch.</p><p>Trunk is freezing.</p><ul><li>Existing installs can keep working</li><li>New trunk publishes stop</li><li>Panic migrations help nobody</li><li>Huge apps should stabilize with git pins, then move to SPM gradually</li></ul><p>The internet says “CocoaPods is dead.”<br>What it usually means is: the public registry stops evolving.</p><blockquote>Museum stays open.<br>They just stopped collecting new pieces.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=feefdd872e74" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>