testflight the requested app is not avaliable

I am developing a video player software applying to HLS.How can I get the values of luminance of displayed images ?I was not able to get it using renderInCotext and AVAsset.

i have for years used a non-email based Apple ID. The latest build for iOS 9.0 will not accept my credentials, is anyone else seeing this.

I have a very small Swift 2.0 project which should run on 7.1 and newer.It should use WKWebView on iOS > 8.0 and UIWebView on iOS < 8.0.As soon as I add the WKWebView I can't compile the app again:import UIKit import WebKit class ViewController: UIViewController { override func viewDidLoad() { super.viewDidLoad() if #available(iOS 8.0, *) { let w = WKWebView() w.frame = self.view.frame w.autoresizingMask = [UIViewAutoresizing.FlexibleWidth, UIViewAutoresizing.FlexibleHeight] self.view.addSubview(w) } else { let w = UIWebView() w.frame = self.view.frame w.autoresizingMask = [UIViewAutoresizing.FlexibleWidth, UIViewAutoresizing.FlexibleHeight] self.view.addSubview(w) } } override func didReceiveMemoryWarning() { super.didReceiveMemoryWarning() } }When I compile for the simulator I have no problems at all, but when compiling for devices I get the following warning:ld: warning: URGENT: all bitcode will be dropped because '/Applications/Xcode-beta.app/Contents/Developer/Platforms/i

When I'm connected to cellular and not WiFi my iCloud photo library doesn't download any thumbnails or higher resolution files.I have enabled cellular under preferences > cellular for the Photos app.When I enable Wifi, it works again. There is an exclamation icon at the bottom right of the photo when I'm over cellular, and nothing gets downloaded.I had this in iOS 8 and after upgrading to iOS 9 beta the problem is still there.

Hello,some aspects of these new features aren t really clear to me...- Is it mandatory to support Multitasking / Slide over / Split view? I read in the documentation, which says you should, Apple and users will expect you to... But in my case, my App UI is absolutely not designed to support it. My User Interface just needs the space, I can t shrink the UI to that compact size and dynamically size changing thing, I can t even support portrait on iPad, it s landscape only. So what will happen in iOS 9? If I do nothing, will my app just not work / not be selectable in this split view / Slide over mode? Or will the UI just be messed up? If I don t want / just can t because of UI design aspects support that Split view / Slide over feature, I could set a Boolean in Plist I read? but will this be approved or will I be forced to support it? I guess my app is not the only one that just does not work in that dynamically sizeable compact view Split

I wrote a small class extension for UITableViewRowAction, while doing my Unit Test I've notice that the instance created with the extension 'init' method were alive longuer that I would have expected.So I've trim down the implementation to the bare minimum to test that difference.public extension UITableViewRowAction { public convenience init(title: String!, style: UITableViewRowActionStyle, exposedHandler: (UITableViewRowAction!, NSIndexPath!) -> Void) { self.init(style: style, title: title, handler: exposedHandler) } } class UITableViewRowAction_test: XCTestCase { func test_deallocationOfStoredItems() { weak var a1 : UITableViewRowAction? weak var a2 : UITableViewRowAction? if true { var action : UITableViewRowAction? action = UITableViewRowAction(title: title, style: .Normal) { (a: UITableViewRowAction!, b: NSIndexPath!) -> Void in } a1 = action action = UITableViewRowAction(style: .Normal, title: title, handler: { (a: UITableViewRowAction!, b: NSIndexPath!) -> Void in }) a2 = action println(here

I am having a hard time finding how to download older osx software from the new Member Center SDK section.Is access to all pre yosemit software gone ?

I have rebuilt my app using XCode 7 and am testing that it works on my watch running watchOS 1.0.1 before I upgrade the device to version 2.0. Everything seems fine so far except that my groups do not have their custom insets (all zero) but instead have insets of 2. If I change the insets to larger values then it seems to work as expected, but not for zeroes.This works fine in the simulator (which runs 2.0) but not on the watch when running 1.0.1. I notice that the new API offers the ability to set the insets at runtime (which is very useful - thanks for that) so I'm wondering if this is related to that?Sounds like I need to file a bug report but I thought I'd mention it here in case anyone else notices that things are positioned strangely when running an app built with XCode 7 on a watch running 1.0.1.