Open PMStanley opened 9 years ago
Hi, @PMStanley,
I don't plan to pay for Apple's Developer Program in the near future. Anybody else willing to sign it?
I'm in the same situation as you @crmne, no plans to join the Mac developer program any time soon...
I'm a Mac developer be willing to help if i can
@Gary-Ash would you be prepared to sign a release with your Developer ID?
I've setup a signed release test on fork.
Thanks @Gary-Ash! :)
Thanks @Gary-Ash, just downloaded it and the pkg file is not signed. Any chance you could sign this too?
Accepted the security warning on the pkg and ran the installer but it errored out with a non descript message in the console: 26/09/2014 11:00:56.557 Installer[863]: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
try the 2nd test release, please. Sorry for the problems
Install still fails, error messages are:
com.apple.kextd[19]: ERROR: invalid signature for com.Cycling74.driver.Soundflower, will not load
com.apple.kextcache[1848]: Soundflower.kext has invalid signature; omitting.
Just had a though, Yosemite requires the Xcode 6.1 beta. I'm still running Mavericks and Xcode 6.01
Hmm, might be an issue then. Does it install OK for you?
Seems to work for me
There's 2 issues installing Soundflower on Yosemite Developer Preview 4 and whilst I have workarounds I was wondering if there was anything more that can be done?
1) Yosemite does not accept unsigned kexts. Workaround: run the following command in a terminal, reboot and try the installer again: sudo nvram boot-args="kext-dev-mode=1"
2) Gatekeeper stops the Soundflowerbed app install into ./Applications Workaround: copy it in manually after the installer completes.
With issue 2 I set my system to allow installs from anywhere but it was still blocked when running the generated installer package (the rest of the files copied in fine, just the app was blocked). Not sure if that's a bug, mistake on my part or working as intended.
Both issues would be resolved by a "Developer ID" signed release, but I guess the issue there is that as soon as someone signs a release they 'own' it and will potentially get support requests for it.
@crmne You've provided binary releases so far, do you have the capability to sign the releases and would you be prepared to do it?