“eskimo”

I don’t think there’s anything fundamental blocking an MDM system from doing what you want it to do. When the Mac checks in with MDM, the MDM system knows the identity of that Mac and can send it a configuration profile with a unique com.apple.security.root payload [1]. But there are some obvious challenges: Getting an MDM system that actually supports this. Securely passing the certificate from the Mac to the MDM system [2]. It’s hard to offer advice on that front because this isn’t a standard MDM feature, and thus the answer is going to depend on the MDM server you’re using. The one thing I can rule out is a client-side solution. There’s no longer any supported way for code running on the Mac to install a trusted root without user approval. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Or do the same thing with declarative device management, which is the new hotness. [2] Certificates are just fancy public keys, and

[quote='820277021, Great_Om, /thread/820277, /profile/Great_Om'] Since it was not possible using the UserDefaults class [/quote] What’s not possible? Reading a user default from a specific domain, like com.apple.Finder? You are correct that UserDefaults can’t do that, but running the defaults tool is not the best alternative. Rather, use CFPreferences. For example: import Foundation func main() { guard let obj = CFPreferencesCopyAppValue(ShowHardDrivesOnDesktop as NSString, com.apple.Finder as NSString), CFGetTypeID(obj) == CFBooleanGetTypeID(), let showHardDrivesOnDesktop = obj as? Bool else { fatalError() } print(showHardDrivesOnDesktop) } main() WARNING Unless otherwise documented, system preferences like this are an implementation detail. It might be OK to use them in a limited scope — like in a managed environment where you control all the copies of the code — but you should not rely on implementation details in a product that you deploy widely. The code above won’t work if your app is sandboxed. Then ag

