Welcome Guest
Pages: 1
Cocoa Error 35 - more helpful message?
artelsePostAugust 26, 2016, 08:34
Newbie
Posts: 12
Registered:
August 15, 2016, 22:20
Normal topicCocoa Error 35 - more helpful message?

It appears that when Yate saves a file and it is in use by iTunes (playing the file), you get an error 35. Perhaps an idea to issue a more helpful error message or is it difficult to detect?
2MR2PostAugust 26, 2016, 08:51
Avatar photo
Administrator
Posts: 2362
Registered:
August 23, 2012, 19:27
Normal topicRe: Cocoa Error 35 - more helpful message?

Yate does file manipulation in lots of places. When it gets an error it asks the OS for the reason. Apple returns wonderful things such as "Cocoa Error 35" as text. In this case even displaying "Permissions Error" may not be much better. Okay...it's a little better 🙂

The issue is that we'd have to check after each error and determine if better text could be formulated.... or create a centralized error 'dumper'.

Perhaps it was poor design but as each file system call returned an error object, it was far simpler to display the textual reason as supplied.

I'll look into it.
2MR2PostAugust 26, 2016, 08:57
Avatar photo
Administrator
Posts: 2362
Registered:
August 23, 2012, 19:27
Normal topicRe: Cocoa Error 35 - more helpful message?

Sorry...35 is "Resource temporarily unavailable"
artelsePostAugust 26, 2016, 10:58
Newbie
Posts: 12
Registered:
August 15, 2016, 22:20
Normal topicRe: Cocoa Error 35 - more helpful message?

In this case the message could pose a question. "Is the file playing in iTunes or open elsewhere?" or something similar. But agreed these things can be tricky to be accurate about.
2MR2PostAugust 26, 2016, 12:42
Avatar photo
Administrator
Posts: 2362
Registered:
August 23, 2012, 19:27
Normal topicRe: Cocoa Error 35 - more helpful message?

It turns out that there is really only one location where these errors will typically be posted. I'll look into coming up with something better.

I'm on El Capital and iTunes 12.4.3.1 and I don't get errors saving while iTunes is playing. I've tried local and remote files and everything seems fine. I have not tested this on any other OS version. It's always possible that it is dependent on the type of mount that the music is on.
2MR2PostAugust 26, 2016, 15:16
Avatar photo
Administrator
Posts: 2362
Registered:
August 23, 2012, 19:27
Normal topicRe: Cocoa Error 35 - more helpful message?

I now catch and replace the more common Cocoa Error messages. It'll appear in v3.14 coming soon.
artelsePostAugust 27, 2016, 06:17
Newbie
Posts: 12
Registered:
August 15, 2016, 22:20
Normal topicRe: Cocoa Error 35 - more helpful message?

Ok thanks for looking into this. My music collection is stored on a Synology NAS, so no HFS+, but ext4. This could be why the error occurs.
artelsePostAugust 28, 2016, 13:47
Newbie
Posts: 12
Registered:
August 15, 2016, 22:20
Normal topicRe: Cocoa Error 35 - more helpful message?

It seems the error 35 is not always related to an in use file. When I save an album, occasionally I get error 35 and what is odd, is that Yate then removes the file from the list. Is this intentional?
2MR2PostAugust 28, 2016, 13:55
Avatar photo
Administrator
Posts: 2362
Registered:
August 23, 2012, 19:27
Normal topicRe: Cocoa Error 35 - more helpful message?

The file removal is historic as once the save was started it did not use to be possible to back out. That limitation is long gone so v3.14 no longer closes files on benign save errors. This is already implemented.

I'm not sure why you're getting 35s. Perhaps the drive is slow to respond.

The only time Yate can get a Cocoa Error 35 is at the start of a save when it attempts to get a File Handle for writing. It is theoretically possible to get it later while writing, but I've never seen it.
Pages: 1
Mingle Forum by Cartpauj | Version: 1.1.0beta | Page loaded in: 0.044 seconds.