“translate scheme”

If it works in a different scheme, then the most likely cause is that the target membership of the file is incorrect, or perhaps there's something wrong in the scheme itself.Is this Swift or Obj-C?

Objective-C. The target membership seems fine ... how do I check whether there's something wrong with the scheme or not? It indexes most of the files just fine ... just a few (important ones) that are off

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.

You should check out the Developing iOS 8 Apps with Swift Stanford course in iTunesU. In the first three lectures a calculator is developed that uses enum and struct to create a stack that handles numeric and string data. Then in the first part of the lecture 5 (if memory serves correctly) an example of translating the stack to a string and back again is shown. The approach used in that course may work for you.

(returning to the top level because the text boxes are getting too narrow)I think you're all wrong! You're confusing two different problems, one major and one minor. (Generic structs are the minor one.)The major problem is that any serialization scheme, to be useful, must encode the type of each object (by which I mean an instance of a class, struct or enum) in the archive. Not only does Swift not have a way of giving something for a type that's readily archivable, it doesn't provide you with a way of getting back, at deserialization time, arbitrary types from their serialized representations. That means you're forced to translate serialized types into type literals via a great big switch statement (or equivalent). That also means that your archiving system can only represent a finite number of the infinite number of possible Swift types, and the ones it knows must be known explicitly.Incidentally, there's another complication here that you haven't considered. In general, a class name in Swi

Even when you do manage to boot into the beta, the battery drain issues and instability of the OS makes it impossible to work with for more than 2-3 hours at a time, which for me is just about long enough for each session of development. The only way I managed to get past this update screen was to wait until the battery was drained completely flat. Once dead plug it into a charger and wait until there is enough power for the watch to automatically turn itself on to low power mode. Once in low power mode I found that I was able to browse through settings and to very quickly go to the reset option and reset the watch. It took 3 or 4 attempts as the watch kept rebooting as I was browsing the options but as the batrtery slowely charged I was able to get to a point where I could hit that restore button. I am still encoutning issues, such as very fast battrery drain, random restars and apple logo freezes however it doesnot restart without problem. For some reason low power mode does get you into the OS and was the

I ran into a similar situation. I have a few bots for different schemes-- one of the bots kicked off from a commit and I canceled it before it had finished. Unfortunately any subsequent integrations got stuck into a 'Pending' state. For various reasons, I did not want to wipe out these bots.What eventually worked was to delete all the canceled integrations (which had been stuck in the 'Pending' state) including the original integration I canceled that seems to have triggered this stuck state. After the canceled integrations were deleted, any following integrations worked as expected.

Have you tried cleaning the build folder before archiving, holding down the option key to get the Product >> Clean Build Folder... menu item?In one of the 6.3 beta versions I ran into problems with a generated header that wasn't updating/creating properly when I switched between different schemes, and maybe you are running into a similar problem?

Interesting. Yeah, that's really weird. Have you checked out the Zombie Objects or Address Sanitizer features? They might be able to help you pinpoint your problem. Both are accessible when you edit your scheme, head to the Run action and click on the Diagnostics tab. After enabling them, run your app. Now when it crashes, you'll get a detailed readout on what went wrong.Say, did you check to see if anything was wrong with your source file? Take a look in the File Inspector. Maybe also create another Swift file with a function in it that does the same thing as your setup code, and call that function from your original file. Other than that, I'm just as stumped as you are.