“eskimo”

Are folks still having this problem? I just tried it myself and everything worked for me, so either this was a transient thing that’s now fixed or it’s caused by an environmental thing that doesn’t apply in my case. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. We implemented your own HTTP protocol on top of NetworkConnection. OK, cool, that’s kinda what I expected but I’m glad you confirmed it. We are very eager to send HTTP requests over Wi‑Fi Aware using URLSession — is this achievable? No. I recommend that you file an enhancement request for that. Please post your bug number, just for the record. Coming back to your throughput issue, I don’t have an immediate answer to that. I’m gonna do some digging and get back to you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='881307022, nixx, /thread/820080?answerId=881307022#881307022, /profile/nixx'] staging the package contents in an HFS volume … allows pkgbuild to succeed [/quote] I’m glad that worked but… sheesh… it’s a bit of a worry. Hopefully we’ll get a fix to FB22312299 sooner rather than later. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='881470022, GangOrca, /thread/820251?answerId=881470022#881470022, /profile/GangOrca'] dlopen and dlsym are Linux-specific C APIs [/quote] No. These are Posix APIs that are supported on most Unix-y platforms, including macOS [1]. [quote='881470022, GangOrca, /thread/820251?answerId=881470022#881470022, /profile/GangOrca'] How are they invoked in Swift directly? [/quote] Like you would any other low-level C API: import Darwin func main() { guard let dl = dlopen(/usr/lib/libSystem.B.dylib, RTLD_LAZY) else { … handle error … } … use `dl` … } main() Note that Darwin is implicitly imported by Foundation, so most Mac programs won’t need to import it explicitly. [quote='881470022, GangOrca, /thread/820251?answerId=881470022#881470022, /profile/GangOrca'] I couldn't find any swift documentation about these symbols. [/quote] Indeed. Most low-level C APIs are documented in our man pages. I’ve got a post about that somewhere… ah, OK, here we go… Availability of Low-Level APIs. Share and Enjoy — Quinn “The Eskimo

[quote='881369022, marrgd, /thread/820088?answerId=881369022#881369022, /profile/marrgd'] I lost the knowledge, how to open the pdf book on Swift Playground to experiment inside Swift Playground. [/quote] Right. This is what were were discussing on your other thread. There’s no direct fix, but you can work around it by creating your own playground and copying chunks of code from the tutorial to that playground. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

OK, here’s a summary, sorted by version: Version | User ------- | ---- 4.0.0.0.1.1762585687 | kthchew 4.0.0.0.1.1762585687 | nathan-pierce-veertu 4.0.0.0.1.1772003596 | eskimo As you can see, I’m on the latest. And this is indeed the version of the MobileDevice package inside Xcode 26.4 [1]. Consider: % plutil -extract CFBundleShortVersionString raw /Applications/Xcode.app/Contents/Info.plist 26.4 % xar -xf /Applications/Xcode.app/Contents/Resources/Packages/MobileDevice.pkg % cat PackageInfo … Earlier I wrote: [quote='880808022, DTS Engineer, /thread/819456?answerId=880808022#880808022'] When I wrote the above I hadn’t yet installed Xcode 26.4rc. So I installed that and repeated the test. [/quote] I don’t think that had an effect because I’d installed an earlier release of the Xcode 26.4 beta, one that had the same MobileDevice installer version. So I was on the latest MobileDevice prior to running my test, and updating to Xcode 26.4rc didn’t change that. So my understanding of how this should wo

[quote='881346022, alex_strong, /thread/820155?answerId=881346022#881346022, /profile/alex_strong'] I tried to put this in a comment [/quote] It’s better to reply as a reply, rather than as a comment; see Quinn’s Top Ten DevForums Tips for this and other titbits. [quote='881346022, alex_strong, /thread/820155?answerId=881346022#881346022, /profile/alex_strong'] Fetching the Notary Log was exactly what I was looking for. [/quote] Yay! [quote='881346022, alex_strong, /thread/820155?answerId=881346022#881346022, /profile/alex_strong'] Any idea how to request signed artifacts from Maven? [/quote] No, sorry, I don’t have any experience with Java build systems (just their output :-). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='820395021, matthewruzzi, /thread/820395, /profile/matthewruzzi'] FB22328001 [/quote] Thanks for that. [quote='820395021, matthewruzzi, /thread/820395, /profile/matthewruzzi'] have a GitHub issues style edit history. [/quote] Yeah, that’s the challenge. Supporting indefinite edits without this edit history is worrisome IMO, and the forums platform does not currently support anything like this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

matthewruzzi wrote: Report a bug Exactly! See Bug Reporting: How and Why? for lots of hints and tips about filing effective bug reports. Also, if you do file a bug, please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='820314021, Ludovic, /thread/820314, /profile/Ludovic'] As far as I understand for preboot I need to provide a persistent token [/quote] No, you’ve got that backwards. CryptoTokenKit supports two different types of token: Smart card tokens Persistent tokens A smart card token is backed by hardware; a persistent token may be entirely virtual. A smart card token subclasses TKSmartCardToken. A persistent token subclasses TKToken directly. Because a smart card token is backed by hardware, it can work at login time. In a persistent token, the information about the credentials in the token is stored in the user’s home directory, and thus it can’t be used to log in. It’s a chicken’n’egg problem. My understanding is that you have a smart card token working for general login, and now you’re trying to get that work for FileVault unlock. There’s no way to make that work. It’s another chicken’n’egg problem. Your app is stored on the encrypted volume, so it can’t be accessed until the user has unlocked that. This w

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