“translate scheme”

I'm developing an open-source library, and I want to run XCode 7's new code coverage on my unit tests. You can download the library at https://github.com/zeveisenberg/bonmot if you want to follow along at home.I opened the example project, went to Prduct -> Scheme -> Manage Scheme, went to the Test pane, and checked the Gather Coverage Data box. When I ran my tests, I got coverage data for all the classes in the sample project (cells, views, view controllers, main.m), but nothing for the classes in my library (BONChainLink, BONTextAlignmentConstraint, BONTextConfiguration, UIImage+BonMotUtilities). Has anyone had any luck with this? I tried enabling the Generate Test Coverage Files flag in build settings for the Pods Xcode project, but no dice.

Dear all,Do you know an internet forum or a Google group dedicated to the development of an open source web browser written in Swift language ?If it does not exist, it is urgent to create this group because, as this browser does not exist, there are many things a web browser running on an Apple device can not do.The simplest is to develop a free web browser Swift language starting with translating the C ++ code of Chromium in Swift language.Thank you. 🙂Sincerely,Naomi

I am new in Xcode. This may sound silly. Can Xcode upload the output only to the devices listed in the scheme list? For instance, uploading to iPad mini is not possible?

Hi all,I’ve got an app that can read files from normal file:/// URLs, and also URLs with a custom scheme of my design. This all works pretty well as long as autosavesInPlace returns false. However, when I change autosavesInPlace to return true, suddenly I get this console warning on opening a document with my custom URL:Failed to read draft status extended attribute for document at: /Foo. No such file or directoryWhat it’s apparently doing is to use the path portion of my non-file URL and interpret it as if it *were* a file URL, and then try to set an extended attribute on it. Obviously, we can’t have this. If the path component of the URL happened to coincide with a path to some actual file on the file system, we would mangle it, which is clearly unacceptable behavior.One would think that setting the document’s ‘draft’ property to false would be sufficient to tell the system that this, in fact, isn’t a draft, but this has effect on this warning. A little digging through the assembly reveals the foll

While I can understand companies like Twitter abusing the privacy of a user with canOpenURL, this change negatively impacts applications that want to opt into a system where app detection is a heavily-relied on feature. This is especially the case for enterprise apps that utilize a common library to do secure inter-app communication. Because this list of apps keeps growing, it's unfeasible to have every app using such a library to maintain the list of every other app's schemes.I've posted a bug report on this but there hasn't been any feedback. I'm hoping this forum post could provide more visibility. I have a suggestion on a solution that doesn't compromise the privacy enhancement that comes with this change and yet would allow for app discovery:Lets say you have apps A and B. Here is the relevant portion of their Info.plist:App A:<key>CFBundleURLTypes</key><array> <dict> <key>CFBundleURLName</key> <string>CompanyASchemes</string> <key>CFBundleURLSchemes&

Hello everyone,We want to use xCode Server to run automated tests, and we encouter a problem here. xCode Server picks up wrong target when it builds the test scheme.Here is the details. We have three targets, call it OurApp, OurApp-ent, and AutomatedTests. The AutomatedTests target is a test target with host application being set to OurApp. A scheme called AutomatedTests is created based on the AutomatedTests target. So this scheme SHOULD only depend on the OurApp target and it should NOT depend on OurApp-ent target. If we build or run this AutomatedTests scheme within xCode, it works fine. It builds only the AutomatedTests target and the OurApp target.Then we create a Bot based on this AutomatedTests scheme. Then we have trouble. Sometimes xCode Server just builds the OurApp and AutomatedTests targets. This is correct. But SOMETIMES, xCode Server decides to build the OurApp-ent target as well, without any change in the source code or the settings! And this will fail becaus

Hi,I am planning to create an app to translate dirty words into 5 languages. Do you know if Apple puts some restrictions concerning dirty words in apps' contents ?I have read all the app store guidlines, called customer service 5 times, asked so manyquestions on forums and can not find a clear answer.Thank you in advance for your help,Avi.