“translate scheme”

First up, I moved your question to Core OS > Networking because it seems more about networking than about Swift.Second, I'm having a hard time understanding your actual question. At first blush it seems like you're simply trying to test URLs for equality, that is, you're trying to see if request.URL matches some fixed URL. Is that right? If so, == should work. Swift translates it to -[NSURL isEqual:]. For example: import Foundation let u1 = NSURL(string: http://foo.example.com)! let u2 = NSURL(string: http://bar.example.com)! let u3 = NSURL(string: http://foo.example.com)! println(u1 == u2) // prints false println(u1 == u3) // prints true println(u1 === u3) // prints falseNote that u1 and u3 are not the same object, so === returns false: [I tested this with Xcode 6.4 on OS X 10.10.4, although I expect it'd be the same for Swift 2.]println(u1 === u3) // prints falseIMPORTANT URL equality is more complex than you might think. Consider the following:let uR = NSURL(string: http://example.com) let uR1

Try setting kCFNetworkProxiesHTTPProxy key to your proxy host and kCFNetworkProxiesHTTPPort to the port your proxy listens on. Also I think proxy host should be just host name or ip address (without scheme prefix).

I am seeing this as well.UPDATE: As of Xcode 7.0 beta 5, I still see the issue. There seems to be no way to get the watch simulator to change language and region. I tried using a run scheme as well as changing the language and region for the iOS Simulator. As a workaround, I am testing my app on a physical watch. I change the watch's language and region settings in the Apple Watch app on the iPhone.

How the **** these kind of bugs can pass your validation process ? Beta 4, with its assortment of issues was able to execute these kernels…Don’t you have some moderately complex compute kernels that can help you, or do you cross your finger waiting for our returns ? 👿Here at Iluac we have a bunch of kernels, translated from OpenCL, that can vigorously shake your drivers… And seriously, as I test and debug El Capitan as a part time job for nothing, hire me for three monthes and I’ll help you provide decent drivers (yeah… you know, I’m french and supposedly arrogant) ! And because I love Apple, I’ll do that for a honest salary, a business class seat, an unrestricted access to your Redbull's storehouse, and a ticket for WWDC ’16 ! 😁

I've run into the same problem as the original poster. After years of having one active scheme for each simulator/device combination, a few days ago I started XCode and found I have over 200 of them: fifteen for each simulator/device combination. I can see them in the devices window, but deleting them takes a few minutes each, and probably doesn't address whatever root problem caused the proliferation. I'd really like to figure out what caused the problem, and how to delete those I don't want without taking hours to do that.

Also, as the original poster points out, the scheme now shows the device (iPad Air) and the simulator identifier (i.e.: 085BD3A4-CC9E-4717-AF2F-E08106BB7A88) There is no reference to the iOS of the scheme, so it's just hit-and-miss as to what iOS each scheme tests. That makes it difficult - to say the least - to test an app against all devices/iOSs.

I had the same problem (see my posts below). Re-installed Xcode 6.3.2 and find it works correctly there. Since I don't need the changes in 6.4, I'll stick with 6.3.2. Schemes are correct in 7 beta 4, so I'll hope the problem is limited to 6.4.

The problem seems to be that extension targets that contain swift code aren't being handled properly.There's a workaround for this given in stackoverflow:You can put the following in your scheme so that it executes with every build:rm -rf ~/Library/Developer/Xcode/DerivedData/YourAppName-*/Build/Products/Debug-iphoneos/com.yourcompany.Name.extension.*Or, alternatively:touch ${PROJECT_DIR}/SOME SWIFT FILE IN EXTENSION.SWIFTYou need to add either of these, making adjustments for your particular project of course, here:Edit scheme... > Expand the Run mode in the sidebar > Pre-actions > Click '+' > New Run Script Action.It doesn't solve the underlying issue, but perhaps Apple will if they recieve bug reports.

Hi arifnyet,The tel: url scheme allows your app to launch the dialer with the specified number pre-filled. For example tel:1-408-555-5555.See Phone Links in the Apple URL Scheme Reference.

The struct is defined in C as:struct AudioChannelLayout { AudioChannelLayoutTag mChannelLayoutTag; UInt32 mChannelBitmap; UInt32 mNumberChannelDescriptions; AudioChannelDescription mChannelDescriptions[1]; }; typedef struct AudioChannelLayout AudioChannelLayout;So, if you allocate a variable of this type statically in your code, you can use only one element for mChannelDescriptions. AudioChannelLayout layout; for( int i = 0; i < (int)layout.mNumberChannelDescriptions; ++i ) { //This code may crash your app when i being 1 or more. if( layout.mChannelDescriptions[i].mChannelLabel == kAudioChannelLabel_Left ) { /*some action*/ } }If you want to use more than one channels, you need to allocate it dynamically: int numChannels = 2; AudioChannelLayout *layoutPtr = malloc(sizeof(AudioChannelLayout) + (numChannels - 1) * sizeof(AudioChannelDescription)); layoutPtr->mNumberChannelDescriptions = numChannels; for( int i = 0; i < numChannels; ++i ) { if( layoutPtr->mChannelDescriptions[i].mChannelLabel == kAud

Xcode will require a valid developer certificate for iOS development if the active scheme's destination is set to iOS Device (in the toolbar, where it shows your current target/scheme), so if it that's the problem you would just need to set it back to one of the simulators.You can also change it via the Product > Destination submenu.