dsym file

You need to configure an app group and enable the same in both the extension and the containing app. This way the extension can share data or files with it's containig app.Dirk

I filed a,radar,on this a couple of days ago, dont have the number handy, but it is in the system.

Remember, there are two ways to share code between targets - frameworks, and just including the .m or .swift file in multiple targets using Xcode's inspector. I've not started using Xcode 7 yet, but in one app I have a framework that is shared between the iOS app, the iOS today widget and the watchOS 1 extension.From what you've described, that framework isn't going to work with a watchOS 2 extension because that extension runs on a completely different device. Which makes perfect sense! However, instead of creating a new Watch Framework target, including the same files in that target as in my existing framework and linking the watchOS 2 extension with that framework, an alternative might be to simply add those files to the watchOS 2 extension, cutting out the need for a framework entirely. There's not more than one target running on the Watch to share code between, so a framework doesn't really save you any space (which it does on iOS when used by multiple targets).In my case, not

It didn't even occur to me to have the same source files for multiple targets. It looks like this was implied on this thread. In my case, you are right that because there's only one watch app using code in my framework, I won't save space (I'll potentially use more space). However, because I've already isolated much code into a framework, it should be a simple migration step to add a Watch framework and add all the source files to this new target. I could add these files directly to the watch extension target and avoid app groups on the watch, but I think I'll stick with the framework for now. You never know when you'll have a second watch app.

Below is the Webkit Browser in 30 Lines of Swift from practicalswift.com, with some small changes to make it run on latest beta with Swift 2.(Omitted link because this will get stuck in moderation otherwise ...)1. Create a file called browser.swift (or whatever) containing this:#!/usr/bin/swift import WebKit let application = NSApplication.sharedApplication() application.setActivationPolicy(NSApplicationActivationPolicy.Regular) let window = NSWindow(contentRect: NSMakeRect(0, 0, 960, 720), styleMask: NSTitledWindowMask | NSClosableWindowMask | NSMiniaturizableWindowMask, backing: .Buffered, `defer`: false) window.center() window.title = Minimal Swift WebKit Browser window.makeKeyAndOrderFront(window) class WindowDelegate: NSObject, NSWindowDelegate { func windowWillClose(notification: NSNotification) { NSApplication.sharedApplication().terminate(0) } } let windowDelegate = WindowDelegate() window.delegate = windowDelegate class ApplicationDelegate: NSObject, NSApplicationDelegate { var _window: NSWi

I read about SpriteKit and texture atlases a bit more, and it looks like the trimming is considered a feature rather than a bug.https://developer.apple.com/library/ios/recipes/xcode_help-texture_atlas/AboutTextureAtlases/AboutTextureAtlases.htmlThose new images are automatically rotated and trimmed to fit the maximum number of images into a single file...So it sounds like you would need to use the 1% alpha workaround you mentioned above, or use the default centered anchor point on the sprite and textures.

Anything from the Xcode 7 b releases notes shed light?Playgrounds Opening a Playground that was previously displaying the Version Editor may present an alert stating, “The file “MyPlayground.playground” couldn’t be opened because you don’t have permission to viewit.” (20623808). Workaround: Dismiss the alert dialog and show the Standard Editor (Command-Return).Playgrounds sometimes show a window with no editor if they are opened as part of Xcode launching (20694143) Workaround: Close and re-open the playground.Executing an iOS Playground for the first time may take longer than subsequent executions. (21163503)For old-style playgrounds, the menu item Edit->Convert->To Latest Swift Syntax... is greyed out. (20902099) Workaround: Upgrade the playground before attempting to convert to Swift 2.0 by choosing Editor- >Upgrade Playground...Playground pages may recompile each time they are navigated to, even when there are no changes. (21177662)Playgrounds live views may not show images when using th

For tiny data (strings, dates, numbers etc.) there is NSUserDefaults or the keychain.For medium sized data (or lots of tiny data) there is Core Data or SQLite (I like SQLite with FMDB) or some other database.For large data like audio files or PDFs I would think individual files on the file system. Take a look at NSFileManager and related guides - there's lots of documentation on the Apple dev site. (File System Programming Guide)

I am having the same issue, but later in my testing than in launch. Nothing is happening in my app that should be preventing the test from proceeding. If I record the app, it is able to move past but not when it runs the test or any variation of it. The line that fails for me is a button press. It correctly identifies the button but fails when I try to tap the button. t = 46.93s Tap the dropbox files Button t = 46.93s Wait for app to idle t = 76.95s Assertion Failure: UI Testing Failure - App failed to quiesce within 30.0s/xxxxxxx.swift:57: error: -[XXXUITests.XXXXUITests testDropbox] : UI Testing Failure - App failed to quiesce within 30.0s