file uri scheme

Extension error:target specifies product type 'com.apple.product-type.watchkit2-extension', but there's no such product type for the 'iphonesimulator' platformMy watch app also has this error:Xcode/DerivedData/AnxietyTracker-aabqxayllohhlydulhldvvzxqkzv/Build/Products/Debug-watchsimulator/AnxietyTracker WatchKit Extension.appex: No such file or directoryAnyone have any suggestions or insight?

is it possible to import a Sketch 3 file in Xcode and use it to actually build our app ? Or can Sketch 3 only be used to design a UI ?Also, what are some great ways to design custom user interfaces, to not make our app look very basic with base Xcode elements (like buttons) ?

Hi,I just installed the OS X El Capitan, Now i'm suffering major setback because of the new “feature” called “Rootless” which blocked me from editing some of the root files using an App.I would to know how'd i disable it? I need urgent help!

When creating a new playground in Xcode 7 beta (7A120f) and using a custom Cocoa Touch Framework I get the error:Playground execution failed: Game.playground:4:8: error: module file's minimum deployment target is ios9.0 v9.0The custom framework does use specific iOS9 code. When adding a class to the Sources folder using GKEntity the compiler also shows an error explaining I should use:@available(iOS 9.0, *)The meta data of the playground does not show any indication the Playground uses a deployment target (8.4 or some other version).What am I missing here? Why can't I use a custom framework created with iOS9?

Hi,I'm working on getting up and running with Xcode Server for Continuous Integration. I'm running Xcode 6.3.2 on my development machine, and have OS X Server 4.1 running on an iMac with the latest version of Yosemite. I've created a bot for my project, but every time it runs I get an error stating the followingBot Issue: error. Uncategorized.Issue: Test target Tests encountered an error (Timed out waiting 120 seconds for simulator to boot, current state is 1. If you believe th.Integration Number: 18.Integration URL: https://ucs-imac.slcb.uc.edu/xcode/bots/B6CBA97/integrationsDescription: Test target Tests encountered an error (Timed out waiting 120 seconds for simulator to boot, current state is 1. If you believe this error represents a bug, please attach the log file at /Library/Developer/XcodeServer/Integrations/Integration-22c44be172594e54917e9723b9116f90/Session-2015-06-15_18:17:02-ukAljH.log).I've seen several similar issues related to Jenkins and other third party CI servers. One of those disc

I am following this tutorial: https://www.youtube.com/watch?v=4_0Ao11zrtMI am trying to make a login box similar to the one in the video, but for a cocoa app on OS X. I am fairly new at objective-c, and this is my first app.Here is the current code for my LoginController.m file:#import LoginController.h @implementation LoginController - (void)awakeFromNib { [prodigyLabel setTextColor:[NSColor orangeColor]]; [studioLabel setTextColor:[NSColor darkGrayColor]]; loginDictionary = [[NSDictionary alloc] initWithObjects:@password forKeys:@username]; } - (IBAction)loginButtonPressed:(id)sender { } @endThe loginDictionary part was modified because I looked online and thought it might help when I found it on a different site, hence it says NSDictionary alloc.It originally said:loginDictionary = [[NSArray alloc] initWithObjects:@password, nil];But there is no option for forKeys as seen in the tutorial.I keep getting error:Incompatible pointer types sending 'NSString *' to parameter of type 'NSArray *'Please hel

I had a posting in the older forums about this issue. I never really found a solution. Maybe I can try posting again and see if anyone has some good advice.I am a big fan of TDD. One of the techniques I picked up was dependency-injection. Objective-C is a very laid-back language when it comes to type-checking. It is very easy for the compiler to let you swap a test-double class for a production class. I am having a problem in Swift that you might be able to help with.class ChildClass { } class ParentClass { func child() -> ChildClass { return ChildClass() } } protocol ChildProtocol { } extension ChildClass: ChildProtocol { } protocol ParentProtocol { func child() -> ChildProtocol } extension ParentClass: ParentProtocol { }This code is failing to build. Swift does not believe that ParentClass can conform to ParentProtocol. This is a contrived example. I will show you a real example where I would use this pattern in a real app.import Foundation protocol SessionTaskType { } extension NSURLSessionDataTask: