build disappears

You can install and remove apps in Watch app. That where you see the app is showing installing status. You press the swith on the right. After a while, you will got the swich off and the app's removing status disappear. I have reported this as a bug and got a bug duplicated email, so I think there is someone in apple is dealing with this issue. In current and beta 1 wacthOS 2.0, if you install apps more than 1 simutenously, the apps' installation may stuck as your description. That also take a lot battery. Even worse, if some of you apps update in App Store in the same day. They will stick and you don't even know it.So the best way now, is when pairing your watch, choose install apps later instead of all. And install app one by one. The installing status will disappear when you have installed a app in Apple watch.

Using OpenAL from Swift within Xcode 7 beta 2, import OpenAL.AL causes the following error:error: umbrella header 'OpenAL.h' not founderror: could not build Objective-C module 'OpenAL'Maybe OpenAL framework exists, but not ready for use as module.

You can create a bundle name using any language you desire and you can even code in a foreign language if you like. In Mac OSX just make sure you add an input source supporting your language. (System Preferences > Keyboard > Input Sources) While in this area check that Show Input menu in menu bar is enabled. You can configure Shortcuts > Input Sources to leverage shortcuts if you need to move between one or more languages.I don't believe that the default development language cannot be changed. For example if-then statements and all other language constructs cannot be changed. You can use the input source defined above to write your comments and variables in Greek (or any other language) if you choose.I think that I would leave the English and Greek localizations since the English one will always be the system default (for new Xcode builds) and may lead to unpredictable results as Xcode continues to be ungraded.

How broken is syntax highlighting? If all the text is black, then SourceKit has crashed. If the keywords are colored, but nothing user-defined is colored, then the file isn't being indexed.Xcode 7 still seems to fail to display some errors (either live in the editing pane, or in the errors navigator, or both). Try building your project and see if that produces errors you haven't seen yet. Fixing the errors (and rebuiliding again afterwards) should allow you to get back on track.

nothing user-defined is colored, then the file isn't being indexed ... this would be the problem. How do I get the file to be indexed? It's definitely not a build issue ... the target builds and runs fine. Just some files that refuse to be indexed.

Ok, I think I finally know how to explain what I've been trying to say all along now, let's see how it goes : ) But first let's look at these from your previous post:let doublePrinter = Printer<Double>(123.456) let stringPrinter = Printer<String>(Hello)Just so that we are on the same page. Here, doublePrinter and stringPrinter are of two separate types. There is no type Printer, Printer is not a type (on its own). It's only by giving it a T (by entering some text in your code, statically, at compile time) that you can get a type from whatever that Printer thing is, and the type you get by giving it a certain T is not a subclass or anything of Printer.And as for the following, also from you previous post:Is there really no better way of unarchiving generic Swift structs without falling back to using bunch of Any values?I *know* that the unarchived structs are Printers. I want to let the compiler and typechecker know, too.Well, You know that because you happen to know about some runtime-specific str

The scheme's build action specifies which targets to build. Check that the right ones are being built.Assuming that's fine, then I'd start playing around with the file contents. What happens if you deliberately introduce an error? When you remove that error? What happens if you comment out all the methods? Put them back one by one?Does the project have Enable Modules (C and Objective C) turned on? If it's off, try turning it on. If it's on, try turning it off, building, and turning it back on again.

I still cant find the new beta. Is it back up yet? I still have build 13S5255d

When I set Enable Modules (C and Objective C) to No, the source files show all the highlighting and code completion. But it doesn't build becuase I am importing various modules into the app. When I turn it back to Yes and build, it builds fine but the problem returns. So something in modules is throwing it off but not sure what.

[SOLVED] Same problem here with Xcode 6.3.2 and LLVM 6.1.0. I am using waf as an external build tool.Breakpoints were working previously, but it stopped apparently after I changed the C++ standard library in the project's build settings. And it doesn't work changing back.I've tried to restore a previous snapshot and it doesn't work either.It worked for me to include the -g option for GCC (don't know why it worked before without that). But it seems this problem may have multiple causes. There is a post with somewhat detailed troubleshooting https://devforums.apple.com/message/1130832#1130832