show when run

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. Regarding this: it doesn't seem to be an issue with DenyMulticast I don’t think multicast is a factor here, either for good or for ill. iOS has additional restrictions around multicast, but those do not apply on macOS. this command always works for any user When run how? From Terminal? If so, that’s not the evidence that you think it is. Quoting TN3179: macOS automatically allows local network access by: Any daemon started by launchd Any program running as root Command-line tools run from Terminal or over SSH, including any child processes they spawn Based on the info you’ve provided so far, it really does sound you’re bumping into local network privacy issues. This is complicated by the fact that Unix-y programs tend to do things that confuse local network privacy, for example: Common Unix-y techniques, like calling daemon man page, can break responsible code

[quote='871510022, bwill, /thread/810258?answerId=871510022#871510022, /profile/bwill'] the problem is that this behavior appeared without documentation. [/quote] Understood. Unfortunately such is the nature of bugs. If we’d known about the developer impact of this change, we wouldn’t have shipped it. Or, if we had to ship it anyway, we would’ve called it out in the release notes. Usually we’re able to flush out problems like this during the beta seed process, but this case is tricky because it seems to be triggered by the combination of macOS and XProtect changes )-: [quote='871510022, bwill, /thread/810258?answerId=871510022#871510022, /profile/bwill'] If the platform requirement is that the first AppleScript runs on the main thread [/quote] I think you’ve misunderstood my previous posts. I’m not claiming that this is a change in “platform requirement”. IMO this is a bug that we should fix on our side. My suggestion to prime XProtect by running a dummy AppleScript from the main thread is a

When I see questions like this, I like to highlight this quote from the Developer > Swift Student Challenge > Eligibility page: Create an interactive scene in an app playground that can be experienced within three minutes. So, even if the rules didn’t prohibit “sign in”, do you want the judges to waste precious seconds running through that process? Also, keep in mind this one: Submissions will be judged offline. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for the clarification, Quinn. That explains why the hang occurs and why the first AppleScript call needs to run on the main thread. In my case, the problem is that this behavior appeared without documentation. My app legitimately automates Mail and has done so for years. Running AppleScripts from background threads is a normal pattern for this kind of software. Having the first call suddenly require main-thread initialization is a significant behavioral change. There are some practical issues for developers: • The change is not documented. • The hangs are non-deterministic. • There is no API to trigger or control the initialization. • There is no error or diagnostic that would help identify the cause. I understand that AppleScript can be an attack surface and that XProtect integration may be intentional. However, the current approach affects legitimate uses without giving developers a supported way forward. If the platform requirement is that the first AppleScript runs on the

I am developing a macOS virtual audio device using an Audio Server Plug-In (HAL). I want the virtual device to be visible to all applications only when my main app is running, and completely hidden from all apps when the app is closed. The goal is to dynamically control device visibility based on app state without reinstalling the driver. What is the recommended way for the app to notify the HAL plug-in about its running or closed state? Any guidance on best-practice architecture for this scenario would be appreciated. So, full disclaimer, I don't have a lot of direct experience with AudioServer plugins, so the advice I'm giving is coming from a general device management/architecture perspective, NOT from detailed experience with this particular plugin type. In any case, the place I would probably start with here is the sample project Building an Audio Server Plug-in and Driver Extension. You don't need any kind of DEXT for this, but that sample does how to deal with device appearance/disapp

Additional Information: iPhoneSE(Generation unknown - details from client) running iOS 26.0.1: The WebSocket disconnection issue did not occur. Any iPad running iPadOS 26.0.1: I wanted to test this, but I couldn't perform the verification as I didn't have a corresponding device on hand. iPad(A16) running iPadOS 26.2: When accessing directly via the Chrome browser, the WebSocket remained stable and did not disconnect. However, the issue was reproducible when using the PWA version (installed via Chrome). (Does the PWA use the Safari/WebKit engine internally even when installed through Chrome?) Additionally, I found logs corresponding to the time of the occurrence under Settings > Privacy & Security > Analytics & Improvements > Analytics Data. I am attaching those files to this post for reference. ExcUserFault_MobileSafari-2026-01-05-144423.000.ips ExcUserFault_SafariViewService-2026-01-05-144250.ips ExcUserFault_MobileSafari-2026-01-05-143829.ips ExcUserFault_SafariVi

