-
Notifications
You must be signed in to change notification settings - Fork 232
Use Icon Composer app icon in Xcode 26 #2043
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thanks for this. Unfortunately, 38dd321 has no effect: as soon as there is a .icon bundle, it takes over any .iconset left. |
|
I noticed that the asset catalog and the application produced by Xcode through processing of the .icon file are respectively 1 Mbytes heavier than the ones we introduced in 709e440 which were post-processed via icns creator and ImageOptim… The disk image weights 9.1 Mb instead of 7.9 Mb… Not convinced the Apple way of doing things is worth it on this. |
|
The problem with using Asset Catalog instead of Icon Composer is that it won't support a dark-mode icon or tinted icon in macOS 26. Based on the discussion here, it doesn't seem to be possible to have the old-style icon when using Icon Composer (there was a workaround in Xcode 26.0, but that has since been patched out by Apple). 38dd321 is only for backward compatibility with Xcode 16 (which doesn't know about .icon files), Xcode 26 ignores it. Another thing I found out about: AppIcon.icns is actually not what macOS uses to show the app icon, it uses the Asset Catalog since macOS 10.13. The AppIcon.icns file is only there for other apps to use. |
That leads to builds based on Xcode 16 and Xcode 26 presenting different icon looks… Keeping in Asset Catalog what is currently in |
Personally, as far as Apple's default setting for icons and widgets style remains "default", I can live with that. I agree with the prevailing opinion that the design of macOS Tahoe was hastily developed to divert attention from Apple Intelligence's delays. I believe we should ignore the “new features” as much as possible and reassess the situation when macOS 27 is available. Hopefully, Alan Dye's departure from Apple will have had an effect by then. We've already released our icon from the “jail of hell,” so we can leave it at that. |
|
@barijaona which features exactly do you want to ignore? Regardless of how finalized the design is, I don't believe that dark mode or tinted icons are going away, and these options should be provided. |
|
I don't think that saving 1 MB is enough to give up on dark/tinted icon support. I agree that it is unfortunate, but it is not severe enough for me. Side node: The biggest contributors to Vienna's bundle size are the bundled Swift dylibs for macOS 10.13–10.14.3 (~11 MB), which aren't used by macOS 10.14.4+. |
|
Thé missing feature is the dark icon which current version of Tahoe is unable to display correctly. I will explore the possibilities of But currently we always get the PNGs as the system's starting point. |
The `AppIcon.icon` bundle is the same as the one used for PR ViennaRSS#2009 As of Xcode 26 / Icon Composer, the `.icon` bundle is sufficient basis to get the vectorial renderings used for Liquid Glass, and also the bitmap files needed by former versions of macOS. However, we also maintain the `AppIcon.appiconset` bundle resource which is needed by Xcode 16 for building and running some of our Github tests.
6222515 to
bfd9e1a
Compare
|
I don't like how Apple is forcing on us a non optimized solution but… |
No description provided.