A Summary of the WWDC25 Group Lab

Interesting observation—Serif Labs (a team of just 7) has a custom background for Affinity Designer, but the relatively new Affinity Photo, which apparently is just as significant, still makes do with a standard background. I've wondered if it has something to do with winning an award or something, or maybe you get that opportunity after a certain amount of time. Or maybe there used to be a way to do it, but it's since been removed and existing apps are grandfathered in? I really don't know.

It works for me (beta 4). The issue I got on the device, but not on simulator, was related to the place you save the file. I discovered that if you I want to save on Documents folder then on simulator everything works like a charm, but on the Apple Watch the recording doesn't work (no audio animation and I have error when saving). The solution I got was to use instead of Documents folder a group folder, this seemed to solve the issue: now I am capable of recording and playing the audio files. However, I discovered something else: the recording is not continious but it has gaps. I tried to record myself while I was counting from 1 to 20 and in the recorded file it was a gap between 7 and 18. Not sure how to handle this.

Starting two days ago, setHidden no longer seems to have any affect on groups. Have filed a bug report.

Disabling SIP was a diagnostic. Now that you've ruled out a SIP/display driver conflict, you'll need to explore other possible causes. It would be better to switch SIP back on as it is not the culprit.I'm assuming you're referring to the Air's own screen and not an external one you have attached...From your description of the glitches my guess is that this is caused by software you installed when you were on Yosemite trying to launch a window but being unable to display. Try removing everything from your login items (System Preferences > Users & Groups > use the - button to remove them from the list).Then restart your Mac with Reopen windows when logging back in un-selected)

Today, i start up the mac.... after an hour i tryed to send an email and the problems comes again:Data (Yesterday i do NVRAM / SMC Reset)I checked and in the preferences the checkbox Allow insecure authentication isnt checked... is like that the preference didnt save this... but all the day works after i check it... the problems comes tomorrow ( ? )... ---------------2/8/15 10:20:19,114 a.m. secd[310]: secTaskDiagnoseEntitlements MISSING keychain entitlements: raw entitlement values: <CFBasicHash 0x7fbe0b720ac0 [0x7fff7610fee0]>{type = mutable dict, count = 0,entries =>}2/8/15 10:20:19,114 a.m. secd[310]: secTaskDiagnoseEntitlements MISSING keychain entitlements: original ag: (null)2/8/15 10:20:19,114 a.m. secd[310]: secTaskDiagnoseEntitlements MISSING keychain entitlements: newly parsed ag: (null)2/8/15 10:20:19,114 a.m. secd[310]: __security_simulatecrash Simulating crash, reason: keychain entitlement(s) missing, code=53c000072/8/15 10:20:19,114 a.m. secd[310]: __security_simulatecrash_link Simulat

I've tried using Library directory, caches directory, documents directory.. still doesn't work.. beta 4.The solution I got was to use instead of Documents folder a group folder,.What's a group folder? I thought app groups no longer worked in watchOS 2.0?

I've run into the same issue. It's unfortunate that Keychain Sharing via access groups is no longer supported between an iPhone app and it's accompanying Watch 2 app. I'll have to devise an alternate solution outside of this mechanism.

