A Summary of the WWDC25 Group Lab

For sure! (I suppose you are talking about the second case)First, you have to create the shared container in the project or the provisioning portal. In Xcode you can do by selecting your target - capabilities - App Groups, activate the feature, and clicking in the plus sign. Use a new identifier (usually in the form group.yourcompany.yourapp).Assuming you have downloaded a file using NSURLConnection (https://developer.apple.com/library/prerelease/watchos/documentation/Cocoa/Conceptual/URLLoadingSystem/Tasks/UsingNSURLConnection.html - listings 2.1 through 2.5, easy source code) you'll have a NSMutableData with the content of the file. After that, you need to store in the shared container you created.The code that performs that is something like this: NSMutableData *soundFile=[yourDownloadedNSMutableData]; NSURL *container= [[NSFileManager defaultManager] containerURLForSecurityApplicationGroupIdentifier:@group.yourcompany.yourapp]; NSURL *filePath = [container URLByAppendingPathComponent:@yourFilenam

I want to optimize reading and writing of large files.Ah, yes, that’s one of the “various possible reasons” I was mulling over.The gotchas that spring to mind here are:Core Storage, where one volume is outside of the volume group and one volume is insideRAIDdisk imagesIt’s possible to write code to do the right thing in each of these cases (you typically do it by taking the disk’s BSD name, mapping it to an IOMediaBSDClient in the I/O Registry, and grovelling around from there) but there are serious drawbacks:it’s a whole bunch of ugly special case codeyou will also find more special cases further down the pathKeep in mind that a lot of folks use SSDs these days (although maybe not as many in your market as in the general market) and doing multiple streaming operations on an SSD is not the horror show that it is on spinning rust.All in all, it might be easier to use stick with your whole disk approach (-: That’s certainly a reasonable base heuristic.Taking a step back, all the special cases, both goo

After doing that (I also use Sparkle), now Xcode 7 crashes when I try to export a Developer ID Signed application from the OrganizerProcess: Xcode [11920]Path: /Applications/Xcode.app/Contents/MacOS/XcodeIdentifier: com.apple.dt.XcodeVersion: 7.0 (8223)Build Info: IDEFrameworks-8223000000000000~15Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: Xcode [11920]User ID: 501Date/Time: 2015-09-18 07:52:42.112 -0400OS Version: Mac OS X 10.11 (15A282b)Report Version: 11Anonymous UUID: 98FBD7C6-A1F5-E174-F66F-39ECB5EA836CSleep/Wake UUID: 3A17E47B-4DDE-480D-BB55-042228B926E1Time Awake Since Boot: 400000 secondsTime Since Wake: 500 secondsSystem Integrity Protection: enabledCrashed Thread: 0 Dispatch queue: com.apple.main-threadException Type: EXC_CRASH (SIGABRT)Exception Codes: 0x0000000000000000, 0x0000000000000000Exception Note: EXC_CORPSE_NOTIFYApplication Specific Information:ProductBuildVersion: 7A218UNCAUGHT EXCEPTION (NSInvalidArgumentException): -[NSTaggedPointerString count]: unrecognized selector

We would strongly recommend that you use AVPlayerViewController for media playback experiences. You may want to use a custom approach if you do not require playback controls, or if the media playback experience needs to be atypical in nature.You can handle marking regions as interstitial content by setting the interstitialTimeRanges property of your AVPlayerItem. You can also set metadata for the item manually (if not contained in the media asset) using the externalMetadata property, and manage chapter groups using the navigationMarkerGroups property.By setting an intersitial timerange, that region of the timeline will be collapsed, and you will receive callbacks to your AVPlayerViewControllerDelegate as the player enters and exits the interstitial regions, allowing you to adjust playback behaviour or seek past ads if appropriate.Take a look at the discussion of these items in the documentation for AVPlayerViewController for more information.

Good summary of the issues. I didn't realize didAppear was a bug and have spent literally dozens of hours wrestling with watchConnectivity over the past three weeks. This makes so much sense.Other bugs I've run into:•iTC doesn't allow healthkit in UIRequiredDeviceCapabilities plist: https://forums.developer.apple.com/thread/15917• Healthkit workouts on watchOS2 stop/end after less than 1 min on real watch but continue until stopped on simulator.

If you're using watchOS 1 you need to ensure that both the iOS app and watch extension have a provisioning profile configured for App Groups, and configure the App Group name in the developer portal (where you set up provisioning profiles).If you're using watchOS 2 you can't use App Groups to share files since the watch extension runs on the watch, not the phone. The WatchConnectivity API needs to be used to coordinate data transfers or sharing of app data.

Right next to volume in Settings -> Remotes -> Home Theater group. It's called Turn your TV on with your remote

In the panel which is called Summary after your click Export in Xcodes organizer window. It shows the app icon and Binary and entitlements. On the buttom you will find two checkboxes for including symbols and bitcode.Jochen

I have the same issue on this threadSome people are saying they can do it with just the app group, I have been trying all day erryday and still cannot get it to work.