So, looking at things from our side, I'm not sure. I found one bug on this (r.166518515) about accessing a custom directory (/Library//), but the analysis of the engineering team is that it isn't a bug in macOS 26.2... because it shouldn't work in macOS 26.0 EITHER. More specifically, it should only be accessing one of these documented directories: 2. Writing of files: pursuant to normal UNIX file permissions, filters and backends can read/write files to the cache directory specified by the CUPS_CACHEDIR environment variable, to the state directory specified by the CUPS_STATEDIR environment variable, to the temporary directory specified by the TMPDIR environment variable, and under the /private/var/db, /private/var/folders, /private/var/lib, /private/var/mysql, /private/var/run, /private/var/spool (except /private/var/spool/cups), /Library/Application Support, /Library/Caches, /Library/Logs, /Library/Preferences, /Library/WebServer, and /Users/Shared directories. FYI, that does suggest a possible wo

Thanks for the detailed information and diagnostic steps. This makes me believe you have debugged your end adequately, and we are not running into an invalid image, or something simple as that. It might be more suitable to file a Feedback Report than a DTS ticket, so the Notifications team can take a look as to why the store might be becoming inaccessible. The question that comes to my mind is whether this happens when the device is locked and the system Notifications setting is set to not show previews (Settings -> Notifications -> Show Previews) when the device is locked. If that is not set to Always could you try with setting it to Always. I don't really believe this could be the case as you mention the app being active, but it's an easy test to see if that setting has any effect on the issue. Regardless, this would best be handled as a bug report with diagnostic logs. Here are the steps to obtain logs. First , please go to https://developer.apple.com/bug-reporting/profiles

I think I just filled out this form: https://developer.apple.com/contact/request/migrate-individual-account And then they had emailed me in a couple of days. And that began a long series of back and forths where I often had to fill out additional forms with the exact same information. And then I waited for like 3 additional weeks until I was approved. And yet, my app still shows up under my individual name so I dunno.

You'd need to generate a set of Path instances from the characters in your text. This is only really suitable for small amounts, e.g. the Welcome animation or clock digits, etc., because it's not the most performant thing. Also, bigger text is better. Lastly, remember to wrap it all in a GlassEffectContainer to avoid each character's glass being rendered in a discrete pass. Actually lastly: you'll need to adjust the location of the text using .offset(x:y:) or by tweaking the path creation to include better offset translations. This is my quick & dirty attempt. Since .glassEffect() is designed similarly to a fill API, you need something non-empty to 'fill' with your text. Color.clear gets elided by the rendering engine, but what I've found is that Color.white.opacity(0) works to cause an actual (invisible) view to render and take up space during layout calculations. And now: the code! This was written for tvOS, so it uses BIG fonts and offsets to write big numbers. I had it draw a counter that increments e

We are seeing this behaviour even with mounted disk images. We will test with AFP server also. We are not seeing this behaviour when we copy using cp or mv terminal commands or any other application. It’s certainly due to some changes in DesktopServicesHelper on macOS Tahoe which triggers file deletion if it takes more than 5 seconds to transfer. We have tried with less than 5 seconds like 4.5 sec or 4.9 seconds and it works as expected. Interesting. I spent some time looking at our code today and, while I wasn't able to find the specific change, there were a number of operation timeouts added to the copy architecture as part of resolving a number of hangs and other issues. None of them exactly match what you're describing, but the Finder's copy implementation is sufficiently complex that it's likely that I simply missed something. A few different comments: I should have asked this earlier, but what's the auth event you’re actually blocking and are you sure it's something you SHOULD be blocking? Notably, I su

I have the inverse problem. Large title shows fine, but when the user scrolls the content up, the inline title is hidden by a NavigationBarPlatterContainer.

I see the community bringing this up from time to time, and so would like to take this chance to hopefully get it sorted. For the clarify of the discussion, I'd split this question into three parts: Does App Review guideline allow a keyboard extension to launch its container app? If yes, is there any API to do so? Is there any API for the container app to bring the host app back to the foreground? The first part is about App Review policy, and so only the App Review team has the final answer, but looking into the App Review Guideline, you can see the following related to keyboard extensions: 4.4.1 Keyboard extensions have some additional rules. ... They must not: Launch other apps besides Settings; Here the guideline uses other apps, rather than simply apps or any app. I believe that means to say that launching the container app is allowed. To make sure my understanding is correct, I've reached out my App Review colleague, and they've confirmed that launching the container app from a keyboard extension (to do