file uri scheme

Post the crash log. (the header and crashed thread, at least - don't need the long list of binaries)If it is symbolicated, it should contain the source file and line number if any of your code is involved in the crash. If it's not symbolicated, drag it into the Device Logs view in Xcode's Devices window when you have a device connected. Xcode should then symbolicate it.

Many people had this same issue. I solved it by deleting all files from the following folder:/Users/<YOUR HOME FOLDER>/Library/Application Support/iCloud/AccountsThen reboot.I was then able to get into the iCloud preference pane, where it asked me for my new password. After giving it, all was working again.

I have the same problem but only when building for the simulator, if you make your target an actual device xcode seems to use these .tbd files correctly

I am seeing this problem as well when I activate whole module optimization in Build Settings.Since I have a ton of Swift files on the command line (shown in the dump), I was wondering if there was a way to tell the compiler to indicate which particular file it was working on just before the crash happens?----------------------------------------------------------------------Assertion failed: (D->getSourceRange().isValid()), function buildDeclarationRefinementContext, file /Library/Caches/com.apple.xbs/Sources/swiftlang/swiftlang-700.0.38.1/src/swift/lib/Sema/TypeChecker.cpp, line 946.0 swift 0x000000010378ae0b llvm::sys::PrintStackTrace(__sFILE*) + 431 swift 0x000000010378b54b SignalHandler(int) + 3792 libsystem_platform.dylib 0x00007fff8b2adf1a _sigtramp + 263 libsystem_platform.dylib 000000000000000000 _sigtramp + 19601246724 libsystem_c.dylib 0x00007fff8fe4cb53 abort + 1295 libsystem_c.dylib 0x00007fff8fe14c39 basename + 06 swift 0x0000000101defe92 (anonymous namespace)::TypeRe

Now I've been able to run my iPhone 6 128GB with iOS 9 beta 1 for 40 minutes straight in standby mode (just viewing some e-mails from time to time, mobile data enabled, all background stuff disabled with not even 1% loss on the battery. Battery saving mode is also disabled. Don't really know what I did.. All I did was viewing the log files through the device viewer in Xcode. Disconnected the cable after a while and ended up where I'm now.. Before viewing the logs in Xcode I rebooted the phone also. But I did not change any settings in the phone from where it was before so I don't really understand what's going onSoon it's actually 50 minutes without any battery loss.. still at the 97% as it was when I disconnected it from my Mac. Seemingly the background activity going on before on the home screen also suddenly stopped.I'm going to spend my weekend looking into this matter a bit deeper, just for the pure fun of it

Thank you!As a side note of the side note, I removed a lot of code, but your example is way better.I didn't know about that redeclaration though, thanks.I'm just going to file a radar then!

I can say that I usually make it from 6:30 to 17:00 with ~40% remaining on a regular work day (with iOS 8.4). With iOS9 I can make it from 6:30 to 12:00 with ~40% remaining. Definitely filing a BR on this one, hopefully it gets fixed in next release. There's a similar problem in WatchOS 2 with battery draining. I used to make it all day with ~40% remaining when I got home from work, now I'm lucky to have ~10%.

Odd, i used a VPN and the file worked fine. I guess it was something from my ISP.

It's definitely sandboxed---the core data files are being created, written to, and read from its Application Support folder in the sandbox Container. Does Xcode treat the sandbox differently when launching an application?Yes, Xcode and the OS have changed. I'll march backwards and see if I can figure out if one of those has made a difference. In other unrelated work I've found that the jump from Xcode 5 to 6 revealed a number of multithreading bugs, so I suppose this could be related.

I have a BR filed on this. They requested taptic data along with continuity data so we will see what else they request after the engineers take a look. They know it's an issue with this build, and are looking into it.