“smb big sur”

IAiSeed, it looks like your response was AI generated. If that’s the case, it’d be good to let folks know that, so that they can decide for themselves how much trust to put it in. Coming back to the technical issue, this isn’t right: [quote='877778022, IAiSeed, /thread/817236?answerId=877778022#877778022, /profile/IAiSeed'] Functions like class_getInstanceMethod and IMP are used to dynamically invoke Objective-C methods from C. [/quote] A minor issue is that IMP isn’t a function, it’s a type. A more significant issues is that this approach, known as IMP caching, is not the right option in most cases. Rather, if you want to call Objective-C directly from C it’s better to call the objc_msgSend function (or one of its variants; more on that below). When you call Objective-C in this way, it’s critical that you cast the objc_msgSend function pointer to a function pointer with the right arguments. For example, to call -[NSUUID getUUIDBytes:] you’d do this cast: typedef void (*NSUUID_getUUIDBytes_Ptr)(NSUUID *, SEL,

I selected Opus and Sonnet. Is Sonnet 'better' for coding? Maybe leaving it at Default is best. It seems logging into Anthropic requires a paid account. Using a 'free' API lets you use the models for free, for now? Codex with a 'pay as you go' account is very capable but I'd like to use Claude going forward. I'm more of a hobby coder at this point and the Pro account is 'big' step up. ;-) maybe I should start charging for my apps. Hopefully I'll get a good feel for Claude in it's current configuration and can accept the value added of the paid account. [Just one more subscription]

Use this command: mount -t my_ngpc ngpc://login ~/my_ngpc Interesting. The part that makes this strange is that having the volume appear in the sidebar is actually the default behavior, which you normally DISABLE by passing the nobrowse option into mount. A few things: Please file a bug on this and post the bug number back here. Even if the behavior is expected, at a minimum it would probably be worth better documenting. I'd also appreciate you filing a separate bug asking for a high-level (it would probably end up in DiskArb) mount API that supports FSKit. The underlying issue here is that the lack of a high-level API means that you're not properly integrated into the system full volume architecture, which means the system isn't necessarily designed to pick up your mount. This is something we're obviously already aware of, but developer bugs help us prioritize work. What does the mount entry for your volume show when run mount to list all current mounts? This will between the kernel mark the volume nobrowse

Has been exactly 1 month today for Waiting for Review. sent emails. update check and no feedback from apple. other stores are able to review the app within a day. unacceptavble.. Is this only for independent devs or even big corps are having this issue?

[quote='877556022, mbisque, /thread/816956?answerId=877556022#877556022, /profile/mbisque'] I am unable to revoke existing Developer ID Installer Certificates. [/quote] Right. Revoking a Developer ID certificate is a big deal because its stops existing products from running. You should only do that if the key is compromised. Quoting The Care and Feeding of Developer ID If you believe that your private key has been compromised, follow the instructions in the Compromised Certificates section of Developer > Support > Certificates. I don’t believe that’s the case here. So you have two choices. The one I recommend is that you manually recover the private key associated with one or more of your Developer ID certificates, which will give you a signing identity that you can use to sign your software. The Care and Feeding of Developer ID explains various strategies for this. And once you do that, intentionally back up the signing identity so that you don’t run into this problem again in the future. The

This isn’t the first time I’ve seen reports of this. See this thread. Unfortunately something I failed to drive that thread to a conclusion )-: so I’m going to use your thread to continue the issue. In that thread I suggested that the developer tweak their filter to return .allow(), purely as a diagnostic test to see whether the problem is fundamental to content filters or something specific to the filter working on the SMB stream. They indicated that it’s the latter. Do you concur? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

First up, on the bug side, what would be most useful now would be to capture a sysdiagnose after the crash, then upload that log to the bug. A few notes on that: The log doesn't need to be collected all that soon after the bug. I try to collect within a few minutes of the crash, but there really isn't any difference triggering within the next 15+ minutes. Eventually, we start purging log data (losing data), but I've gotten useful data out of logs that were taken hours after the event. It IS important that you not reboot the machine first. Lots of data is purged during that process, to the point where I've basically found those logs useless. PLEASE include information about WHEN the problem occurred. Even better, upload the crash log from the same crash you want to use to look at in the sysdiagnose. The log volume is so high that trying to figure out what happened without a time reference can be extremely slow and time-consuming. Similarly, the crash log should be included in the sysdiagnose, but there are cas

[quote='816782021, alexfromapex, /thread/816782, /profile/alexfromapex'] Has anyone gotten Postgres to run in a sandboxed app? [/quote] Not personally, but I can shed some light on the App Sandbox side of this. System V IPC is a compatibility API an macOS. We recommend against using it in new code. Given that, it shouldn’t come as a big surprise that it doesn’t have a good story regarding the App Sandbox. The alternative, Posix IPC, works in the App Sandbox as long as you conform to the naming guidelines described in App Groups Entitlement [1]. So, to make this work you’ll need to: Sign your executables to claim access to an app group. Configure the library to use Posix IPC. With a name that’s authorised by that app group. I don’t have any expertise with this specific third-party library, so I’ve no insight into the last two. I’m happy to help with the first. I have lots of background on that in App Groups: macOS vs iOS: Working Towards Harmony. Share and Enjoy — Quinn “The Eskimo!” @ Developer Techn

It is a bit non-standard not being deployed as a System-Extension, but rather as a global daemon. This is actually pretty common. So, let me start here: My guess is, some ES_AUTH events (with deadline) arrive when Mac goes to sleep, and somehow my high-priority dispatch_queue handling them is put to sleep mid-processing them, so when the Mac wakes up - event handling continues long after the deadline passed, and MacOS decides to kick the process. No, I don't think that's what's going on, at least not in the basic case. The system that feeds events into your ES client as a kernel extension feeding events into user space and it will have kept your ES client active long enough that we cleared all syscall activity through your client before we allowed the system to sleep. There are lots of places where things can go wrong, but I don't think the core event delivery system is the issue. That leads back to here: Hi, I develop an ES client applying rule-engine evaluating ES events (mostly File-system events). What do

Waiting for 3 weeks now for my app to be approved. No sign of them despite 3 support emails and one expedite review. This version introduces inn app purchases. I provided detailed instructions on how to get everything with 0 effect. I can see in the analytics that some bots (or humans, I don't know) launch the app once in a while but do not navigate in the menus, do not test anything. It is very frustrating and disrespectful for the work I put in this app. I don't know what to say. We pay money for the subscription, big money for their gear and we're treated like this.

I’m interested in developing (or interfacing with) an accessory that transmits video over USB using the UVC standard, and I’d like to better understand how this works within the MFi (Made for iPhone) program. This is actually pretty easy to answer, as the answer is it doesn't. That is, the MFi program simply doesn't have anything to do with this. Let me start by explaining what's going on here: From what I understand, USB-C iPads appear to offer more direct support for standard UVC devices. So, there are actually two iPad-specific options here: iPadOS support DriverKit, which, at a purely technical level, means it's possible to create an iPadOS app that directly communicates with any USB device. iPadOS also includes a class-compliant driver for UVC (USB Video Class) devices. For more information on that, see Support external cameras in your iPadOS app from WWDC2023. To some extent, #2 exists to minimize unnecessary disruption from #1. That is, it was (and is) always going to be possible to make a camera work