Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Updated to 13.1 and now file "can't be found"
- Thread starter rovostrov
- Start date
- Sort by reaction score
I'm not going to pursue this anymore. I don't think NSXPCConnection is relevant. Here's the last thing I saw when trying to open a Numbers file:
Process 764 is Finder. But, that log message is made at the "Default" log level rather than "Error" level, so it could be nothing.
Anyway - it's up to Apple to solve this. I'm just playing around and have no idea what is broken. Even though I always see Launch Services logging an error, it doesn't mean that code is responsible.
i've reported it thru FOUR OS updates, and am sure others have reported it as well...
If their Feedback Assistant's report ID (e.g. FB121...) increments by 1 for every report, then based on numbers between my 2 reports they are receiving ~2200 feedbacks every day. I think that is a huge amount of reports to process 1 by 1 every day so they probably just pay attention to the ones that are reported repeatedly many times, but on the other hand they are Apple and can check all of them if they wanted to.
We are seeing an interesting twist on this on 13.3 and above.
There are 2 ways to describe letters like "ä" in UTF8. One of them no longer works correctly. This was introduced in 13.3
There are 2 ways to describe letters like "ä" in UTF8. One of them no longer works correctly. This was introduced in 13.3
After I did the above actions the file cannot be found has not occurred anymore have done all the updates released are now on 13.3.1I have erase the entire internal HDD/SSD and install clean Ventura 13.2 and did not use Time machine backup but copied only the programs and documents manually and some important folders in Application Support. After a week I have not seen the errors which previously occurred with files could not be found and external disks and SD cards very strange but could it be that updating previous operating system messed something up!? Continuing to test with Zip files and external filesystems to see if it is stable over a longer period of time.
Fingers crossed
I'm not young enough to know everything but also not so old that I've forgotten everything 🤪 😂
just ran today's update... and i think this is fixed 🎉
i put 2 images in a folder, named it 'test'. they open. renamed the folder 'something else', images still opened. yesterday, i would have gotten the 'file not found' error.
will be interesting to see what others here report, but looks good....
i put 2 images in a folder, named it 'test'. they open. renamed the folder 'something else', images still opened. yesterday, i would have gotten the 'file not found' error.
will be interesting to see what others here report, but looks good....
haven't seen the issue again once (yet). still, lol, am holding my breath.................
I have now encountered this file won't open issue on a clients machine with macOS 11 Big Sur. The only thing that worked in Big Sur is renaming the containing folder. If you name it back to the original name it, unlike macOS 13 Ventura, once again silently refuses to open in any app. No error messages. Tried pdfs and word files in Word and Pages.
Renaming the file itself also didn't help.
Apple have bombed this one.
Note that, in macOS 13.3.1(a) at least, I seemingly don't have this issue any longer. I had multiple issues that went away with 13.3.
Renaming the file itself also didn't help.
Apple have bombed this one.
Note that, in macOS 13.3.1(a) at least, I seemingly don't have this issue any longer. I had multiple issues that went away with 13.3.
what does this have to do with ventura? you should discuss this on the OS 11 forum.
& not sure how apple has 'bombed this one', since it's fixed on ventura, and not a common issue on big sur (or, to be fair, i never experienced it there)...
As can be seen in my previous posts I first encountered this in macOS 13 Ventura. I used Big Sur for 18 months without anything even remotely like this. Since I now saw it in Big Sur on a client's machine, I thought it worth to mention this issue is not unique to Ventura.
Proof "it's fixed on ventura"? Apple "bombed this" as it's an extremely embarrassing bug. None of us have an idea how common this issue is, but it should be so rare I wouldn't encounter it more than once. For me the problem survived complete re-installations and in new fresh users the problem was in place immediately. That's not good at all.
i never saw this in big sur, and don't remember people talking about it (that of course does not mean it didn't happen). and if you have evidence that this was common... please share it. but personally, i've never experienced it until ventura.
still, bugs are bugs, and need to be fixed. on ventura, this one (finally) is. that's not bad at all.
So you keep saying without explaining, as if you would know what is behind this kind of issue on multiple macs you have no access to. You don't know. You have anecdotal information, as most of us.
of course, but am not claiming anything further. i never said anything like "None of us have an idea how common this issue is". also (not that it matters), but i did freelance mac support (& made a very good living!) for 18 years in nyc, and never saw this issue once... until ventura. but agreed, i have anecdotal information; nothing more, nothing less.
The Ventura bug is embarrassing. I'm not sure the Big Sur bug is the same one, but it might be. I guess Big Sur has had patches and maybe introduced the same issue.
Was there something funny about the name of the folder whose contents couldn't be opened until it was renamed? I know there was a patch related to unicode characters causing problems opening files. It was mentioned in another thread, but I can't find it at the moment. I'm pretty sure Apple called it a "regression", which means it was working but they broke it with some update. I also seem to remember it mentioned something about a security check against the name they couldn't parse. Big Sur certainly gets security patches. I got one kind of recently (applied it yesterday).
