“We are unable to process your request”

Generally speaking, Apple does not monitor these forums. You should use the Report Bugs link at the bottom of each page to submit a feature request. That's the only thing they look at when setting their development priorities.

Please use the Report Bugs link at the bottom of the page to submit feature requests. The squeaky wheel gets the grease.

Well, the tagline for this part of the forums reads: Provide feedback or request enhancements to the forums, so I think I’m exactly in the right place.

Watch the What's New in Swift talk. Since `executeFetchRequest` is a throwing method (https://developer.apple.com/library/prerelease/ios/documentation/Cocoa/Reference/CoreDataFramework/Classes/NSManagedObjectContext_Class/index.html#//apple_ref/occ/instm/NSManagedObjectContext/executeFetchRequest:error:), you need to wrap it in a `do { ... } catch { ... }`. So I think it should look like this:do { ... let results = try managedContext.executeFetchRequest(request) as! [StockCode] } catch { fatalError(Fetching from the store failed) }This is based on my take away from the talk. I still haven't downloaded Xcode 7 :[

You could try submitting a enhancement request bug report for this Bluetooth audio capability, but it's very likely a dup, as it's been asked about in the forums here for years.

Update:So I ended up using one of my technical support credits on this question, but the results weren't very pleasing regarding HTTP Live Streaming (HLS).Our engineers have reviewed your request and have concluded that there is no supported way to achieve the desired functionality given the currently shipping system configurations - Apple Developer Technical SupportI guess I'll start a new post under HTTP Live Streaming, since that is the only issue now.

Due to the nature of how Apple Pay works, when you implement it in your project your card will not actually get charged (even though you'll see a notification that you did). Your payment token gets passed into the didAuthorizePayment delegate function, so it really depends on what your code is doing there. If it's not really doing anything, then do not fret, your card is not getting charged 🙂 Typically you would implement the mentioned delegate method such that it passes the payment token to some sort of Payment Platform you'll have set up that actually processes the charge. However depending on the payment platform you use, you could create a sandbox environment in there so that your card will not be charged.Take a look at the Ray Wenderlich's guide for Apple Pay, it'll give you step by step instructions on how to set Apple Pay up and how to set up a sandbox environment on the payment platform so that your credit card doesn't get charged.

Having this problem on all the latest apple betas. IOS 9 & 8.4 and OSX 10.10 and 10.11 betas. I found this in our clearpass server for onboarding, i wonder if the new updates are actually impementing this added trust requirement -The server certificate is used by ClearPass to secure web (HTTPS) and authentication (RADIUS) traffic. It can be configured in Policy Manager under Administration » Certificates » Server Certificate.The optimal configuration for Onboard is a server certificate issued by a trusted commercial certificate authority. A list of certificate authorities trusted by iOS devices can be found at http://support.apple.com/kb/HT5012Alternatively if you only wish to use a single Onboard Certificate Authority then you can use that Certificate Authority to sign the server certificate. Users will then have to install the certificate as part of the provisioning process. Refer to the Deployment Guide for more information.For testing purposes you can disable the requirement for HTTPS on the

This is the case in iOS 8.3 and iOS 8.4 beta. iBooks finally supports displaying chapters in iOS 8.4 beta, but we are unable to extract them. Please advise what new API we have to use, or if this is a known bug which will be corrected.