On 2013 Oct 16, at 12:39, Kyle Sluder wrote:
> "98% of the time that means the process changed its sandbox at runtime
> such that it gained or lost access to some prefs."
Thank you, Kyle.
Neither this app, nor its tool, are sandboxed. I didn't think that a sandboxed
app could use CFPreferenc
On Wed, Oct 16, 2013, at 12:00 PM, Jerry Krinock wrote:
> My app's helper uses CFPreferencesAppSynchronize() to update preferences
> of its main app, in whose package it resides.
>
> CFPreferencesAppSynchronize() sometimes logs this to the system consoleā¦
>
> ERROR: looping synchronize attempt.
>
My app's helper uses CFPreferencesAppSynchronize() to update preferences of its
main app, in whose package it resides.
CFPreferencesAppSynchronize() sometimes logs this to the system consoleā¦
ERROR: looping synchronize attempt.
Dirty keys count is 1.
Saved server state is 3650.
Shmem state is 36