{"id":49937,"date":"2025-11-05T15:13:31","date_gmt":"2025-11-05T20:13:31","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=49937"},"modified":"2025-11-10T13:38:55","modified_gmt":"2025-11-10T18:38:55","slug":"xcode-26-1","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2025\/11\/05\/xcode-26-1\/","title":{"rendered":"Xcode 26.1"},"content":{"rendered":"<p><a href=\"https:\/\/developer.apple.com\/documentation\/xcode-release-notes\/xcode-26_1-release-notes\">Apple<\/a> (<a href=\"https:\/\/download.developer.apple.com\/Developer_Tools\/Xcode_26.1\/XcodeXIP_26.1_Universal.xip\">xip<\/a>, <a href=\"https:\/\/developer.apple.com\/download\/all\/\">downloads<\/a>):<\/p>\n<blockquote cite=\"https:\/\/developer.apple.com\/documentation\/xcode-release-notes\/xcode-26_1-release-notes\">\n<p>Xcode 26.1 includes Swift 6.2.1 and SDKs for iOS 26.1, iPadOS 26.1, tvOS 26.1, macOS 26.1, and visionOS 26.1. Xcode 26.1 supports on-device debugging in iOS 15 and later, tvOS 15 and later, watchOS 8 and later, and visionOS. Xcode 26.1 requires a Mac running macOS Sequoia 15.6 or later.<\/p>\n<\/blockquote>\n\n<p><a href=\"https:\/\/mastodon.social\/@stroughtonsmith\/115482591437083945\">Steve Troughton-Smith<\/a>:<\/p>\n<blockquote cite=\"https:\/\/mastodon.social\/@stroughtonsmith\/115482591437083945\"><p>It might be just me, but Xcode 26.1 seems to have thrown a grenade into the visionOS build process. Getting things to build with the right deployment targets and the correct images in the assets catalog is a mess<\/p><\/blockquote>\n\n<p><a href=\"https:\/\/mastodon.social\/@stroughtonsmith\/115492302026642095\">Steve Troughton-Smith<\/a>:<\/p>\n<blockquote cite=\"https:\/\/mastodon.social\/@stroughtonsmith\/115492302026642095\"><p>PSA: from what I&rsquo;ve seen, Xcode 26.1 ignores your minimum deployment target for visionOS apps, and sets it to 26.1. Re-setting it to the intended version does seem to work. Saw this across a bunch of my projects. I haven&rsquo;t checked if it does this for iOS or other platforms, but that&rsquo;s a nasty bug to slip through&#8230;<\/p><\/blockquote>\n\n<p><a href=\"https:\/\/tapbots.social\/@paul\/115492321121019291\">Paul Haddad<\/a>:<\/p>\n<blockquote cite=\"https:\/\/tapbots.social\/@paul\/115492321121019291\"><p>Xcode 26.1 still doesn&rsquo;t seem to let you get rid of the AI icon from the Toolbar, but hey at least it still works on Sequoia.<\/p><\/blockquote>\n\n<p><a href=\"https:\/\/mastodon.social\/@jamesthomson\/115497205425610731\">James Thomson<\/a>:<\/p>\n<blockquote cite=\"https:\/\/mastodon.social\/@jamesthomson\/115497205425610731\">\n<p>Xcode 26.1 seemingly removes the undocumented &ldquo;&mdash;enable-icon-stack-fallback-generation=disabled&rdquo; flag for actool, which enabled you to supply different icons for older systems.<\/p>\n<p>It also means if you have lots of alternative icons, you&rsquo;re back to extensive rebuild times as it re-renders all those icons every single time you touch your asset catalog.<\/p>\n<p>I do not recommend updating to Xcode 26.1 if you, like me, are relying on this flag.<\/p>\n<\/blockquote>\n\n<p>Previously:<\/p>\n<ul>\n<li><a href=\"https:\/\/mjtsai.com\/blog\/2025\/09\/25\/xcode-26-1-beta-1\/\">Xcode 26.1 Beta 1<\/a><\/li>\n<li><a href=\"https:\/\/mjtsai.com\/blog\/2025\/09\/25\/xcode-26-0-1\/\">Xcode 26.0.1<\/a><\/li>\n<li><a href=\"https:\/\/mjtsai.com\/blog\/2025\/08\/08\/separate-icons-for-macos-tahoe-vs-earlier\/\">Separate Icons for macOS Tahoe vs. Earlier<\/a><\/li>\n<\/ul>\n\n<p id=\"xcode-26-1-update-2025-11-06\">Update (<a href=\"#xcode-26-1-update-2025-11-06\">2025-11-06<\/a>): <a href=\"https:\/\/mas.to\/@avidrissman\/115504046352293970\">Avi Drissman<\/a>:<\/p>\n<blockquote cite=\"https:\/\/mas.to\/@avidrissman\/115504046352293970\">\n<p>Since several folks noted it, while &ldquo;enable-icon-stack-fallback-generation&rdquo; still exists as a string in Xcode 26.1, it is no longer parsed as a flag in <code>-imageCatalogCompilerOptionsFromToolArguments:&#8230;<\/code>, and it is no longer processed in <code>_IBICIconStackCommonCreateNamedAssetImportInfos()<\/code>. I have no further details nor advice.<\/p>\n<\/blockquote>\n\n<p id=\"xcode-26-1-update-2025-11-10\">Update (<a href=\"#xcode-26-1-update-2025-11-10\">2025-11-10<\/a>): <a href=\"https:\/\/www.linkedin.com\/posts\/artem-mirzabekian_heads-up-for-ios-developers-using-xcode-261-activity-7392042721181409281-ZQMu\/\">Artem Mirzabekian<\/a> (via <a href=\"https:\/\/weekly.fatbobman.com\/p\/fatbobmans-swift-weekly-0110\">Fatbobman<\/a>):<\/p>\n<blockquote cite=\"https:\/\/www.linkedin.com\/posts\/artem-mirzabekian_heads-up-for-ios-developers-using-xcode-261-activity-7392042721181409281-ZQMu\/\"><p>If you&rsquo;re noticing unusually high CPU usage when running the iOS 26.1 simulator, you&rsquo;re not alone.<\/p><p>It appears that a process called MercuryPosterExtension is repeatedly crashing, which in turn triggers ReportCrash to spin up constantly - flooding the system and causing heavy CPU load.<\/p><\/blockquote>","protected":false},"excerpt":{"rendered":"<p>Apple (xip, downloads): Xcode 26.1 includes Swift 6.2.1 and SDKs for iOS 26.1, iPadOS 26.1, tvOS 26.1, macOS 26.1, and visionOS 26.1. Xcode 26.1 supports on-device debugging in iOS 15 and later, tvOS 15 and later, watchOS 8 and later, and visionOS. Xcode 26.1 requires a Mac running macOS Sequoia 15.6 or later. Steve Troughton-Smith: [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"apple_news_api_created_at":"2025-11-05T20:13:33Z","apple_news_api_id":"d2d4772d-1a63-4791-99c1-0bcf00002d49","apple_news_api_modified_at":"2025-11-10T18:38:58Z","apple_news_api_revision":"AAAAAAAAAAAAAAAAAAAAAQ==","apple_news_api_share_url":"https:\/\/apple.news\/A0tR3LRpjR5GZwQvPAAAtSQ","apple_news_coverimage":0,"apple_news_coverimage_caption":"","apple_news_is_hidden":false,"apple_news_is_paid":false,"apple_news_is_preview":false,"apple_news_is_sponsored":false,"apple_news_maturity_rating":"","apple_news_metadata":"\"\"","apple_news_pullquote":"","apple_news_pullquote_position":"","apple_news_slug":"","apple_news_sections":"\"\"","apple_news_suppress_video_url":false,"apple_news_use_image_component":false,"footnotes":""},"categories":[4],"tags":[2352,30,2742,71,1959,226],"class_list":["post-49937","post","type-post","status-publish","format-standard","hentry","category-programming-category","tag-asset-catalog-car","tag-mac","tag-macos-tahoe-26","tag-programming","tag-simulator","tag-xcode"],"apple_news_notices":[],"_links":{"self":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts\/49937","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/comments?post=49937"}],"version-history":[{"count":3,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts\/49937\/revisions"}],"predecessor-version":[{"id":49981,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts\/49937\/revisions\/49981"}],"wp:attachment":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/media?parent=49937"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/categories?post=49937"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/tags?post=49937"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}