“Visual Studio Maui IOS”

If you're distributing an enterprise app, then it doesn't have to go through review so your question doesn't apply. But if by enterprise you just mean some arbitrary measure of developer size, no - it's a level playing field. An individual writing code on his laptop on the beach goes into the same queue as a company with hundreds of developers. That may not be true for the very biggest household names... companies like Facebook with deep OS integration probably do get special treatment. But the number of such companies is probably in the single digits.And @rromanchuk - I believe you are wrong about app reviews doing nothing. iOS users are much more willing to spend money and install new apps. They have an intrinsic trust that apps won't contain malware / spyware or mess up other apps on their devices. That is entirely thanks to Apple's hard line approach to app reviews. Long term that generates MUCH more revenue for developers. That is my experience at least. Even though there are comparable numbers

Thanks for the idea but I'd actually just like to stick with the current version of Swift for now until closer to iOS 9/Swift 2.0 release. From what I can see online this isn't possible - Swift version is tied to Xcode and you can't run an older version.

Same problem here. I managed to upgrade to 10.11 but cannot get the link to Xcode download or iOS 9 install. Dropped onto profile page too.

A google search suggests the conflicting method is from the StoreKit framework.https://developer.apple.com/library/ios/documentation/StoreKit/Reference/SKRequestDelegate/Generally, you could find the conflicting method/selector by commenting out your version, writing a call to that selector on an instance typed as id (and arguments of type id), and then using command-double-click to pull up the header in another window.id thing = nil; [thing selectorToFind:thing];

Another wifi connectivity issue confirmed for build 14E33b on WPA2 Enterprise. It will not authenticate. Same issue happens with iOS 9 as stated above. This is a pretty big issue.

It's not watchOS 2, it's iOS 9.Reading the iOS 9 release notes reveals that loss of Health data is a possible side effect of installing the beta, and that to avoid this you should make an encrypted backup to iTunes (unencrypted backups to iTunes and backups to iCloud don't backup Health data).

Maybe the certificate itself or one on the chain are a SHA-1 certificate? Google chrome doesn't support these certificates, even if isn't self signed, and maybe iOS 9 are doing it too.