“translate scheme”

Hi, just want to share my experiences with push (remote notifications) and potentially get some feedback.I just noticed that my app can not get a token when build with Xcode 6 using commandline tools and the app is running on iOS 8 or below.I get the following Error:<Warning>: No valid 'aps-environment' entitlement string found for application 'myApp': (null). Notifications will not be delivered. myApp[571] <Warning>: Failed to register for remote notifications. Reason: Error Domain=NSCocoaErrorDomain Code=3000 ...I use the following command line calls to build:xcodebuild -workspace ... -scheme ... -sdk iphoneos -configuration Release CODE_SIGN_RESOURCE_RULES_PATH='$(SDKROOT)/ResourceRules.plist' CONFIGURATION_BUILD_DIR=... ARCHS='...' CODE_SIGN_IDENTITY='...' PROVISIONING_PROFILE='...' OTHER_CODE_SIGN_FLAGS='--keychain ...' -archivePath '...' archivexcodebuild -exportArchive -exportFormat ipa -archivePath '...' -exportPath '...' -exportWithOriginalSigningIdentity -verboseUsing Xcode 7.1

Hi ! ^^I heard Scheme is not included in project file...so i heard we need to save out to other folder to share scheme with other developers in a same project...my queustions are1. Where scheme is saved ?? (Especially, I want to share pre-action script.. When I zipped project and give other person, script is gone.. no script remand in a project)2. How to save out scheme so that we can share a scheme file ?thanks ~~~

This may turn into a rant but I am looking for guidance on how to efficiently debug Watch OS 2 apps on the watch device. I must be doing something wrong because what is happening now is random, frustrating and time-consuming. Basically, it's a crap shoot to get it working and there are so many random behaviors it is difficult to describe what happens or to file a radar.I have no problems at all debugging my watch app on the watch simulators where I simply Build & Run, and the watch simulator eventually launches with my logging showing up immediately in the debug output window. So, I expected the same process choosing the scheme where my paired watch has the app and extension installed.What happens (besides trying to fight with my iPhone to keep it and the watch awake) is I click Build & Run and there are a bunch of messages flashing across the top of Xcode, and then I wait, and wait, and look up to see that the Stop button is dimmed and the entire process quit. Then I click B&R again, and

The Metal documentation makes it pretty clear that command buffers are executed serially, in the order they are enqueued (...and that committing without a prior call to enqueue implies the enqueue call).What is less clear to me, is if and how the Metal API allows one to establish dependencies between one command buffer and the next, for cases where the output of one command buffer is needed by the next one in the pipeline. Suppose that you have a simple sequence of render passes, implemented through separate command buffers issued on the same command queue:Pass 1: Render something to a texture.Pass 2: Use the texture rendered in pass 1 to do something else.Which would – at a very high level – translate into two serial calls to each command buffer:[commandBuffer1 commit];[commandBuffer2 commit];So where is the problem? I have ran into situation where the commands issued by commandBuffer2 seemingly start executing before the commands in the previous buffer are completely executed. It is an issue of tim

What I'd like to do is seed our app some data for some of my UITests. One appoach that I'm entertaining is to seed the data by replacing the app container with my own container (*.xcappdata). I can do this presently, when debugging my iOS app, by setting it 'Application Data' under 'Options' in the scheme editor. Is there a way to replace the app container in a similar fasion when running UITests?