Error building the project

[Isuru-Nanayakkara]

I have Xcode 6 beta 4 installed. I'm trying to build the project but I keep getting this error.

Command /Applications/Xcode6-Beta4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-stdlib-tool failed with exit code 1

Any idea why?

[Dimillian]

Clean, rinse and repeat. I got it from time to time.

[Dimillian]

You may want to sign the project too if you build for a physical device.

[Isuru-Nanayakkara]

I cleaned and build it repeatedly. Removed the project, re-cloned it and tried building. Same issue.

No, I'm trying to just run it in the simulator.

[TosinAF]

That error is misleading. It's due to with code signing. You need it to sign with your certificate and also turn off the setting for the today extension

[Isuru-Nanayakkara]

I'm trying to change the Team Name in the project Settings to None but that's not getting selected either.

[TosinAF]

In, Capabilities for the project, have you turned off every capability on there?

[Isuru-Nanayakkara]

No. Background Modes is ON with Background Fetch ticked.
Also App groups is ON.

[TosinAF]

Yeah, turn them off, unless you want to create a provisiong profile with those capabilities added.

[Isuru-Nanayakkara]

Turned them off for both SwiftHN and SwiftHNToday targets but no good. Still getting the same error.

[TETRA2000]

Occurred same problem too, but cleared.
Did you changed the Team Name for all Projects?
SwiftHN, SwiftHNToday and SwiftHNShared.

[Isuru-Nanayakkara]

That's the problem. I can't change the Team names no matter how many times I select 'None' from the drop down, its always selected to Unknown name (Z6P74P6T99)

[TETRA2000]

So how about to select your Provisioning Profile?

[Dimillian]

As SwiftHN support some capabilities (like group sharing for data sharing between extensions & app) I would strongly suggest you to generate your own certificate and provisioning profile and put them in the Xcode build settings. As I'll evolve the project it'll support more and more features requiring correct code signing of the application if you want to run it.

[Isuru-Nanayakkara]

This Macbook I'm trying to run it is not my own and also I don't have a paid developer account yet so I can't generate Provisioning Profiles also :( But I'll be getting one soon so I guess I'll have to be patient until then.

[Dimillian]

Ah yeah :( if you don't have a paid developer account I don't think you can generate certificates and profile. Hmm so yeah, you should try as @TosinAF & @TETRA2000 said and disable all feature related to code signing.

[finder39]

After a lot of play with provisioning and disabling of linking the today extension I was able to get it to compile. I'm just curious, is there a way to compile with the today extension working yet?

[Dimillian]

Not yet, I'm waiting for the next beta, this is too bugged at the moment.

Thomas Ricouard
http://thomasricouard.info
http://twitter.com/Dimillian

On 28 Jul 2014, at 05:12, finder39 notifications@github.com wrote:

After a lot of play with provisioning and disabling of linking the today extension I was able to get it to compile. I'm just curious, is there a way to compile with the today extension working yet?

—
Reply to this email directly or view it on GitHub.

[finder39]

I see you got the extension working! Nice! I'm still have trouble building the new code with the extension enabled :/

[Dimillian]

@finder39 Since you contribute to it, maybe I can add you to my dev account team? This way you could properly sign the project. I believe Apple is doing some code signing enforcement for extension :/