A Summary of the WWDC25 Group Lab

Depending on your settings, updates can occur overnight automatically. Anyway, another diagnostic is to test the behaviour of the SysPref lock in a temporary new account. I.e. create a temporary new admin account from System Preferences > Users & Groups > Open Padlock > + button, log into the new account and test...

I have deactivated automatic updates in my settings, so the system does not update without me being aware of it.I would love to create a new admin account, but for that I would need to be able to open that padlock in Users and Groups and if I could do that, then we would not have this conversation in the first place. So, sorry, but I am afraid that I can't do that :-(

Just to add some more color:I'm storing oauth2 creds in the keychain. From a fresh start, the following work:* Accessing an existing credential* Deleting a credential and storing a new one.Where I run into problems is in resuming app after being previously logged in, stepping out to settings, and returning. One feature of the internal build is that the identifier for the service to be used is stored in NSUserDefaults, so the user can go to iOS Settings and toggle their service endpoint. When the app resumes after this happends, I check to see if the service changed, and if it did, I force a logout and ask the user to sign in again.It is at this point I run into problems. After having previously been able to read/write the keychain, I get a -34018 for every keychain access. While the deletes happen almost immediately after the app resumes, the adds typically happen quite a while afterwards, since the user has to enter a name and password.I'm using accessibility specifier kSecAttrAccessibleAfterFirstUnlock. I h

Hi Charu,This question was answered in the WWDC Security Lab Session. The notes for that session that are relavent to your question are as follows:Question: How is the management config for System Integrity Protection updated? Answer:Updates to /System/Library/Sandbox/rootless.conf will likely be coming through Software UpdateQuestion:Which directories and files is System Integrity Protection protecting? Is there a way to get a listing from the command line?Answer:/System/Library/Sandbox/rootless.conf is the SIP conf file, but changes to this conf file are not immediately picked up by SIP. /System/Library/Sandbox/rootless.conf itself is protected by SIP.ls's -O flag (capital O) should show restricted filesls -laO lists files and shows restrictionsQuestion:Is it possible to add custom inclusions and exclusions to System Integrity Protection?Answer:/System/Library/Sandbox/rootless.conf is Apple's, it should not altered by third-parties.Asterix-marked ( * ) listings in /System/Library/Sandbox/rootless.c

The magic here is workspaces (trust me, in Xcode the magic is always workspaces :-).To test this, I did the following in Xcode 6.4:I created a new framework project, “QFramework”, from the OS X > Framework & Library > Cocoa Framework template, selecting Swift as the language.I created a new file, TF.swift, and set its contents to: public class TF { public init() { } public func f1() { println(works) } }IMPORTANT I tweaked your code to add a public initialiser.I created a new app project, “QApp”, from the OS X > Application > Cocoa Application template, also selecting Swift as the language.Note The Swift runtime makes command line tools tricky, so I recommend that you start out with the simple case of an app.I closed both projects.I created a new workspace.I added both projects (the *.xcodeproj files) to the workspace.IMPORTANT When adding, make sure Copy items into destination group’s folder is not checked.In the Link Binaries with Libraries section of the Build Phases tab of the app’

Are you sure that your content fits the page?Try creating a group with Width and Height as Relative to Container = 1 and add all your contents inside it.

Thank you for the suggestion.I tried adding a Group to a page that, currently, only contains one label. I set the Group's Width and Height to Relative to Container = 1, and placed the label in the Group. The Label's Position is Horizontal = Center, Vertical = Top, and its Size is Width = Relative to Container = 1 & Height = Size to Fit Content. The label uses the Body font. Even with all of these settings, the Page still scrolls; both when using the Digital Crown and when scrolling with my finger.

My images were not showing up from my 1.0 app, when I moved all my images from 1x to 2x in the group, they started showing again.Img: http://i.imgur.com/K4SBjBS.gif

Let's assume I have a simple Notes app with two screens--a list view (ListVC) and a single note view (DetailVC). Let's say that the note has a Title and Body properties. Great example.I am assuming exlusive usage of NSUserActivity and no Core Spotlight integration.But we're off on the wrong foot. This is not the way I would recommend doing this. CoreSpotlight is designed to index user content, which your notes content would be considered. So you should be using CoreSpotlight here.1. If my app has user modifiable content, exclusive usage of NSUserActivity, without Core Spotlight is a bad idea.Correct.2. Exlcusive usage of NSUserActivity, only makes sense in an app with read-only, static content.Not necessarily. Your app might present content that is static, but that the user might want to be able to search without having interacted with it. That is, let's say your content presented shared notes which are read-only (e.g. from a shared group of coworkers). Your app should be able to index those shared n

The best way to provide feedback to the Core Audio engineering team is to file a bug report with a good summary of the API feature you are requesting along with as much detail about your specific need for the API. How would your application use an non-interruptible Audio Session for example, why do you need this feature and so on.All bugs are screened and analyzed by real humans of the engineering variety involved with the specific frameworks pertaining to the request in the report(s), so you shouldn't worry that no one will read it or understand or that we simply punt it - now, you may never hear about your feature request again and that's just the way things work in this world unfortunately - but then again, you may see the feature introduced at a future WWDC.We are always looking to improve the audio system APIs and developer feedback is a very important and vital component for us to archive this goal.https://bugreport.apple.com/

I'd add a short change list/summary of all changes to the review notes for the latest build.