A Summary of the WWDC25 Group Lab

I have been really trying to incorporate the code into my app, however there is a couple of things I don't understand.In GroupOperation, when you call cancel() it calls cancel on all the operations in the queue, however if cancelWithError is called, this is not the case, why?It seems the pattern is to always call finish, even if the operation is cancelled as seen in evaluateConditions where it changes the state to cancelled but still calls finish() but if we would call cancel() on a group operation, all operations will be cancelled meaning finishOperation would never be called cause we cancelled all the operations in queue. Is it a must for any Operation that uses the timeout observer to subclass cancelWithError and call finishWithError itself?Another thing is that the error handling pattern seems to be wierd. It seems like each operation is showing error UI itself instead of letting the object that created the operation to decide what to do with the failure, even thogh the operation doesn't have any

Process: Xcode [80346]Path: /Applications/Xcode-beta.app/Contents/MacOS/XcodeIdentifier: com.apple.dt.XcodeVersion: 7.0 (8178.7)Build Info: IDEFrameworks-8178007000000000~3Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: Xcode [80346]User ID: 501Date/Time: 2015-07-29 19:22:01.335 +0800OS Version: Mac OS X 10.10.5 (14F6a)Report Version: 11Anonymous UUID: 58F6A28D-715A-E1B4-54D4-FEED8B09AB43Sleep/Wake UUID: ABCA5098-5B93-4BF9-BCAA-A4CD97A9D4BBTime Awake Since Boot: 130000 secondsTime Since Wake: 4400 secondsCrashed Thread: 0 Dispatch queue: com.apple.main-threadException Type: EXC_CRASH (SIGILL)Exception Codes: 0x0000000000000000, 0x0000000000000000Application Specific Information:ProductBuildVersion: 7A165tûõ ƒ Thread 0 Crashed:: Dispatch queue: com.apple.main-thread0 libsystem_kernel.dylib 0x00007fff8eb584de mach_msg_trap + 101 libsystem_kernel.dylib 0x00007fff8eb5764f mach_msg + 552 com.apple.CoreFoundation 0x00007fff8bcf7eb4 __CFRunLoopServiceMachPort + 2123 com.apple.CoreFoundation 0x00007fff8

My application uses a group container that shares files between the main application and its helper. The helper is launched by using SMLoginItemSetEnabled. When I switch to xCode 7 and build the project, I get an error :error: Embedded binary's bundle identifier is not prefixed with the parent app's bundle identifier. Embedded Binary Bundle Identifier: X2RD457E37.com.myCompany.myHelper Parent App Bundle Identifier: com.myCompany.myAppSo far, the bundle’s name of the helper started with the the group container ID (X2RD457E37). Did this rule change ? I have found no documentation on the subject.I develop in Objective-C but I notice that with Swift the method SMLoginItemSetEnabled is no longer avalaible. I guess it was replaced. But by what?Thanks for any help.

Hi all!.Beta 3 Public.I have a problem with Mail.When i start it, and i try to send an email, the loop seems to be this:Send button:Try to send the email.The pop up of the email dissapear.The pop up of the email appearThe pop up of the email dissapear.The pop up of the email appearThe pop up of the email dissapear.The pop up of the email appearThe pop up of the email dissapear.The pop up of the email appearindefinitely.........The only way that can i send the email is, with this window opening and closing,,, try to enter to preference and put the password of the SMTP again....If i do it, Like a Spartan fighting with the pop up of the email, this can be sended and the pop up loop stops....How can i fix this?.RegardsP.D:Here have all the console menssages antil send correctly the email:30/7/15 9:57:23,668 a.m. Spotlight[248]: XPC connection was invalidated30/7/15 9:57:23,732 a.m. Spotlight[248]: XPC connection was invalidated30/7/15 9:57:23,931 a.m. Spotlight[248]: XPC connection was invalidated30/7/15 9:57:24,

My question is fairly straight forward - can iOS create a Wi-Fi Direct group that can be joined by non-iOS devices?The only information I can find relating to iOS direct peer connectivity is https://developer.apple.com/library/prerelease/ios/documentation/MultipeerConnectivity/Reference/MultipeerConnectivityFramework/index.htmlMore specifically, The Multipeer Connectivity framework provides support for discovering services provided by nearby iOS devices...Based on this I would say no, but technically speaking, there should be no limitation for Wi-Fi Direct as it is an open standard, and apps like AirDrop already use it.

Opening a new playground with Xcode 7 b4 and adding a single line like print(hello) results in a EXC_BAD_ACCESS error.Console.app shows the following:7/30/15 1:07:27.000 PM kernel[0]: Sandbox: MyPlayground2(75453) deny file-read-data /Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 8.4.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/UIKit.framework 7/30/15 1:07:27.146 PM com.apple.dt.Xcode.Playground[75242]: IDEPlaygroundExecutionSessionThread(pid=75453) IDEPlaygroundExecution: * thread #1: tid = 0xd320cf, 0x0000000107c9a962 libicucore.A.dylib`utext_clone + 22, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x8) * frame #0: 0x0000000107c9a962 libicucore.A.dylib`utext_clone + 22 frame #1: 0x0000000107dd3c12 libicucore.A.dylib`icu::RegexMatcher::reset(UText*) + 54 frame #2: 0x0000000107e0e3e4 libicucore.A.dylib`uregex_setText + 222 frame #3: 0x000000010577b765 Foundation`-[NSRegularExpression(NSMatching) enumerateMatchesInString:options:range:usingBlock:

I have read in the Apple developer forum that unlike watchOS 1, watchOS 2 does not share its keychain with the phone app so bam!! keychain sharing is not enabled by default we got to do a workaround for that.Ok coming to my issue, I was trying to run a very basic keychain access program on the actual watch device running the latest beta (beta4) let storableString:NSString = keychain in watchos is working with simple code let query : [NSString : AnyObject] = [ kSecClass : kSecClassGenericPassword, kSecAttrService : WatchService, kSecAttrLabel : KeychainData, kSecAttrAccount : SecureData, kSecValueData : storableString.dataUsingEncoding(NSUTF8StringEncoding)! ] let result = SecItemAdd(query, nil) print(result)On the simulator it works like a charm but when I try to run the same on the actual watch it gives me an status code of -34018There was no public documentation about this error code but I did a little digging to find out it turned out to be errSecMissingEntitlement = -34018, / Internal error when a require