file uri scheme

Anyone else test and track using OS X with Exchange? I've filed several bugs over the last few releases, and it'd be helpful to compare notes.

I just spent all day migrating my 30,000-line Swift project to 2.0 and was rewarded with this lone error. Any clue what it means? Is it yet another internal error?Assertion failed: ((IGF.IGM.DataLayout.getTypeSizeInBits(coercionTy) == IGF.IGM.DataLayout.getTypeSizeInBits(paramTI.StorageType)) && Coerced types should not differ in size!), function emitDirectExternalParameter, file /Library/Caches/com.apple.xbs/Sources/swiftlang/swiftlang-700.0.38.1/src/swift/lib/IRGen/IRGenSIL.cpp, line 908. 0 swift 0x0000000106f20e0b llvm::sys::PrintStackTrace(__sFILE*) + 43 1 swift 0x0000000106f2154b SignalHandler(int) + 379 2 libsystem_platform.dylib 0x00007fff94a83f1a _sigtramp + 26 3 libsystem_platform.dylib 0x0000000000000003 _sigtramp + 1800913155 4 libsystem_c.dylib 0x00007fff9c270b53 abort + 129 5 libsystem_c.dylib 0x00007fff9c238c39 basename + 0 6 swift 0x000000010506869d (anonymous namespace)::IRGenSILFunction::emitSILFunction() + 13693 7 swift 0x0000000105064d52 swift::irgen::IRGenModule::emitSILFu

It doesn't seem to be possible for me to debug on device wtih my apple watch. I can run my develpment app normally, but Xcode just can't seem to attach to a debugging session.I've read the relase notes and have tried:1) deleting the app/apps from devices and trying again2) ensuring Show App on Watch is on for dev app3) restarting all of: watch, phone, xcode, mac.4) unpairing / pairing againNo dice.When I click Run on the [AppName] WatchKit App scheme, the status window says Running [AppName] WatchKit App on [Phone name]. It stays like that for about 45 seconds. Then it says Finished running [AppName] WatchKit App on [Phone name].It really seems like the Phone->Watch connection is just way too slow. When I launch Xcode, it takes about 2 minutes before it considers my Phone+Watch pair as eligible for this scheme. During this initial 2 minutes, if I look into Window->Devices I don't see my watch listed even though I can clearly see it is paired.I'm going to turn this into an official bug

Hi All,I'm not sure if this is in the correct place since the new forums organisation, mods feel free to move if not.So i am Using AVFoundation to capture video and audio from an external device and to write to a ProRes encoded *.mov file.I started with an application that only writes video buffers to a file, and this works fine, producing a ProRes encoded .mov as expected.However when i add the Audio AssetWriterInput to the AssetWriter, the file that gets created appears to be invalid.I have checked all the return values for each step of the operation, and everything appears to be ok, it's not until i call finishWriting on the assetWriter at the very end of things that i get an error. Sadly checking this error reveals the -11800 AVErrorUnkown error, which isn't much help.Now, a few things to note- I am trying to create a file with multiple tracks of uncompressed audio. Eg 48Khz, 16-bit, however for the sake of simplicity currently my sample only uses 1 track, which means only 1 AVA

We read through all of the documentation, Xcode 7 header files, and tried to summarize everything we could figure out about watchOS 2. We hope this is a quick jumping off point for developers who just want a quick description and links directly into the Apple documentation. http://www.sneakycrab.com/blog/2015/6/8/watchos-20-tldrPlease give feedback, corrections and new discoveries, and we'll update the post with new information as we find it.

I have a question regarding xcodebuild. I have created a static library and I want to build it and create my .a file without using Xcode. I run xcodebuild from the terminal and it runs without generating an error and tells me that the code is built but there are no files generated in product folder. Any thoughts?

Hi All,I installed new OS X on my External Drive. I use some 802.1x configuration, imported with profile manager of OS X Yosemite Server.When I import the config file I received a generic error.My questio is: I must create a new profile mangere config file with new version of OS X El Capitain Server?Tnx

During the installation of OS X El Capitan on my Mac Book Pro , the install fails and I am left with OS X Could not be installed on your computer File System verify or repair failed. Quit the installer to restart your computer and try again. No matter how many restarts I do it does not install. Also repair does not work in disk utility. Please help me if you know what to do.

I have rebuilt my app using XCode 7 and am testing that it works on my watch running watchOS 1.0.1 before I upgrade the device to version 2.0. Everything seems fine so far except that my groups do not have their custom insets (all zero) but instead have insets of 2. If I change the insets to larger values then it seems to work as expected, but not for zeroes.This works fine in the simulator (which runs 2.0) but not on the watch when running 1.0.1. I notice that the new API offers the ability to set the insets at runtime (which is very useful - thanks for that) so I'm wondering if this is related to that?Sounds like I need to file a bug report but I thought I'd mention it here in case anyone else notices that things are positioned strangely when running an app built with XCode 7 on a watch running 1.0.1.

I have this scenario:My app relies on a framework + bundle.Bundle has xibs.Classes for xibs reside in framework.Their images reside in xcasset files of the framework project.I can quite see the xibs + view controller classes rendering view controllers though they reside inside bundle & framework, respectively.But images aren't coming where I placed them in xibs.I have imported framework + bundle inside my app.But how can I use images inside the framework project's xcasset?How do I tell framework xibs to find images from framework xcassets (or any optional way) ?[so far, xcasset file isn't part of the bundle despite I copy it in 'copy bundle resources' phase.If I import all images into my app's xcasset - even that won't work because app expects them inside the imported bundle, not the main bundle.]