Got some error info when I upgrade to macos 13
FantaZZ opened this issue · comments
It work on local disk, but did not work on ext volumes.
Thanks for reporting this, @FantaZZ.
I don't have macOS 13 yet, and may be a while before I get to look at this.
Do you have any information on whether this could be the result of a deliberate, but breaking change in the new macOS version?
What is the file system of your target disk (not all of them support resource forks, which is what fileicon relies on)?
Did the same command targeting the same volume work prior to upgrading?
Do you have any information on whether this could be the result of a deliberate, but breaking change in the new macOS version?
I can not sure it is a breaking change in the new macOS.
But before upgrade it was work and after upgrade it was not work, on same disk same file.
What is the file system of your target disk (not all of them support resource forks, which is what fileicon relies on)?
Target disk file system is ExFAT.
Did the same command targeting the same volume work prior to upgrading?
But before upgrade it was work and after upgrade it was not work, on same disk same file.
I can confirm that after upgrading to macos 13 I experienced the same error.
With macos 13 you must also allow your terminal to update or delete other applications. You can find this option under Privacy & Security / App Management in your System Settings. Otherwise fileicon will not work and you will get a permission error.
Thanks, @jonafll.
It looks like this applies only to .app folders in /Applications, right?
And when I try without permissions (even with sudo) I get "Cannot modify '/Applications/Foo.app': you do not have write permissions.", which is different from @FantaZZ's symptom.
@FantaZZ, I don't have access to an ExFAT volume; when I try with NFS volumes, it seems to work fine.
Do you still see the problem in the latest macOS Ventura version, 13.1?
@mklement0 I upgrade to macOS 13.0.1, I still got this on ExFAT mobile hard disk
And it is success with same file on Mac mini m1 local disk
Thanks, @FantaZZ.
I have no explanation, and the problem is likely in the Cocoa API that fileicon depends on.
I've marked the issue as resolution-external.
I've just published v0.3.2, which can't be expected to solve the problem, but it may provide a more specific error message.
I got v0.3.2, After call, It look like success, but file icon did not chang. And I did not take any error message.
New discovery, even I darg image to file icon, the file icon still not change. So it is a macos bug can be sure.
