3 ms·

Swift 3.0 is really nice but I backtracked out of Xcode 8.0 for now. I am used to Xcode but this one still vomits Apple internal debug messages into the console

by dep_b 10y ago

Swift 3.0 is really nice but I backtracked out of Xcode 8.0 for now. I am used to Xcode but this one still vomits Apple internal debug messages into the console, that's really too rough for me. I'll wait for the .01 or the .1 before upgrading all my projects. Funny thing is I downloaded one of the first if not the first beta of Xcode 8 and it already migrated my projects flawlessly (where possible). It's all the other stuff that's broken.

kybernetyk 10y ago
I hope I can get used to work without the Polychromatic plugin[1]. Or that the dev somehow can get around the new plugin sandbox in Xcode. Haven't tested it yet with Xcode 8 but I fear it won't work. [1] - https://github.com/kolinkrewinkel/Polychromatic https://github.com/kolinkrewinkel/Polychromatic
- LeoNatan25 10y ago
  Isn't the sandbox only enabled if System Integrity Protection is enabled? Disable that and the plugins should work, if they are updated for Xcode 8. [Update] Hmm, seems so. See this: https://github.com/inket/update_xcode_plugins https://github.com/inket/update_xcode_plugins
- osolo 10y ago
  Try this plugin[1] which will unsign Xcode and allows older plugins to work. I also encourage you to file a radar [2] to let Apple know you're not pleased about them killing a thriving plugin ecosystem. Yes, I know there's a new plugin API but it's so crippled that 90% of the plugins on Alcatraz couldn't possibly move to it. If enough of us complain maybe they will listen. [1] - https://github.com/nrbrook/MakeXcodePluginsWork https://github.com/nrbrook/MakeXcodePluginsWork [2] - https://bugreport.apple.com/ https://bugreport.apple.com/
anmilo 10y ago
there's a settings flag you can add to stop those internal debug messages, which I believe started in the XCode 8 Beta. It is pretty annoying that this not clearly mentioned or toggle-able in the UI https://twitter.com/rustyshelf/status/775505191160328194 https://twitter.com/rustyshelf/status/775505191160328194

by dep_b 10y ago

kybernetyk 10y ago

I hope I can get used to work without the Polychromatic plugin[1]. Or that the dev somehow can get around the new plugin sandbox in Xcode. Haven't tested it yet with Xcode 8 but I fear it won't work. [1] - https://github.com/kolinkrewinkel/Polychromatic https://github.com/kolinkrewinkel/Polychromatic

LeoNatan25 10y ago
Isn't the sandbox only enabled if System Integrity Protection is enabled? Disable that and the plugins should work, if they are updated for Xcode 8. [Update] Hmm, seems so. See this: https://github.com/inket/update_xcode_plugins https://github.com/inket/update_xcode_plugins
osolo 10y ago
Try this plugin[1] which will unsign Xcode and allows older plugins to work. I also encourage you to file a radar [2] to let Apple know you're not pleased about them killing a thriving plugin ecosystem. Yes, I know there's a new plugin API but it's so crippled that 90% of the plugins on Alcatraz couldn't possibly move to it. If enough of us complain maybe they will listen. [1] - https://github.com/nrbrook/MakeXcodePluginsWork https://github.com/nrbrook/MakeXcodePluginsWork [2] - https://bugreport.apple.com/ https://bugreport.apple.com/

anmilo 10y ago

there's a settings flag you can add to stop those internal debug messages, which I believe started in the XCode 8 Beta. It is pretty annoying that this not clearly mentioned or toggle-able in the UI https://twitter.com/rustyshelf/status/775505191160328194 https://twitter.com/rustyshelf/status/775505191160328194