build disappears

You'll need to go thru a normal update submittal routine, again, to add a Preview - just bump the version number in the current build, generate a fresh archive and go again. Call it a 'minor change' if you want to provide info why.

Yep, they just closed mine as a duplicate, so they're definitely aware of it. Hopefully fixed in the next build.

I've begged them for this in bug reports 3 or 4 iOS versions ago, I've written Tim Cook, (and Steve Jobs) for this.I discussed ways I am using past and current Apple tech, UI and frameworks to work around trying to keep my apps at least usable, and instead of Apple helping, those work arounds disappear in the next update of iOS/OSX, this has happened 3 times... the last time, I didn't even think it was even close to something Apple didn't want apps to do, nor would any normal human, yet the next version of iOS/OSX, I could not, nor can anyone, any longer use this extremely useful method... that is just not right.... there just is no reason why it should have disappeared, not battery, not security, not any reason. (and why it was such a big surprise when an Apple employee said: you/your app should not be able to do such and such) I am going to leave that as vage as it sounds, for fear of losing something else.I've grown to use bug reports sparingly, and not at all, twice bitten three times sh

I had the same issue with Xcode 7 beta on my primary Mac (running the current public release of Yosemite). I could fix the issue by checking the Code Sign On Copy box next to the frameworks (in this case, also Sparkle) in the Copy Files build phase.

Sorry, meant to come back to this thread days ago...As others have noted, Swift 2 doesn't seem to support what you want it to do. I see a workaround, though... There's still boilerplate code, but it seems less error-prone to meFirst, we need a way to iterate over the enum cases (and provide their default values):class StoryBookStateGenerator : AnyGenerator<StoryBookState> { var optcase:StoryBookState? = nil override func next() -> Generator.Element? { if let cas = optcase { switch cas { case .Welcome: optcase = .Praise(nil, nil) case .Praise: optcase = .InvitationToRepeat(nil, nil) case .InvitationToRepeat: optcase = .TurnToNextPage(nil) case .TurnToNextPage: optcase = .End case .End: optcase = nil } } else { optcase = .Welcome(nil) } return optcase } }Second, we need a way to parse the source code and extract the case labels. For some reason, I couldn't get String(contentsOfFile) to work. Fortunately, someone on stackoverflow was kind enough to post a class that'll read each line of a file into a [S

There are workarounds for OS X. I have not been able to find any for iOS. For OS X, you can listen to external notifications (input in a support app), build in-playground windows with NSTextFields, or use Alerts to solicit user interaction.

Dex, I tried calling init() (I'm working in Swift, but init() should be equivalent to -init). If I call super.init from my UIView subclass, I get Must call a designated initializer of the superclass 'UIView'. If I try to override init(), I get Initializer does not override a designated initializer from its superclass. This leads me to believe -init is not (yet) a viable alternative. I haven't heard the session where they mentioned that -initWithFrame: was no longer needed, but that would be awesome because it's never made sense to set a frame when using auto-layout. Maybe this change is just not in the current build yet?

Same issue for me too. And it looks like it started to happen since yesterday. All the builds have gone haywire. I will try to resubmit another build though. And contact the Apple review guys.