Ventura issue rendering custom document icons (Fixed in macOS Ventura 13.4)

[xzhouzhou758]

👉 Fixed in macOS Ventura 13.4

• Keka version: [ 1.2.57 (5068)]
• macOS version: [macOS 13.0 (22A380)]

The icon is displayed normally in the download folder, but the icon is displayed abnormally in the download of the dock

[desmortum]

Yeah. Same thing. In Finder looks good. In Dock looks generic in folders like Downloads or if you pin file to Dock. Also, looks generic in Chrome downloads. Seems like something changed in Ventura.

[desmortum]

Same for *.tar. I guess all formats are affected. I tried cleaning icon cache and doing clean reinstall of Keka. When you remove Keka, original archiver icons are back in Dock and Chrome. When you install Keka, they're generic again.

[aonez]

Seems it’s #453 again. Will check if I can replicate this.

[desmortum]

Unlike in #453, icon is completely blank. As if all apps except Finder cannot get icon for formats associated with Keka at all.

[desmortum]

I've done some experimentation and it seems no privacy permission changes help. What I did find is that other built-in and third-party apps have their associated type icons shown properly. For example Visual Studio *.sln file works fine.

[desmortum]

Found few discussions on Apple site. It seems Adobe PDF is affected too. Hope you can find a way to fix it.

[desmortum]

@aonez, any luck replicating?

[aonez]

Tried with one of the first macOS Ventura betas. While it does not show a generic white document icon, the Dock representations show the macOS zip white icons even if Keka is the default handler. As you can see in the screenshots, same as in #453, only compressed files already recognized by macOS have this issue. Brotli, LZIP and ZSTD do not present this issue.

Will install and try with the current Ventura release, but most probably this should be fixed in Apple's end. I will report it myself after trying with the current version.

This should be reported using the Feedback Assistant: https://developer.apple.com/bug-reporting

[desmortum]

Yeah, Brotli is okay in release version of Ventura.

[aonez]

So tried with macOS 13.1 beta and it shows the white icons as you reported. Even when extracting with Keka they show white, same as in Chrome.

This is the offending API:

[NSWorkspace.sharedWorkspace iconForFile:(NSString *)];

I'm reporting this to Apple right away, but if #453 meant something, this might not be fixed until macOS 14 or later. Fingers crossed they fix this before that.

[aonez]

Also note this will probably affect all apps that override macOS defined icons, such as video apps (VLC or INA).

[aonez]

Already reported to Apple:

Title: Third party document icons not displayed properly on macOS 13
Area: AppKit
Issue: Incorrect/Unexpected behaviour

Third party applications that define icons for macOS recognized document types are not displayed properly on macOS 13.

To reproduce:

- Download Keka or another app that defines icons for system known formats (like ZIP, MOV)
- Be sure to set that application as the default handler for the document type (ZIP, MOV).
- Restart the system if needed to refresh icon caches.
- The custom icons will show properly in the Finder but will show blank where they’re displayed using [NSWorkspace.sharedWorkspace iconForFile:(NSString *)].

You can check this adding a folder with the offending files inside to the Dock, as shown in the screenshots.

Additional info:

This was reported by three users already (more to come) and reproduced by me.
https://github.com/aonez/Keka/issues/1177

All apps that use the NSWorkspace iconForFile: API (and variations of it) will be affected by this issue.
https://developer.apple.com/documentation/appkit/nsworkspace/1528158-iconforfile

macOS 13.0 Beta 22A5286j displayed the macOS icons, instead of the custom ones.
macOS 13.0 22A380 and later (tested macOS 13.1 Beta 22C5044e as well) display blank icons.

Please report it too if you are affected by this issue and want it to be fixed as soon as possible.

[desmortum]

Reported as well.

[desmortum]

@aonez, 13.1 beta 3 is out. Maybe if you have time and partition to check it out give it a shot.

[aonez]

There's no mention to this in the release notes, but I'll check it anyway.

[aonez]

Same same...

[desmortum]

Thanks for checking.

[aonez]

Someone that also found the issue:

https://twitter.com/mjtsai/status/1598433805777379336?s=46&t=Mxh_95-9ojAa8c1J2tB4_w

[pan93412]

Reported as well! Hope Apple can take care of their products' issues. I have reported for at least 3 issues related to macOS 13 😢

[aonez]

Ventura 13.2 Beta still has the issue, as expected.

[pan93412]

Ventura 13.2 Release still has the issue :(

[melyux]

Reported too. But does Apple even take action on any feedback items? It's like a black hole. I've probably reported 20+ things in the past but they were never fixed unless Apple decided to revamp the entire application and fixed it by chance several years later.

[codebysandwich]

Ventura 13.2.1 Release still has the issue :(, alfred affected too.

[despecial]

Ventura 13.3 still does not fix this :(

[JustCrazyer]

Ventura 13.3.1 still does not fix this :(

[aonez]

As reported by @pan93412 we got some news in the Feedback Assistant that reads:

Recent Similar Reports: Less than 10
Resolution: Potential fix identified - For a future OS update

So thanks to @pan93412 for the tip and to all who reported this. Expect the fix in macOS 14, as expected 🙃

[animusastralis]

Finally! Ventura 13.4 got it fixed

[aonez]

I'm still seeing the issue on Ventura 13.4 (22F66)

[desmortum]

For me it's also fixed.

[desmortum]

@aonez, try rebooting or doing "killall Dock"

[aonez]

@desmortum yep already did a restart, cold start and relaunched Finder... But also in Safari the bug persists.

@animusastralis are you on an Intel too?

[desmortum]

@aonez, maybe OS icon cache?

[aonez]

Yeah probably, just updated an ARM VM and it's indeed fixed 👏🏼

[animusastralis]

@aonez no, I'm on M2 MacBook Pro. I didn't notice it right away and did a couple of reboots for other reasons

[pan93412]

Before clearing cache, it did still not work:

After clearing the cache with a Gist script, it works now:

@aonez

[gingerbeardman]

Congrats everybody! what a long journey.