“translate scheme”

I submitted two apps (same app with iPhone and iPad versions) on the same day (Aug 27 if I remember right). They both had the words Fixes for iOS 9 in the release notes among many other items. Both apps went into review a week later. One passed (the less important iPad version) while the other was metadata rejected for violationg section 2.3, which says we can't make mention/reference to unreleased or beta software. So I deleted that iOS 9 statement (wasn't even important compared to other parts of the new app version, in the grand scheme of things) and have been waiting for review for 7 days now.I see the mention of iOS 9 in release notes for a lot of apps on the App Store, and based on my experience, some apps go through and others get metadata rejected. It must depend on who reviews the app and how strict they are. Anyhow, it's annoying. At this rate, iOS 9 will be released before my app is reviewed again, which makes the whole rejection moot.In the past, metadata rejected meant a short delay -- b

Same here. Can run DemoBots in an AppleTV 1080p simulator no problem. But when adding a new scheme and target to an existing app, the AppleTV simulator does not appear next to the scheme as a destination. Just a Build Only Generic tvOS Device that you can't run anything on (when you try you just get a error dialog: A build only device cannot be used to run this target. No supported tvOS devices are available....However the AppleTV 1080p simulator can still be seen in Window->Devices

tvOS does support Custom URL Schemes, but support for a given scheme is up to the individual developer creating the app that will host said scheme. You will need to get in touch with the developer of the app you wish to interact with to determine if they will support the use case on tvOS.

That's incorrect, ErrorType is a protocol. The reason this works is because of compiler magic. The compiler automatically emits the code necessary to translate between any ErrorType and NSError.

This seems to be fixed with iOS9/watchOS 2/Xcode 7 GM. The watch app still gets uninstalled for some reason (possibly by building & running just the iOS scheme after having previously built the watch extension scheme?) but it is able to be installed from the Watch app on the iPhone without the need to run from Xcode again.

I have couple of suggestions for you:1. move testing code from the main target to test target (for this you can use ObjC categories)2. move testing code from the main target to a separate target and include that target in the main target, or, even better - only in the test target3. you can add your own User Defines in the main target and wrap your test code in that define. When building test target you can set inside of the test build scheme additional flag that will be automatically passed through to the main target when test target is being builtAbout pt. 3 this is purely theoretical, I never tested this, but it should be possible

I think the problem appears when I compile the simulator slice of the library with the -fembed-bitcode flag. In other words, I use now the bitcode flag only when compiling the library for the device and it works fine.Here is a part of my build script# simulator without bitcode fail unless system xcrun xcodebuild -workspace #{WORKSPACE} -scheme #{SCHEME_SDK} -configuration #{configuration} -sdk iphonesimulator9.0 -derivedDataPath #{derived_data_path} clean build | xcpretty -c # device with bitcode fail unless system xcrun xcodebuild OTHER_CFLAGS='-fembed-bitcode' -workspace #{WORKSPACE} -scheme #{SCHEME_SDK} -configuration #{configuration} -sdk iphoneos9.0 -derivedDataPath #{derived_data_path} clean build | xcpretty -c # fat library arm_file = #{derived_data_path}/Build/Products/#{configuration}-iphoneos/lib#{target}a x86_file = #{derived_data_path}/Build/Products/#{configuration}-iphonesimulator/lib#{target}.a final_file = #{BUILDS_SDK_LIB_DIR}/lib#{target}-#{sdk_version}.a fail u

Update: the Watch was listed as fully available twice throughout my afternoon. I have no idea why. In any case, this apparently hasn't stopped me from embedding and installing my Watch app or anything – just from selecting a debug scheme involving the Watch.

Followed the email link. I think you'd best get your email sorted - not sure if there is any other notice scheme.

Your first post/link shows the text from the rejection, but the followup shows the icons, thanks.I get your scheme for why you 'reduced' like you did, but I'd keep it simple and let something such as OS X's Preview or GraphicConverter 'resize' instead. Then let App Review deal with/decide any artifacts, etc.

I really wish it were that simple. I did try that multiple times and still get the same error. When I build the phone application the watch app dies silently and when I try to run the watch scheme it gives me that error. This also happens with a fresh project and vanilla watchkit app and extension.

Parse has released version 1.8.3 which supports ios9, bitcode. It is only available in objective-c for now. I added it to main ios app and it builds. Main app works, but my watch app notification scheme does not build.