Uniti Core file copy fail

Having updated my Mac to MacOS 26, I now get an ‘unknown error’ fail when trying to copy new files to the Core…?

Although I can create the folders and sub-folders on the Core and then copy the files one at a time…… v. odd.

@davidhendon any thoughts?

ATB, J

No sorry. I have no idea! There was a post about this same problem a few days ago, as I recall the OP said it was fixed by a firmware update to his Mac. But I didn’t fully understand what he meant.

I haven’t let my MacBook Pro do the latest firmware upgrade yet and I’m keeping clear of IOS 26 on our iPhones/iPads for a few months.

Suspect it’s something to do with Intego’s Mac firewall and av software, same thing happened at the last major release, so have raised a ticket with them.

Still don’t really understand why one-at-a-time directory/sub-directory/files works……

Obviously just not smart enough, I’m old enough to have learnt about OS updates breaking stuff :joy::face_with_symbols_on_mouth::joy::face_with_symbols_on_mouth::joy::face_with_symbols_on_mouth:.

Thanks for responding,

ATB, J

This was where a poster commented on how he fixed your issue. Read right down to the end.

Rgr that.

Thx David,

ATB, J :+1:

And as a side note, and a smidge of thread drift, it would appear there’s a possibility that IOS 26.0.1 has created a bug with Apple CarPlay s implemented in my 2024 Renault :face_with_symbols_on_mouth::face_with_symbols_on_mouth::face_with_symbols_on_mouth::face_with_symbols_on_mouth:.

ATB, J

So, a little more experimentation. From my Mac, I can create a directory and/or sub-directory on the Core within the Downloads folder. I am then able to copy files, singly or multiples, into that direction or subdirectory.

Which leads me to believe it is new directory/sub-directory creation which is failing since the MacOS 26/26.0.1 update.

I should know better by now, eh?

ATB, J

1 Like

A permissions issue, possibly?

Just a vague thought…..

Very likely, but who knows where…… obviously associated with the MacOS 26/26.0.1 update.

ATB, J

Can you access a terminal session?

You’d be able to see and alter permissions easily from there, I would think?

Or at least see if that’s where the problem lies, even if you don’t want to change anything for now.

I’m not terribly familiar with MacOS, but rather Linux and GNU utilities and after all MacOS was based on BSD, if I recall? So, very similar underneath, in user space.

I can, but not that familiar with the command line interface.

ATB, J

Ok.

As you say, if it has been caused by an update, then maybe just sit tight and see if a subsequent update puts things right again.

I hope it sorts itself out for you!

Cc @davidhendon

And the answer is……. Ta, da;

“Creating remote folders directly within the Finder on macOS 26 (“Tahoe”) is not possible because of the way Apple redesigned network file access. The new security architecture, along with the deprecation of older protocols like AFP, requires folders to be created and managed on the host computer or server. “

This confirms the process I have now adopted to move albums to my Core.

As I’ve said elsewhere, coding using the Nanny Knows Best guidelines :joy::joy::joy::joy:.

ATB, J

Well done! Very interesting. I wonder whether Naim have understood this. Copying to @Stevesky for his info.

(The issue, put briefly, is that with the latest Apple OS, you can no longer transfer a folder full of files that are on your Mac into the Core’s downloads folder in one go. You have to create the new folder in the Core first and then move the music files from the Mac into the newly created folder in the Core’s downloads folder.)

2 Likes

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.