Closed tomtaylor closed 9 years ago
Sometimes the error manifests as:
24/10/2014 09:40:25.477 xpcproxy[2810]: CFPreferences could not connect to its daemon.
Preferences using the connection 0x0 will be volatile and will not be persisted to disk.
Code signing seems OK:
$ spctl --verbose=4 --assess --type execute ~/Desktop/Satellite\ Eyes.app/
/Users/tom/Desktop/Satellite Eyes.app/: accepted
source=Developer ID
$ spctl --verbose=4 --assess --type execute ~/Desktop/Satellite\ Eyes.app/Contents/Library/LoginItems/LaunchAtLoginHelper.app
/Users/tom/Desktop/Satellite Eyes.app/Contents/Library/LoginItems/LaunchAtLoginHelper.app: accepted
source=Developer ID
$ codesign --display --requirements - ~/Desktop/Satellite\ Eyes.app/Contents/Library/LoginItems/LaunchAtLoginHelper.app
Executable=/Users/tom/Desktop/Satellite Eyes.app/Contents/Library/LoginItems/LaunchAtLoginHelper.app/Contents/MacOS/LaunchAtLoginHelper
designated => anchor apple generic and identifier "uk.co.tomtaylor.SatelliteEyes" and (certificate leaf[field.1.2.840.113635.100.6.1.9] /* exists */ or certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = UY2GK6B69X)
$ codesign --display --requirements - ~/Desktop/Satellite\ Eyes.app/
Executable=/Users/tom/Desktop/Satellite Eyes.app/Contents/MacOS/Satellite Eyes
designated => anchor apple generic and identifier "uk.co.tomtaylor.SatelliteEyes" and (certificate leaf[field.1.2.840.113635.100.6.1.9] /* exists */ or certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = UY2GK6B69X)
It's happening on Mavericks as well.
Do you get that with the latest build of master too?
On 24 Oct 2014, at 13:28, Justin Hileman notifications@github.com wrote:
It's happening on Mavericks as well.
— Reply to this email directly or view it on GitHub.
Sorry, I forgot to respond. Yes, the latest build (and now release) seem to be working in Mavericks.
SE has stopped launching at login, when that option is set. I can't work out if this is a code signing issue, or related to Yosemite.
I thought a89cd1768a0316b61cff8574a34565bd55ec09cf might fix it, but it hasn't.
When I run the app from
/Applications
and set 'Run SE at start up' in the preferences I see the following error:Can anyone confirm if this happens on their build?