Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I guess you're asking me if I reported the issue to Apple - I haven't. Other issues plague me more and I don't even follow through on those; only if there's no workaround do I call them. It's a bit of a time sink to call them; I guess I'm a bit lazy.

Regarding this problem, though, since it's so easy to reproduce, if Apple has even looked at it briefly, they've certainly checked to logs and have seen what I've seen.

Since you're so polite, if you really insist, I'll call it in.

If it depends on my politeness, I will try to be very polite, Sir :)

I know it is a time sink. I am lazy too. Let's see if it is fixed in the next point release. Fingers crossed.
 
If it depends on my politeness, I will try to be very polite, Sir :)

I know it is a time sink. I am lazy too. Let's see if it is fixed in the next point release. Fingers crossed.
i've reported it thru several betas on the feedback app (including the latest beta). hoping for a fix next update (but it isn't a life-&-death issue)...

EDIT: still happening on the RC (27march)
 
Last edited:
  • Like
Reactions: osplo
Im on 13.3 RC. copied a folder from a sdcard to my desktop with jpgs. renamed the folder and now get this with any pic I try to open but once you open each file the first time its fixed,
 
Im on 13.3 RC. copied a folder from a sdcard to my desktop with jpgs. renamed the folder and now get this with any pic I try to open but once you open each file the first time its fixed,

The problem continues for me as well with 13.3...:(
 
  • Angry
Reactions: osplo
Have you found that if you wait, then it works the first time you try to open the file? I seem to remember I tested that and got the problem even after waiting 5 seconds or so. I can't reproduce that at the moment and have to get to work. I will test further later.

I opened a file whose containing folder I had renamed the day before and the problem occurred.
 
not sure (about the wait); will check it next time i move or rename something... anyway, reported (again!) in the feedback app.

EDIT: easy to duplicate. i change a folder name, double-click a file in that folder... 'file not found'. just went to open a file in that folder (5 minutes later) and got the error. ugh
Confirmed in macOS 13.3:

Did
I opened a folder and double clicked on a file out of four that opened in TextEdit, then closed it.
I then renamed the enclosing folder and went into it in Finder

Result
I opened the same file I had opened before without issues
The other three was "not found"

Expectation
All files to open without issues, just as they did once I had changed the folder name to the original.


Further I've noticed that whole old folders deeper down in Documents are unavailable when selected in the sidebar in Finder even as I can open them no problem in Finder. This problem has stayed active for some hours**.
I encountered this file not found issue more heavy than ever before when I closed a file I had been working on, duplicated it and tried to open it again in another app, which resulted in "File not found", a problem which stayed long enough for me to escalate to Apple support (no resolution yet). After I had created another user and managed to open a copy of the file from there I returned to my main user and had no issues with the original file since, though the sidebar thing exists.

We should note that my user disk is FileVault encrypted, which is new for me since updating to macOS 13 this February.

** I noticed now that this was affecting an enclosing folder not renamed for years, which contained two newer folders that I created and possibly renamed a few times and inside those two folders I've created, renamed and deleted dozens of files the last 48 hours.
I've now re-added them to the sidebar and no issues so far.
EDIT
No, it's broken again. The parent folder and the subfolders that I re-added once again to the sidebar are not found.

Amazingly, if I open the folder from Terminal with open [path-to-file] it unfolds right up in Finder.
 
Last edited:
Yet another symptom I have now is that some files that are not in renamed folders also won't open, like Numbers files that opened no problem recently and some text files in Text editor app Sublime, excel files in Numbers and ods-format files in NeoOffice. All those apps are native and signed.

The solution is as simple as it's unsatisfactory: a warm restart. Well, actually copying the file before opening it, that have been suggested does seem to work, at least for one file. This is so stupid.
 
Last edited:
  • Sad
Reactions: osplo
Yet another symptom I have now is that some files that are not in renamed folders also won't open, like Numbers files that opened no problem recently and some text files in Text editor app Sublime, excel files in Numbers and ods-format files in NeoOffice. All those apps are native and signed.

The solution is as simple as it's unsatisfactory: a warm restart. Well, actually copying the file before opening it, that have been suggested does seem to work, at least for one file. This is so stupid.
Oh boy. I'll keep an eye out for that one. So far, I've only had the issue when renaming a containing folder and it's always been resolved on a second attempt to open the file.

Do you see the same popup?

Screenshot 2023-03-29 at 07.53.22.png
 
Oh boy. I'll keep an eye out for that one. So far, I've only had the issue when renaming a containing folder and it's always been resolved on a second attempt to open the file.

Do you see the same popup?

View attachment 2180702
Yes.

A new detail now is that in the Finder sidebar newly added folders (same as before), that have had very few name changes applied both for the folder names as for the files inside; since being re-added; do work there, but the same sidebar folder entries when clicked in the open dialog from any app results in "not found".
 
Last edited:
i've reported it 3 times in feedback assist. am wondering if the 13.4 beta will help...

I admire your dedication!

Some people in this forum say that the best way to report bugs is through a Developer account since developers have a direct way to report bugs - a free tier developer account can be created easily at no charge. I don't have this bug but I think I will go this way when destiny knocks on my door.
 
I admire your dedication!

Some people in this forum say that the best way to report bugs is through a Developer account since developers have a direct way to report bugs - a free tier developer account can be created easily at no charge. I don't have this bug but I think I will go this way when destiny knocks on my door.
isn't a developer account $99 a year? or has that changed...

anyway am on the public beta program, and report everything problematic i encounter... repeatedly, if necessary.
 
  • Like
Reactions: osplo
isn't a developer account $99 a year? or has that changed...

anyway am on the public beta program, and report everything problematic i encounter... repeatedly, if necessary.
You only pay if you need to sign release software. Developer accounts while just developing doesn't cost anything.
 
Confirmed in macOS 13.3:

Did
I opened a folder and double clicked on a file out of four that opened in TextEdit, then closed it.
I then renamed the enclosing folder and went into it in Finder

Result
I opened the same file I had opened before without issues
The other three was "not found"

Expectation
All files to open without issues, just as they did once I had changed the folder name to the original.
Now also confirmed in a new fresh user. As have been suggested by other menbers this is easily reproduced.
 
You only pay if you need to sign release software. Developer accounts while just developing doesn't cost anything.
i just went to sign up, and the $99-per-year is absolutely in the signup process (this is after i was approved for an account). i don't see any way around that. anyway am staying with the public beta program...
 
i just went to sign up, and the $99-per-year is absolutely in the signup process (this is after i was approved for an account). i don't see any way around that. anyway am staying with the public beta program...

You can get a developer account without joining the developer program. I just used a random Apple ID that I had from years ago and logged in at developer.apple.com. It asked me for a contact phone number for 2-factor authentication. Other than that, there were no requirements. I had access to the developer forums which other people have mentioned is a good avenue for bug reporting.

https://developer.apple.com/help/account/get-started/about-your-developer-account
 
  • Like
Reactions: osplo
You can get a developer account without joining the developer program. I just used a random Apple ID that I had from years ago and logged in at developer.apple.com. It asked me for a contact phone number for 2-factor authentication. Other than that, there were no requirements. I had access to the developer forums which other people have mentioned is a good avenue for bug reporting.

https://developer.apple.com/help/account/get-started/about-your-developer-account
if you just logged in, and didn't have to sign up, that suggests you already have a developer account...???? 🤔

when i go there, i get this:
Screenshot 2023-03-30 at 12.58.18 PM.png


anyway, am fine on the public beta program, and will let this thread get back on topic...
 
It's a launch services problem. Since it's so easy to reproduce, I was able to capture in the logs, using the "log" command at the shell.

2023-03-13 19:21:11.446502-0700 0xc2b68 Error 0x11b6bd 894 2 CoreServicesUIAgent: [com.apple.launchservices:uiagent] handle LS launch error: {\n Action = odoc;\n AppPath = "/System/Applications/Preview.app";\n Documents = (\n "yyy.pdf"\n );\n ErrorCode = "-43";\n FullPaths = (\n "/Users/xxx/Test cods/yyy.pdf"\n );\n}
2023-03-13 19:21:11.447776-0700 0xc38b8 Error 0x11a9c6 376 2 launchservicesd: [com.apple.launchservices:cas] CopyProcessByPid(3538,NO) failed because session 100030 didn't match expected 100282

Error seems to point to a problem loading the preview app. If you could figure out what process is associated with PID 3538 that might give further information.

The solution is as simple as it's unsatisfactory: a warm restart.

I have a different problem with Ventura where large directories take a long time to load. Can get the spinning gray wheel for minutes. It was improved on advice from Apple Support by doing a Safe Boot (which cleans up a lot of things) followed by a normal boot. Seems to be better with 13.3 update.
 
  • Like
Reactions: fisherking
i just went to sign up, and the $99-per-year is absolutely in the signup process (this is after i was approved for an account). i don't see any way around that. anyway am staying with the public beta program...
Did you try just logging in with Apple ID? That's how I got started. To be clear I'm not in the Apple Developer Program, but I do have access to the free resources at developer.apple.com in my account there.
 
Error seems to point to a problem loading the preview app. If you could figure out what process is associated with PID 3538 that might give further information.

Here's an example when trying to launch an OmniGraffle file and getting the error:

2023-03-30 14:03:13.858696-0700 0xb3e2a Error 0x1322b5 822 2 CoreServicesUIAgent: [com.apple.launchservices:uiagent] handle LS launch error: {\n Action = odoc;\n AppPath = "/Applications/OmniGraffle.app";\n Documents = (\n "xyz.graffle"\n );\n ErrorCode = "-43";\n FullPaths = (\n "/Users/xyz/Desktop/xxx/HousePower.graffle"\n );\n}
2023-03-30 14:03:13.859985-0700 0xb65c5 Error 0x130b41 375 2 launchservicesd: [com.apple.launchservices:cas] CopyProcessByPid(38208,NO) failed because session 100022 didn't match expected 100178

"Preview" is now replaced by "OmniGraffle" in the log entry.

I will try to dig into what the particular process is, just for fun.
 
Did you try just logging in with Apple ID? That's how I got started. To be clear I'm not in the Apple Developer Program, but I do have access to the free resources at developer.apple.com in my account there.
maybe i'll revisit this, but not urgent.

i just logged in with my ID, and filled in a form to apply for the developer program. then i got an email with confirmation, and a link to finish the signup. and there, i encountered the payment window...
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.