Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keka 1.1.2 fails on Mac OS X 10.9 #257

aonez opened this issue Aug 9, 2018 · 1 comment

Keka 1.1.2 fails on Mac OS X 10.9 #257

aonez opened this issue Aug 9, 2018 · 1 comment


Copy link

aonez commented Aug 9, 2018

As reported by @briatte on #27 (comment), Keka 1.1.2 fails to get access to files.


On Mac OS X 10.9 the Keka preferences are not correctly read/stored. Therefore Keka can't get access to files.

  • Opening Keka and removing the older file access (In Keka - Preferences - File Access) gives Keka access trough the session
  • As soon as Keka is closed, the new access is replaced by the OS, rendering it unusable in the next session

This message appears randomly when launching Keka:

xpcd[XXX]: restored permissions (100600 -> 100700) on /Users/aone/Library/Containers/com.aone.keka/Container.plist

This message appears after updating the file access and closing Keka:

cfprefsd[XXX]: CFPreferences detected an inconsistency. An attempt by process XXX to access preferences in 

Domain: com.aone.keka
User: aone
Container: /Users/aone/Library/Containers/com.aone.keka/Data
Path: /Users/aone/Library/Containers/com.aone.keka/Data/Library/Preferences/com.aone.keka.plist
plist data:<CFPDXPCBuffer: 0x7ff19b408bf0>
shmem index:1022

 actually resolved to 

Domain: com.aone.keka
User: aone
Container: (null)
Path: /Users/aone/Library/Preferences/com.aone.keka.plist
plist data:(null)
shmem index:1666

 Typically this indicates that the process's sandbox profile changed in a way that added or removed a shared-preference-* rule or changed its container path. To avoid overwriting data incorrectly, cfprefsd is disconnecting this client from this source, its preferences will not be saved to disk

This issue does not affect on Mac OS X 10.10 and newer.


Right now there's no definitive fix. But:

  • Updating Mac OS X to 10.11 will fix this issue. All Mac machines running 10.9 can run 10.10 and even 10.11 flawlessly, with all the feature and security improvements.
@aonez aonez added this to the 1.1.3 milestone Aug 9, 2018
@aonez aonez self-assigned this Aug 9, 2018
Copy link
Owner Author

aonez commented Aug 10, 2018

Finally it was a sandbox check using some 10.9 incompatible code. This will be fixed in 1.1.3.

@aonez aonez closed this as completed Aug 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant