OS X 10.7.1 FSMoveObjectAsync still has serious bugs
OS X 10.7.1 FSMoveObjectAsync still has serious bugs
- Subject: OS X 10.7.1 FSMoveObjectAsync still has serious bugs
- From: Steve Gehrman <email@hidden>
- Date: Mon, 22 Aug 2011 19:14:18 -0700
Anyone on the team that does FSMoveObjectAsync want to explain why this still has serious bugs?
I use FSMoveObjectAsync to move an application across volumes. That works. Then I move it back and it gives a -36 error message every time. There is nothing wrong with the source or destination.
Even the Finder fails. Move an app across volumes, move it back, go back and forth a few times and it says a file is busy and stops. There are no busy files, the operation fully completes.
This API has been bug ridden since 10.4.
There are also some data corruption bugs in FSCopyObjectAsync that still haven't been fixed, but for now just wondering why this API still doesn't work after years of reporting bugs.
-steve
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden