Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for

In the Swift 2 Prerelease for the Swift book, it states:“There are some cases in which you know a throwing function or method won’t, in fact, throw an error at run time. In these cases, you can call the throwing function or method in a forced-try expression, written, try!, instead of a regular try expression.Calling a throwing function or method with try! disables error propagation and wraps the call in a run-time assertion that no error will be thrown. If an error actually is thrown, you’ll get a runtime error.”https://developer.apple.com/library/prerelease/ios/documentation/Swift/Conceptual/Swift_Programming_Language/ErrorHandling.html#//apple_ref/doc/uid/TP40014097-CH42-ID508(there is no way to deep-link to the relevant section but it's the second from last, Disabling Error Propagation.)If you have a chance to watch the video posted on the developer site from the What's new in Swift session, it's well worth it. I think that's where I saw this.

Can confirm this is in the public beta for iOS 8.4 (12H4125a) too. Both my iPhone 5S and iPad Mini 2 will no longer connect to my university's WiFi as it uses WPA2 Enterprise.

Try to go into the Watch app in the iPhone simulator then uninstall and reinstall your watch app from there.

I too have been experiencing the same very fast battery drain that you are all talking about. I have an iPhone 6 16GB. I just recently re-install iOS 9 right over my previous iOS 9. Since doing this my battery life experience has greatly improved. I can't exactly say that things are back to normal but very much better than before I re-updated. I did try re-installing iOS 8.3, restoring from backup and then upgrading to iOS 9. 1st and 2nd time same results, battery life out of control. Now that I just updated right on top of iOS 9 and things have greatly improved. If things change I will re-post. Good Luck!!!

If you want to debug both of the processes at the same time, here's what I'd do. First, run the app on the watch simulator. Then, open up the app on the iPhone by tapping on the app icon. Then, go to Xcode, then the top menu Debug -> Attach to Process, and select the process for your iPhone app. This should have both apps running in the debugger simulatneously. Now you can insert breakpoints or whatever and ensure that you are properly activating the session on both sides.I haven't played with WCSession yet and gotten it working, but this might help you find an issue. I will give it a go when I get a chance soon hopefully!

Reposting this with more info:When the beta came out yesterday, I did an upgrade and not a restore. Today I litterally watched the battery percentage drop 1 percent every two minutes while I only had the home screen active (background apps disabled, location services disabled, etc). I kept checking the Settings -> Battery page and it show Home Screen at 15% of the usage, which was completely wrong.Today I did a complete restore and now things are better. The Settings -> Battery screen not only showed Photo App as the top user (I have over 8 gigs of phots and videos), but it also showed it as Background Activity. I didn't see that before I did the complete restore. Now, Mail, Messages and Calendar also show that. I'm sure the battery will still drain faster than with a production version, but at least it seems like the reporting is working correctly and it allowed me to understand what was sucking the life out of my battery.---------------------------------------------------------As an update, I have an

Same issue - Mid 2010 MBP.Application Specific Information:Assertion failed: (ctx), function CIEAGLContextCreate, file /Library/Caches/com.apple.xbs/Sources/CoreImage/CoreImage-327.6/Framework/misc/CIEAGLContext.m, line 261.