You are definitely breaking new ground here, so I’m gonna to do some research and get back to you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Error code 69 is EX_UNAVAILABLE, which isn’t something I’d expect from notarytool. Are you sure you’re not hitting an xcrun problem? What does this report: % xcrun -f notarytool /Applications/Xcode.app/Contents/Developer/usr/bin/notarytool Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='881252022, alexfs123, /thread/819160?answerId=881252022#881252022, /profile/alexfs123'] I got a couple of kernel panics while developing a new plugin. [/quote] Kernel panics are always bugworthy. See Bug Reporting: How and Why? for my advice on how to file effective bug reports. And please post your bug number, just for the record. Honestly, I’d be surprised if these kernel panics were caused by FSKit. My experience is that kernel panics are usually caused by other subsystems within the kernel. However, the only way to know for sure is to get a bug on file. As to the behaviour of PassthroughFileSystem, keep in mind that it’s sample code, not a production file system. If you encounter weird problems, it’s worth investigating whether those issues are caused by FSKit or by the sample. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='881081022, wu_aaron, /thread/818708?answerId=881081022#881081022, /profile/wu_aaron'] We have successfully connected an iOS device with a non-iOS device via Wi-Fi Aware [/quote] Nice! I know lots of folks have struggled to get that working, so I’m glad to hear of a success story. [quote='881081022, wu_aaron, /thread/818708?answerId=881081022#881081022, /profile/wu_aaron'] we still have a throughput issue … sends an HTTP request over an already-established TCP connection [/quote] So, just to be clear, are you using URLSession for this? Or have you implemented your own HTTP protocol on top of Network framework? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='881114022, craigc123, /thread/819926?answerId=881114022#881114022, /profile/craigc123'] do you have any recommendations of things that might work here? [/quote] No, sorry. I try to avoid speculating in general, and especially so in cases like this. [quote='881114022, craigc123, /thread/819926?answerId=881114022#881114022, /profile/craigc123'] tried using the Multipeer Connectivity API [/quote] Multipeer Connectivity won’t help. It uses the same peer-to-peer Wi-Fi infrastructure as Network framework. Oh, and it’s best avoided anyway [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] One day I’ll succeed in my efforts to get that API officially deprecated, and I’ll sing a happy song while I update the advice in TN3151 and Moving from Multipeer Connectivity to Network Framework (-:

[quote='881073022, chkpnt, /thread/748447?answerId=881073022#881073022, /profile/chkpnt'] Is this a bug or intentional? [/quote] I’d call it a bug, by my opinion doesn’t matter (-: If this is causing your product significant grief then it’s worth filing a bug about, even if it’s intentional. [quote='881095022, chkpnt, /thread/748447?answerId=881095022#881095022, /profile/chkpnt'] I've filed FB22313288. [/quote] Thanks. It’s been marked as a duplicate of a bug that was filed internally, one that’s definitely with the right folks. I don’t have any info to share beyond that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m still not entirely sure what stage you’re at here. You started this thread talking about manually checking requirements, which is not what I recommend when dealing with XPC. Rather, you should apply the requirement directly to the XPC connection, as explained in this forums post. With that in mind, it’s a question of crafting the right requirement. There are two parts to this: Identifying your clients Identifying your code loaded into system clients Identifying your clients should be straightforward. You start with the DR of those clients and then adjust the Boolean logic to suit your specific needs. It’s not possible to identify your code loaded into system clients, so the best you can do is identify those systems clients themselves. And there’s no good way to do that: You could use the client’s designated requirement (DR), but that might break if the system changes the context in which it loads your authorisation plug-ins (as has happened in the past). You could use a much broader requirement, like anch

[quote='881100022, nathan-pierce-veertu, /thread/819456?answerId=881100022#881100022, /profile/nathan-pierce-veertu'] FB22313446 [/quote] Thanks. I’ve been discussing this with the Virtualization team and I think I know what’s going on here. But, just to confirm, on a Mac that’s showing this problem, what does this command report: % pkgutil --pkg-info-plist com.apple.pkg.MobileDevice … … pkg-version 4.0.0.0.1.1772003596 … Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

So, the standard term for this is network interfaces. macOS supports a wide array of network interfaces. I have lots of background to this in the various posts referenced by Extra-ordinary Networking. [quote='820120021, happyanimal55, /thread/820120, /profile/happyanimal55'] I'd like to permanently delete them [/quote] Don’t attempt to do that. Some of these interfaces are used for stuff that’s vital to the internal operation of macOS, for example, communication between the main CPU and various co-processors. My general advice is that you adjust your workflows so that these don’t get in the way. If you’re writing code, the suggestions in Extra-ordinary Networking should help. If not, I’ve found this command to be super helpful: % networksetup -listallhardwareports … Hardware Port: Wi-Fi Device: en0 Ethernet Address: … … It gives you the BSD name of each user-visible interface, which you can then use with commands like ifconfig. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ App

[quote='820155021, alex_strong, /thread/820155, /profile/alex_strong'] I've had issues getting the dmg signed by the Apple notary service [/quote] That text suggests that you’ve misunderstood how notary works. The notary service doesn’t sign your product. Rather, you present it with a distribution-ready product, one that’s already signed, and the notary service checks it and, if all is well, issues a signed ticket. See Notarisation Fundamentals for more about how this process works. As to why the notary service is refusing to notarise your product, it’s hard to say without more info. It sounds like you were able to submit the product and get a response, but the status is Invalid, indicating a problem with your submission. In that case the next step is to look at the notary log. What does it say? See Fetching the Notary Log for info on how to get the log. [quote='820155021, alex_strong, /thread/820155, /profile/alex_strong'] The only big change we made this time was switching to Maven [/quote] Ah, Java. Notari

[quote='820080021, nixx, /thread/820080, /profile/nixx'] I have submitted this via Feedback Assistant (FB22312299). [/quote] Thanks. I’m not sure what’s going on here, but it’s clearly a regression and thus warrants a bug report. Having said that, there’s a long-standing gotcha you need took out for. Using non-ASCII names for pure data should be fine, but you have to be careful when using non-ASCII names for files within a code-signed bundle. There’s a long-standing problem with that, as explained in this post. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I want to be clear about terminology here: A load-time import is one that’s statically declared in the binary via the LC_LOAD_DYLIB load command. A run-time import is one that you do from code, using dlopen or some API layered on top of that. Beyond that, I’m going to use the terms from an An Apple Library Primer, and you should read before continuing. [quote='820251021, vd02, /thread/820251, /profile/vd02'] What is the recommended approach on macOS for this kind of explicit dynamic loading … ? [/quote] My recommendation is that you not do this. Apple platforms generally prefer load-time imports because it enables optimisations in the dynamic linker. Specifically, the dynamic linker can build and cache a closure for an app, reusing that closure the next time the app launches. Note We discussed this in detail in WWDC 2017 Session 413 App Startup Time: Past, Present, and Future. Sadly, it’s no longer available from Apple, but the core info is still available from third-party sources. I don’t think this closure

I’m sorry but I don’t understand the question here. Are you asking for someone to provide the code that ‘answers’ that experiment? Or asking about how you actually experience with this within the Swift Playground app? Please elaborate. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com