Where can I find the contract from before? it's gone

Hi Michael, Thanks for your reply. I did find the post you refer to myself as well a couple of days ago. Actually I wanted to post this link myself, but I did not yet, as I did not get things working. The (extensive) code example the Apple engineer posted looks promising, but in my code I could not get it to work: I did notice that as soon as I set the focusValue, my app goes haywire: my codebase has some NSViewControllerRepresentable's and the update method is called endlessly as soon as the Focusvalue is set. This causes my app to show the spinner and become unresponsive. I suspect it is a bug, but I am not sure. I posted a bug report to Apple, hoping they will ever read and fix it. In the meantime, I keep trying myself and I am hoping someone on this forum might come up with some great solution. While I am at it: I think the demo code is the way to go, but it raised an additional question for me: suppose one has an embedded AppKit outlineView (or whatever) and want to update menu, for example because. that outline view has the focus on some selected items: how to (best) use "focus value" from within appkit?

Fixed in Big Sur.

Update: working in Big Sur beta 9, XCode12.2 beta 2.

Same question here... I have been puzzling on this for many hours. How is this supposed to work Apple? It is nice that you think up new magic stuff, but please add some instructions on how it is supposed to be used, using real-world examples. I watched your WWDC session, but still it is a puzzle. If an apple engineer is reading this: please enlighten us...

@Frameworks Engineer: how? How would you "put a NSTrackingSeparatorToolbarItem in your toolbar" if you are working in swiftUI 2.0 (not creating a toolbar in Appkit, but using the .toolbar modifier in SwiftUI?

Suffering the same problem (still in 12.2 beta 2). It look like some empty, non translucent, view is laid over the area where the attributes should show, making it impossible to see anything. We are literally being kept in the dark. I really wonder how Apple quality control can release software like this. Don't they ever use Core Data themselves? Could it be that Beavis and B*tthead are now running development at Apple, trying to mess things up, just for fun: "let's put a blank view over everything, huh huh, yeah, yeah, huh, huh"? Please file a problem report to get the deaf and mute at Apple to notice "something is wrong".

ACK, same here. First it was one way problem only (not able to access anything on network from my TDK), now -since the beta 6 update- it is I-directional. Since latest I found that automator scripts to connect to a server do not work any more as well. What a mess.

I am asking myself the exact same question. Did you manage to figure this out?

Update: I finally managed to get in touch with Apple. It appears they had forgotten to add the entitlements to my account, despite the confirmation mail. After they added it for the second time, everything was working as expected: I was able to add the entitlement to the provisioning profile in the last step.

I am questioning this as well. In addition: what is the line "shuffleImageView.image = shuffleImage" about? It generates an error. 5 lines of code, 2 errors. Apple: I already know it is too much to ask to document anything, but does anybody check this stuff before spending a 10 second fragment on erroneous code? How in earth can this get passed any quality control?

No progress. Apple is not answering. Anybody else who can point me in the right direction? Thanks.

@Quin: thanks. If I understand well, one should also ask for special permission when still developing on a local machine. I would understand if Apple would want that when publishing (in the App Store), but it is a bit confusing that Apple wants developers to ask special permissions for local development (in the early stages). I would expect one to be able to develop 'without restrictions' as long as nothing is signed for distribution. I can only assume the special permissions are linked to the signing certificate(?).

Updating to Xcode 11.4 resulted in :"Swift package product '{SWIFT PACKAGE}' is linked as a static library by '{APP NAME}' and '{EXTENSION NAME}'. This will result in duplication of library code.". My project contains an application (A) and a helper (H), both sharing some libraries. Some of these libraries are under my control: my own packages (X). Some libraries are however not under my control: github libraries (Y). Xcode needs dynamic libraries to build my project, not the static libraries I had been using until 11.4. If your project resembles mine, the follow may fix the problem: Step 1 - Fix the libraries under my control (X)In the libraries that have a package.swift that is under my control, look up the .library and add type: .dynamic, as described by tadija (see above)Step 2: Fix the github libraries (Y)Fixing external libraries needs a (simple) workaround. Create a fresh framework (Z) for your project. Relocate libraries that are (still) causing problems from A and H to Z.Detailed instructions on how to do this: https://github.com/renaudjenny/Swift-Package-Manager-Static-Dynamic-Xcode-Bug (in particular step 4).Step 3: RelaxRebuild and run!PS: Apple: when are you going to grow up to a responsible IT company, documenting your stuff and proving decent guidance? Instructions to avoid breaking stuff should be provided with release notes. Stop wasting our time to find needles in hackstacks.