fix: recognize Icon Composer .icon file type - #1162
Open
jsj wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Short description 📝
This change recognizes Xcode 26 Icon Composer
.iconbundles during file-reference generation.Solution 📦
Xcode maps the
iconextension tofolder.iconcomposer.icon.XcodeProj did not contain this mapping. Thus, Tuist-generated projects created
PBXFileReferenceentries without alastKnownFileTypevalue forAppIcon.icon.Local Xcode inferred the file type. Xcode Cloud did not infer the file type. It treated the bundle as a plain folder.
As a result,
actoolreceived onlyAssets.xcassets. It did not findAppIcon.This change adds the missing mapping to
Xcode.filetype(extension:).Implementation 👩💻👨💻
.icontofolder.iconcomposer.icon.swift test --filter XcodeTestspasses.AppIcon.iconin the asset-compiler inputs.