new AFPClient for iOS/OSX <--SOLUTION FOR LION USERS

(2012-04-15 03:17)Ned Scott Wrote:  The AFP client lib we use is buggy, and the people who originally developed it have abandoned that project. The biggest issue that I've seen is this sort of "cuts in and out" type thing that you've described. Sometimes it's not so bad, sometimes it drives one mad. There's not much we can do about it, since even improving that AFP client lib is now seen as a dead end. A replacement AFP client lib is something sought out, but there is no ETA.

very interesting. thanks for the info!

FWIW, my experience is as follows:

Adding afp://mymac.local/Sharename works fine, it shows up in Files.

Streaming videos from there works as well, until it doesn't. Crashes XBMC 11.0 somewhere during the video playback.

Mac Mini (Intel) on Snow Leopard (10.6.something).

We know about it and are looking for a better afp library for accessing these sort of shares already.

Here I am again. In preparation for the upgrade to Lion, I had XBMC working great over afp:// serving from OS X 10.6.8. My shares were simple, just:

afp://MacPro.local

From there I could browse to any volume I wanted.

Now on Lion (went straight to 10.7.4), browsing that share crashes XBMC (now on ATV2 running OS 5.x tethered).

This is the last line in the xbmc.log:


The odd thing is, that public folder is not a source or anything, while MacPro.local is... And even still, with my user:pass (admin) I should have access to that public folder. And also why is path name truncated and duplicated like that?

post the full log to pastebin and put the link here

(2012-05-11 09:59)Memphiz Wrote:  post the full log to pastebin and put the link here

Thanks. Here's the full log.

Some additional notes on this.

• The crash occurs a few seconds after listing the contents of the share/source. That is, the full list of all connected volumes and Public Folder share points defined in OS X File Sharing. So the actual login via afp:// seems successful.

• I can confirm this by going to "Edit Source" and then "Browse". In this case there is no crash. However when I try to open the "Jane Smith" (name changed) public folder in question, there is a delay but then nothing opens. It is also displaying the mangled folder name for that one particular folder.

• I note that there's a curly single quote on : Smith's. Is that expected? It must be OS X that under normal circumstances lists that folder when it's a share point as "Mike Jones's Public Folder" because of course in the file system the actual path is ~/mjones/Public/

• I am currently suspecting a permission issue in that user domain or on that folder that did not manifest under OS X 10.6.8 but is manifesting now. Will try to repair.

Could you do the log with debugging enabled again please? (turn it on in settings->system->debugging)

(2012-05-11 12:43)Memphiz Wrote:  Could you do the log with debugging enabled again please? (turn it on in settings->system->debugging)

Sorry, should have done that the first time. Here it is.

Could you pm me the real name of Jane Smith and the string of that volume as it appears in your log file. And you added the source just by

afp://user:pass@MacPro.local/

How did you setup this? Normally there MUST be a volume for each afp source. Please give me your configuration as detailed as possible, so i can setup a environment as near to yours as possible for trying to reproduce that shit.

Correct. The source is exactly as you put it. I realize it has been suggested that there must be a volume for the source. But believe it or not doing it that way worked beautifully on 10.6.8. Also, the same method works currently on another Mac (afp://iMac.local/) that is now running 10.7.3. It's much easier that way, as I don't need symlinks (which as you may recall was a huge problem in moving from smb:// to afp://) at all. Furthermore, I didn't need to add each of several volumes separately.

There is no particular share point in OS X's Sharing Pref pane. Logging on with my admin user/password gave me access to all connected volumes! (And as I said, does with the other Mac!)

I will PM you the original name and log string, along with a ls -a of the user's folder.

Anything else you need to know?