4 ms·

I have a large complex project in XCode. (It's this: http://macdaddy.io/mac-backup-software http://macdaddy.io/mac-backup-software) It looks simple but it's ac

by feelix 10y ago

I have a large complex project in XCode. (It's this: http://macdaddy.io/mac-backup-software http://macdaddy.io/mac-backup-software) It looks simple but it's actually about 6 different programs all stuck together. Codesigning breaks on it periodically, and it takes days to fix. XCode 8 has just broken this worse than any other XCode version in history. It seems to have done so by trying to automate all its requirements. So now it outputs broken bundles when I compile it. This has taken me all of today, and I'll be surprised if I have it working within the next 6 hours of work. This is a fairly typical experience of using XCode for me. Many times getting codesigning working correctly and getting it working within the mac app store parameters takes more time than writing the code. In short: Using XCode is harder than programming.

tempodox 10y ago
You can never, ever, just upgrade Xcode (or anything important, really) on a production Mac. Xcode, especially, needs to be installed on a sandbox machine first where it can destroy anything it wants. It's an effort, but still better than having production explode in your face.
- feelix 10y ago
  That's probably a good approach. Still, when my certificates expire (which makes the provisioning profiles invalid), that alone will take hours or days to fix. So even if it's left in a completely untouched environment certificates expire after a year or two and I cannot recompile the project without a lot of work.
Cthulhu_ 10y ago
Maybe you need to refactor your application instead, to make it more like how xcode expects applications to be structured?
- feelix 10y ago
  It's all using Apple endorsed formats. It's just using an awful lot of them. But it's all exactly how it's supposed to be. But because it's using a daemon, a Finder extension, command line interface apps, etc, they all have their own provisioning profiles and they all have to be codesigned in their own ways. Which is what makes it tricky.
bmaniar 10y ago
Please report this issue at http://bugreport.apple.com http://bugreport.apple.com along with sysdiagnose, we'd love to take a look. Please include project as well if possible.
bmaniar 10y ago
Please report this issue at http://bugreport.apple.com http://bugreport.apple.com along with sysdiagnose, we'd love to take a look. Please include project as well if possible.

by feelix 10y ago

tempodox 10y ago

You can never, ever, just upgrade Xcode (or anything important, really) on a production Mac. Xcode, especially, needs to be installed on a sandbox machine first where it can destroy anything it wants. It's an effort, but still better than having production explode in your face.

feelix 10y ago
That's probably a good approach. Still, when my certificates expire (which makes the provisioning profiles invalid), that alone will take hours or days to fix. So even if it's left in a completely untouched environment certificates expire after a year or two and I cannot recompile the project without a lot of work.

Cthulhu_ 10y ago

Maybe you need to refactor your application instead, to make it more like how xcode expects applications to be structured?

feelix 10y ago
It's all using Apple endorsed formats. It's just using an awful lot of them. But it's all exactly how it's supposed to be. But because it's using a daemon, a Finder extension, command line interface apps, etc, they all have their own provisioning profiles and they all have to be codesigned in their own ways. Which is what makes it tricky.

bmaniar 10y ago

Please report this issue at http://bugreport.apple.com http://bugreport.apple.com along with sysdiagnose, we'd love to take a look. Please include project as well if possible.

bmaniar 10y ago

Please report this issue at http://bugreport.apple.com http://bugreport.apple.com along with sysdiagnose, we'd love to take a look. Please include project as well if possible.