“DTiPhoneSimulatorErrorDomain Code 2”

Did an upgrade to El Cap on a spare iMac machine. Everything upgraded smoothly but the Magic Trackpad constantly freezes for a couple of seconds, the trackpad disconnects itself then immediately re-connects itself. This doesn't happen with the wireless keyboard, just the trackpad.1. Anyone seeing similar behavour?2. Anyone any clues what might be going on and any workarounds.I did try the basic: removing the trackpad and re-pairing it, but didn't solve the disconnect / re-connect pattern.

It might be me, but iOS 9 Battery life so far has been painfully bad, down from 100% to 85% without using it much in 2 hours... has anyone experienced anything similar?'I might try a complete restore since i only updated from iOS 8 to iOS 9 Beta, just curious to see if anyone else is in the same boat.....after all ...battery life is one of the focus for iOS9.Andrea

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 AVAssetWriterIput for the audi

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.

Hey everyone. I wasn't sure which section to put this in but this was the most relevent i could find.Im new to all this and this is my first app so bare with me.I've created an app using Unity and then built it through xcode. When submitting to the app store i got 3 crash reports. I've tried to understand them but I cant seem to get my head around what they mean.All 3 crash reports are fairly simmilar with the following error: Exception Subtype: KERN_INVALID_ADDRESS at ... I will post one example below. If you want the other 2 reports then just ask!Thanks for your help!Incident Identifier: 938FFF53-56A2-4A1D-BF23-4E24567BA101CrashReporter Key: 3286a932eadfb6a4501de9b1e0044450b3f54fb3Hardware Model: xxxProcess: Box [1376]Path: /private/var/mobile/Containers/Bundle/Application/00E4561A-F30C-4C48-B2BD-355A71A4D971/Box.app/BoxIdentifier: Bob.BobVersion: 1 (1)Code Type: ARM (Native)Parent Process: launchd [1]Date/Time: 2015-06-02 17:16:47.033 -0700Launch Time: 2015-06-02 17:16:42.956 -0700OS Vers

I originally posted this in the old Developer Forums, but didn't get a response there.I have an app written in Swift with a WatchKit 1 (i.e. not beta) extension. I have a few different actions that I want to connect to menu items.The problem is, more often than not, hitting the menu item fails to fire the action. Sometimes it works once; usually it doesn't work at all. Buttons connected to the same actions work perfectly, but I don't want visible buttons in the UI for these features. The problem is not with the code in the action failing to have an effect—a breakpoint in the action is not hit. Has anyone seen anything like this before? Any idea what might be causing it?

Even if the watch must deactivate the app when a user lowers there wrist (though preferrably not) we desparately need for apps to be guaranteed to become active again when the wrist is raised again. An opt-in would be the perfect option. Obviously not all apps should do this so you'd want a way for users to decide.I develop a fitness timer app that users check regularly. Once tired and sweaty if the user raises their wrist and the app is no longer there it's too much to ask for them to use the fiddly app selector interface to get the app back. At that point they probably just assume the app has crashed and will no longer use it. And who can blame them.The only option is to select that the last activity always becomes active, but who wants their watch to do that? If this has not been addressed yet, it absolutely needs to be.I'm currently in the ludicrious position of telling the users that are asking for a watch app that the Apple watch is no good for timing apps!