{"id":28829,"date":"2020-04-29T16:04:21","date_gmt":"2020-04-29T20:04:21","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=28829"},"modified":"2023-03-06T09:53:58","modified_gmt":"2023-03-06T14:53:58","slug":"actool-strips-larger-icon-sizes","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/04\/29\/actool-strips-larger-icon-sizes\/","title":{"rendered":"actool Strips Larger Icon Sizes"},"content":{"rendered":"

Max Seelemann<\/a>’s App Store upload failed because the high-resolution versions of the icon were missing:<\/p>\n

\n

It turns out, the icons actually<\/em> were not there… but obviously we had them in the source asset catalog. We didn’t change the asset catalog or how icons are created in months.<\/p>\n

[…]<\/p>\n

It started dawning on me… if we didn’t notice others might not have as well? A quick check in the app folder… yep, other recently updated apps like \n@pixelmator, \n@vectornator, or \n@dayoneapp\n show the same problem. It even affects Apple’s own apps like KEYNOTE!<\/p>\n

[…]<\/p>\n

1) iconutil requires images in an “iconset” to be named like “icon_16x16.png” etc. – actool seems to be more flexible (but strips the larger sizes)<\/p>\n

[…]<\/p>\n

2) Seems that Finder no longer takes the app’s icon from the icns file. Instead, it reads the embedded asset catalog (if there is any).<\/p>\n

So you can’t just add an .icns file and use it – if you have an asset catalog, the icon must be compiled in.<\/p>\n

3) You cannot compile an app icon in an asset catalog without actool also writing the icns file. Whatever you do … you need to replace<\/em> that icns file in later build phase.<\/p>\n<\/blockquote>\n\n

I haven’t been using asset catalogs because, last I checked, they don’t work with frameworks<\/a>. There’s no public API to look up an image in a given asset catalog; it only checks the one at the top level.<\/p>\n\n

See also:<\/p>\n