Today Again with the problem. :3/8/15 11:13:46,638 a.m. secd[310]: secTaskDiagnoseEntitlements MISSING keychain entitlements: raw entitlement values: <CFBasicHash 0x7fbe0b43f2e0 [0x7fff7610fee0]>{type = mutable dict, count = 0,entries =>}3/8/15 11:13:46,638 a.m. secd[310]: secTaskDiagnoseEntitlements MISSING keychain entitlements: original ag: (null)3/8/15 11:13:46,638 a.m. secd[310]: secTaskDiagnoseEntitlements MISSING keychain entitlements: newly parsed ag: (null)3/8/15 11:13:46,638 a.m. secd[310]: __security_simulatecrash Simulating crash, reason: keychain entitlement(s) missing, code=53c000073/8/15 11:13:46,638 a.m. secd[310]: __security_simulatecrash_link SimulateCrash not available3/8/15 11:13:46,639 a.m. secd[310]: securityd_xpc_dictionary_handler com.apple.Addres[425] copy_matching Error Domain=NSOSStatusErrorDomain Code=-34018 client has neither application-identifier nor keychain-access-groups entitlements UserInfo={NSDescription=client has neither application-identifier nor keycha

Good Day,I installed Version 3 of El Capitan Beta, and now i can't open Mail. It crashes after opening the application. Could anyone help me solve this problem.These are the logs I am getting...Process: Mail [1498]Path: /Applications/Mail.app/Contents/MacOS/MailIdentifier: com.apple.mailVersion: 9.0 (3073)Build Info: Mail-3073000000000000~1Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: Mail [1498]User ID: 501Date/Time: 2015-08-03 09:49:30.062 -0600OS Version: Mac OS X 10.11 (15A234d)Report Version: 11Anonymous UUID: D703EE4A-4267-FA27-620B-4F3C6D3B6A26Time Awake Since Boot: 2200 secondsCrashed Thread: 1 -[LibraryImportAssistant synchronouslyDoTheImport] Dispatch queue: NSOperationQueue 0x7fbc82499770 :: NSOperation 0x7fbc82499cf0 (QOS: UTILITY)Exception Type: EXC_CRASH (SIGABRT)Exception Codes: 0x0000000000000000, 0x0000000000000000Exception Note: EXC_CORPSE_NOTIFYApplication Specific Information:*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '<MFSq

Good Day,I installed Version 3 of El Capitan Beta, and now i can't open Mail. It crashes after opening the application. Could anyone help me solve this problem.These are the logs I am getting...Process: Mail [1498]Path: /Applications/Mail.app/Contents/MacOS/MailIdentifier: com.apple.mailVersion: 9.0 (3073)Build Info: Mail-3073000000000000~1Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: Mail [1498]User ID: 501Date/Time: 2015-08-03 09:49:30.062 -0600OS Version: Mac OS X 10.11 (15A234d)Report Version: 11Anonymous UUID: D703EE4A-4267-FA27-620B-4F3C6D3B6A26Time Awake Since Boot: 2200 secondsCrashed Thread: 1 -[LibraryImportAssistant synchronouslyDoTheImport] Dispatch queue: NSOperationQueue 0x7fbc82499770 :: NSOperation 0x7fbc82499cf0 (QOS: UTILITY)Exception Type: EXC_CRASH (SIGABRT)Exception Codes: 0x0000000000000000, 0x0000000000000000Exception Note: EXC_CORPSE_NOTIFYApplication Specific Information:*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '<MFSq

Max,Tried all the steps you described and still crashes... is there anything else i could do ? Here is the Log.Process: Mail [574]Path: /Applications/Mail.app/Contents/MacOS/MailIdentifier: com.apple.mailVersion: 9.0 (3073)Build Info: Mail-3073000000000000~1Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: Mail [574]User ID: 501Date/Time: 2015-08-03 12:18:43.745 -0600OS Version: Mac OS X 10.11 (15A234d)Report Version: 11Anonymous UUID: D703EE4A-4267-FA27-620B-4F3C6D3B6A26Time Awake Since Boot: 480 secondsCrashed Thread: 7 -[LibraryImportAssistant synchronouslyDoTheImport] Dispatch queue: NSOperationQueue 0x7ff89d89e4e0 :: NSOperation 0x7ff89d89ea00 (QOS: UTILITY)Exception Type: EXC_CRASH (SIGABRT)Exception Codes: 0x0000000000000000, 0x0000000000000000Exception Note: EXC_CORPSE_NOTIFYApplication Specific Information:*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '<MFSqliteHandle: 0x7ff89bdce840> attempting to dealloc with active db'abort() calledterm

It feels painful because you're struggling to make Swift do things it just doesn't do, at least not at the moment. You can't make arrays of Hashables be Hashable, or optional versions of Hashables be Hashable.You can manually patch in support for specific cases, as you've done, but it's going to be high-maintenance and is never going to be a correct and general solution. Why stop at two layers of optionality and/or sequencing? What if someone has a three-layer structure they need to hash?I think this is probably a good context for a YAGNI approach. Just fill out the basic system, and if you really need individual extensions for your own code, you can put them in ad hoc as you come across those cases. If the API is for an external client, just supply the basics and perhaps an extension system that lets them roll their own Frankenstein hashing routines.There's no reason to give these functions different names. Just call them all the same thing and let Swift sort out the priority.Some may disagree, but I don't l