“eskimo”

Historically, there was no supported way to maintain access to keychain items across an app transfer. That’s recently changed. However, this is still something you need to approach with caution. The process is tricky, and if you get it wrong you run the risk of significantly inconveniencing your users. I talk about this in a lot of detail in App ID Prefix Change and Keychain Access. [quote='821752021, neha24, /thread/821752, /profile/neha24'] Is this attribute kSecAttrAccessGroup helping us to retrieve the KeyChain items without having to rebuild [/quote] That depends on how you’re using this attribute. If you’re supply an app group ID, rather than a keychain access group ID, and you’ve transferred that app group to the new team then, yes, this is the approach discussed in the post I referenced above. If that’s not the case then something else is going on. ps The code snippets in your post are really hard to read. Check out tip 5 in Quinn’s Top Ten DevForums Tips for advice on how to avoid that in the future.

The way that device’s enforce CT is an implementation detail. There are no APIs to control that. Given that, it’s not something we usually get in to here on DevForums, where the focus is on APIs [1]. So, my advice here is that you file a bug about this. IMPORTANT Make sure to attach a sysdiagnose log taken on an affected device shortly after reproducing the issues. 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 [1] The on-the-wire behaviour of Apple devices falls under the domain of Apple Support in general. That’s why, for example, the documentation about this stuff, including Apple Platform Security, is on their website, not the Developer website.

Is this for Team ID N________H? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The best way to get this feedback to the right people is by filing it officially in Feedback Assistant. See Bug Reporting: How and Why? for lots of hints and tips on the process. I recommend that you split this up into multiple reports. You have a lot of different suggestions and things usually work out better when you split them up [1]. Please post your bug number — well, bug numbers — just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] We can split things up internally, but then you lose the ability to get any sort of status information, because those internal bug reports are no long associated with your team.

OK, so there’s two parts to this: Why the delay? What to do about the Team is not yet configured for notarization failure? The second part is the one that matters, but lemme quickly touch on the first. I have a standard spiel about this, which I’ve included at the end of this post, just as an FYI. Regarding the second part, this isn’t something we can help you with here on the forums. Rather, you need to seek help via official channels. For the details, see this post. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instru

iPad latest update version (4.7?) of Playground. Hmmm. I tried this here in my office and I was able to upload a build to the App Store just fine. I even went so far as to assign it to TestFlight internal testers group. I didn’t actually download it using TestFlight, but I fully expect that’d work. This is with Swift Playground 4.7 on iPadOS 26.3.1 (a). It’s all public stuff [1]. I’ve no idea why it’d be failing in your case )-: If you create a new app playground, just for testing, giving it a new unique bundle ID, are you able to upload that? ps 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. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Except my developer team, which is a work team I use for this sort of testing. However, my experience is that it this team behaves virtually identically to a third-party Individual team.

[quote='883156022, Richie_Wu, /thread/820894?answerId=883156022#883156022, /profile/Richie_Wu'] any update on this? [/quote] I don’t think so, but you can check for yourself in Feedback Assistant. Earlier I wrote: [quote='882231022, DTS Engineer, /thread/820894?answerId=882231022#882231022'] Is any of your code involved here? [/quote] Was I right in assuming that this isn’t the 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. It's been 6 days now … Hmmm, that’s not good. If you’re still seeing the problem when you get this, please post the UUID and creation date of the first stuck request and your most recent stuck request. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I don’t have any good input on the original issue that kicked off this thread, but I wanted to address this: [quote='883180022, -dp, /thread/806471?answerId=883180022#883180022, /profile/-dp'] if someone knows a good solution to disable all system logs while keeping my own [/quote] Xcode 15 introduced a new Console area with excellent integration with the system log. For example, consider this program: import Foundation import Network import os.log let log = Logger(subsystem: , category: ) func main() { let c = NWConnection(host: example.com, port: 80, using: .tls) c.stateUpdateHandler = { newState in log.log(did change state, state: ( (newState) )) } c.start(queue: .main) log.log(will enter main loop) dispatchMain() } main() IMPORTANT This is not meant to work. It tries to connect to the HTTP port using TLS, which won’t end well. The goal is to generate a bunch of log entries from Network framework, which it absolutely does (-: When I run this (Xcode 26.4 on macOS 26.3.1) I see this: will enter main loop did

[quote='883273022, blackson, /thread/820695?answerId=883273022#883273022, /profile/blackson'] I use two Contetnts Filter, both was not working. [/quote] Are these content filters that you created? Or are you using products created by other third-party developers? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

App Store Connect doesn’t have a way to do this. From its perspective, the bundle ID uniquely identifies the app and there’s no way to merge app records, or change the bundle ID for an app record. With Xcode this isn’t usually a problem, because you can change the bundle ID for your app in the project. So, you’d take your new project and change its bundle ID to be that of the original test project and away you go. I don’t know if that’s possible with your third-party tooling; I recommend that you ask that via the support channel for that tooling. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

AFAIK the official guidance hasn’t changed; see Porting just-in-time compilers to Apple silicon. As to what’s going on with your specific third-party runtime, I don’t have expertise in that codebase so it’s not something I have an opinion about. You have the usual options: Seek advice from the runtime vendor. Or, as this is open source, dig into the code yourself. ps It’s very unlikely that library validation is a factor here. Unless you have specific reasons for disabling it, I recommend that you re-enable it. That’s good for security and it helps you avoid various runtime problems caused by build-time issues [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] The one I see all the time is described in Resolving Gatekeeper Problems Caused by Dangling Load Command Paths, but there are others. For example, I sometimes see folks create an app that’s only partially signed, typically because they’ve embedded native code wi

[quote='821615021, matthewruzzi, /thread/821615, /profile/matthewruzzi'] Many posts on the Apple Developer Forums are categorized incorrectly. [/quote] Yeah, we’ve noticed )-: We have a bunch of ideas about how to improve this, but no concrete plans to share at the moment. [quote='821615021, matthewruzzi, /thread/821615, /profile/matthewruzzi'] It would be nice if there was a way to suggest changes to the topic and tags [/quote] Yeah, that’s be cool. Thanks for filing it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’ll come back to your main issue in a sec, but I wanted to start with this: [quote='821619021, diplomaticmedic, /thread/821619, /profile/diplomaticmedic'] Entitlement: com.apple.developer.networking.networkextension.url-filter-provider [/quote] That doesn’t make sense. There is no com.apple.developer.networking.networkextension.url-filter-provider entitlement. The entitlement key is com.apple.developer.networking.networkextension. As explained in the docs, the value is an array, and if you’re building a URL filter, then that array must contain the value url-filter-provider. So, either: You’re using com.apple.developer.networking.networkextension.url-filter-provider as a shortcut for com.apple.developer.networking.networkextension > url-filter-provider Or I’ve no idea how your code works at all I suspect it’s the former (-: Regarding your main issue, you wrote: [quote='821619021, diplomaticmedic, /thread/821619, /profile/diplomaticmedic'] Is there a Capability Request form I need to submit** for url-filter

This sounds like a bug in the App Store Connect app checking system. The -string entitlement values must be strings, because that format changes is what allows for back deployment. Please file a bug against App Store Connect. Once you’re done, reply here with your bug number and I’ll take action from there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com