eskimo

Given that we’re talking about notarisation, that means Developer ID signing, and I have some general advice on that topic. See The Care and Feeding of Developer ID. As to your main issue, you wrote: [quote='812229021, treedweller, /thread/812229, /profile/treedweller'] Otherwise, notarization will fail. [/quote] That’s not giving us a lot to go on. Which step fails? And how does it fail? What error is reported? Speaking generally, I’m not aware of anything that would cause notarisation to fail in this situation. Lots of developers notarise from multiple machines, for example, in CI/CD systems. Given that, I suspect that there’s something weird going on with your setup specifically. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

MetricKit reports jetsam counts — see the cumulativeMemoryResourceLimitExitCount properties hanging off MXAppExitMetric — but it doesn’t report any details in the form of a diagnostic. I did some rummaging and discovered that we already have a enhancement request for this (FB9972410). If you’d like to be notified if and when this is added, I recommend that you file a bug and ask that it be dup’d to that bug. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

So one of the following must be true: You want to use the Background Tasks framework to run long-running tasks via BGProcessingTask. Or you don’t. If you do, add the BGTaskSchedulerPermittedIdentifiers property to your Info.plist and populate it with the list of background task identifiers you use. If you don’t: Remove the processing value from the UIBackgroundModes property in your Info.plist. Remove any code that uses BGProcessingTask. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks. I’ve asked about this internally and I’ll update this thread when I know more. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

OK, I got a response, which is good, but I can’t share a concrete timeline [1]. What I can say is that: Your bug is with the right folks. They understand the urgency of this. That urgency will only increase as more developers complete their URL filter projects and receive approval for their relays. I will continue to monitor this situation but, honestly, you might hear about the fix via Feedback Assistant before I notice it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] There’s nothing special about that; it’s just our standard rules of engagement here on the forums. See tip 3 in Quinn’s Top Ten DevForums Tips.

[quote='871489022, MikasaAlen, /thread/805248?answerId=871489022#871489022, /profile/MikasaAlen'] Does iOS 26 completely prohibit the use of private APIs? [/quote] It’s best not to think about this stuff in terms of public and private APIs. Rather, there are APIs, the public things that we specifically publish for third-party developers to use, and implementation details, meaning everything else. Once you think about it this way, the consequences are clear: If you use APIs, you can reasonably expect consistent behaviour. If you rely on implementation details, the behaviour can change between different OS releases, different device types, different users, and so on. [quote='871489022, MikasaAlen, /thread/805248?answerId=871489022#871489022, /profile/MikasaAlen'] And is the only recommended method for opening the [Settings app] now the use of [UIApplicationOpenSettingsURLString] API? [/quote] Supported URL Schemes lists lots of different APIs for opening Settings, each focused on a specific test. But if you wan

[quote='871501022, roanutil, /thread/811382?answerId=871501022#871501022, /profile/roanutil'] It's just preferences stored in the key-value store. [/quote] Cool. [quote='871501022, roanutil, /thread/811382?answerId=871501022#871501022, /profile/roanutil'] I have updated the entitlement value with the correct Team ID. [/quote] OK. But you shouldn’t need to do that because Xcode should pick up the correct Team ID via the $(TeamIdentifierPrefix) syntax. As to your main issue, I suspect that Xcode has cached something that’s causing this. In situations like this I generally approach the problem in two ways: First, I create a new dummy test app, with a new bundle ID and thence a new App ID, to check whether this is working in general. Once I’ve confirmed that, I then start trying to resolve the issue with my real project. With regards that second step: In Signing & Capabilities, make sure that “Automatically manage signing” is enabled, the new team is selected in the Team popup, and that Signing Certificate is

I’ve no info to share right now, but lemme go ping some folks… Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='871359022, Waad, /thread/812013?answerId=871359022#871359022, /profile/Waad'] The target team is an Individual Apple Developer account [/quote] OK. That explains the behaviour you’re seeing. [quote='871359022, Waad, /thread/812013?answerId=871359022#871359022, /profile/Waad'] Please let me know how this can be resolved for an Individual account [/quote] I think the only good way to resolve this is to update the team to an Organization team. See the instructions in Developer Account Help > Account > Updating your account information > Updating an individual membership to an organization membership. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='871537022, KrishnaveniNalka, /thread/811866?answerId=871537022#871537022, /profile/KrishnaveniNalka'] Attached the files to [FB21464147] ticket. [/quote] Thanks. That’s the right place for them. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='871409022, OrchardAcre, /thread/807490?answerId=871409022#871409022, /profile/OrchardAcre'] Maybe someone playing with the 26.3 beta can check for us? [/quote] Based on my reading of the bug we’re using to track this issue (r. 164272589), 26.3b1 (23D5089e) doesn’t have a fix for this. However, and as always, I encourage folks to test with new beta releases as we seed them. 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. 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 inference. Such programs a

[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 workaround, and I

That seems like a reasonable request. The best way to get it to the folks who have the power to enact change is to file it officially using Feedback Assistant. 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

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