On Nov 7, 2013, at 10:10 AM, Mike Abdullah wrote:
> Ah, that’s a shame.
>
> Come to think of it, there’s a limit on how many security-scoped bookmarks
> you’re allowed to access at once. I wonder, does the problem seem to happen
> around a particular, fairly predictable, number of bookmarks?
On 7 Nov 2013, at 16:18, Andrew Madsen wrote:
> Thanks for the reply Mike. I'm one of Patrick's colleagues.
>
> On Nov 6, 2013, at 5:28 AM, Mike Abdullah wrote:
>
>> This line of code jumps out at me as slightly suspicious for the isStale and
>> resolveError parameters. They are supposed to
Thanks for the reply Mike. I'm one of Patrick's colleagues.
On Nov 6, 2013, at 5:28 AM, Mike Abdullah wrote:
> This line of code jumps out at me as slightly suspicious for the isStale and
> resolveError parameters. They are supposed to be passed by reference. Is this
> the real code you’re sho
On 5 Nov 2013, at 20:01, patrick machielse wrote:
> We're developing an application that needs to track a lot of files (say 10k).
>
> As recommended, we use url / bookmarks to store references to file system
> objects.
>
>
> We regularly see crashes that originate here:
>
> return [NSURL UR
I haven’t seen any crashes like that, but a few weeks ago, while “modernizing"
an app, migrating from the old Alias Manager functions to the newer NSURL
bookmarks, I learned something interesting.
When I tried to resolve an alias which was on a previously-mounted but
currently-unreachable volu
We're developing an application that needs to track a lot of files (say 10k).
As recommended, we use url / bookmarks to store references to file system
objects.
We regularly see crashes that originate here:
return [NSURL URLByResolvingBookmarkData:bookmarkData
