DTiPhoneSimulatorErrorDomain Code 2

You wont actually notice anything when you hit the button, no pop up or anything. But after about 2 mins you should notice all is resynced.

Well, first thing...and sorry to say this: XCode will not automatically 'port your Apple Watch code. All you really have to do is create new apple watch target. XCode will do that for you and then you must copy all your code and xib's, assets, storyboards yourself. Apple says this in their transition to watchos2 document.(Sorry, i don't know how to reactivate migration assistant but this is the answer you will end up with anyway...migration really isn't migration with XC7)

additional observation - when on batter in the lower left it shows mailbox activity - well while on battery it shows steps 1-2 waiting for AC power... but I can not seem to find any settings to change this. (still working with just 1 exchange account)... will not sync even when manually syncing...

I was wondering the same thing, I would really like to use the new UI testing features but as soon as I open my project, Xcode 7 forces me to upgrade the project to Swift 2.Is there a way to use Xcode 7 while maintaing the Swift 1.2 code base?

Sorry I can't point you to any sample code off the top of my head, but this sounds like a perfect application of NSOperationQueue and operation dependencies. You could add an operation for each download. You can set the max concurrent operations to limit the number of concurrent requests but still have parallelism. You could add your processing operation with an operation dependency on each of the download operations so it wouldn't start until all the downloads were completed.Posting sample code to show multi threading synchronization is fraught with peril anyway since every situation is different. But in general, if you are accessing a common data structure from multiple threads, you add a synchronization primitive around each and every access to that data structure (read or write), and try and ensure that you don't deadlock. Don't hold the lock while you're doing a long network operation, for example - do the network operation, then lock / update / unlock. I use Obj-C so I've been doing it

1.) Check the iTunes Connect FAQs for details, but remember that daily reports are not to be considered dead accurate, and are calculated on a fiscal month...only the monthly financial reports are valid to reference for payouts.2.) Monthly. But know there may be conditions where earnings for a given month don't meet the payout threshold, which might delay payment until the next month. Again, see the iTC FAQs.

While I have the same take on this as the other two posters Apple explicitly statet the fact in the past.This time - if you look into the XCode 7 release notes - there's this section:Submitting an archive built with BITCODE_ENABLED=NO will fail during upload. (21247555)Workaround: Build the archive with BITCODE_ENABLED=YES and then uncheck the “Include bitcode”option when distributing the archive (functionally equivalent).Not sure about the reasoning behind that, but why mention that you have to takecertain extra steps when submitting with the beta if it is - as always in the past - not allowed?

You can. I did and the update process did work fine for me after the invitation code being unlocked for the German AppStore.But I found, 10.11 has way more bugs than 10.10.4 beta, so, for example, for me, Photos is not launching anymore and I got a problem with iCloud mail in Mail while all other accounts I got in there continue to work fine.

Not sure why you're trying to assign two things on the same line there. You should use separate assignment statements for clarity. In any case, you can't assign directly to your destination view controller's UI widgets from prepareForSegue. (It's bad style - a violation of MVC - but more importantly, the view has not yet been loaded at that point, so any outlets will be nil.)prepareForSegue should pass data / info to the child - here is the information you should display. It is up to the child to decide how and when to display it. Could be a UILabel, a UITextView, a UIButton, render fancy graphics into a UIImage, whatever - the parent should not know or care. The child should usually do this (populate its UI widgets based on the data it is supposed to display) in viewWillAppear.I have no idea what that repeating content error message means, but I suspect you have done something funky / non standard in the way you've set up your outlets. Might be worthwhile to watch some videos where they do it (e.g.