eskimo

I don’t know a lot about this feature, but the developer in this thread indicates that it’s working for them. 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 instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This is a known issue. See the discussion on this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='811284021, Papaductions, /thread/811284, /profile/Papaductions'] We've opened a feedback assistant report here: FB21445903 [/quote] Thanks. That’s definitely the best path forward here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for sharing those titbits. [quote='805770021, Wearetriple, /thread/805770, /profile/Wearetriple'] please update the documentation! [/quote] The best way to get that request to the right folks is to file a bug against the docs. 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='869936022, DTS Engineer, /thread/118508?answerId=869936022#869936022'] The simplest solution [/quote] Agreed, but I also want to note that macOS 26.3 beta restores the behaviour you saw on earlier systems. See this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Does this crash generate a crash report? If so, please post an example. See Posting a Crash Report for advice on how to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I can’t help you with the Core Bluetooth side of this, but I wanted to reply about this: [quote='810872021, Magnudr, /thread/810872, /profile/Magnudr'] does anyone know what is going on with Apple's entitlement service? [/quote] I’m not aware of any general problem affecting entitlement approvals, although my experience is that lead times can vary wildly, from a few days to months, depending on the entitlement being requested. We can’t help you with specific requests here on the forums, so you should seek formal assistance via Apple > Developer > Contact Us > Development and Technical > Entitlements. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='870261022, MaheshGubbi, /thread/808088?answerId=870261022#870261022, /profile/MaheshGubbi'] will there be any problem in apple review ? [/quote] DTS and App Review are separate organisations and we can’t give you definitive answers about their policy. My general advice is: Check App Review’s published guidelines. If that doesn’t answer your question, you should feel free to engage with App Review directly. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='870122022, Hylus-Arbor, /thread/806187?answerId=870122022#870122022, /profile/Hylus-Arbor'] We had a similar issue with Accessibility permissions in 26.1 and 26.2 Beta. However it has now been fixed in 26.3 Beta. [/quote] [quote='870110022, dseijffers, /thread/806187?answerId=870110022#870110022, /profile/dseijffers'] Seems that this is resolved in 26.3 beta 1 [/quote] That gels with my expectations. Thanks for taking the time to test this on the beta seed. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

First up, you’re correct that there’s a contradiction here: Apple has effectively deprecated the file-base keychain in favour of the data protection keychain. But the Personal Team limits, which come from iOS, run counter to the expectations of macOS developers. I don’t have any answers for you on that front, but if you file a bug describing this contradiction and post the bug number here, I’ll make sure that the relevant folks see it. Coming back to your real issue, there’s a lot to unpack there and I don’t have time to dig into it all. However, you seem to have bumped into a pretty fundamental limitation: You want the system to protect your item such that only your program can access it. But you’re not giving it any code-signing credentials to do that. Something has to give. The file-based keychain has a bunch of legacy access control centred around code-signing requirements — see TN3127 Inside Code Signing: Requirements — so that’s one thing you might explore. But that still requires you to have a stable c

[quote='869055022, Yvan.d, /thread/809534?answerId=869055022#869055022, /profile/Yvan.d'] could this type of Keychain item design … lead to the kind of attribute inconsistency [/quote] It’s certainly possible. My experience is that there’s a lot of really bad keychain code out there )-: That’s partly because the SecItem API is way more subtle than people think, and partly because Apple’s initial documentation and sample code for it was… well… less than ideal. Moreover, the keychain is a persistent database where it’s important to not lose user state. So if your app has been around for a while, debugging a keychain problem means that you have to understand your current code and all the previous iterations of that code. There’s a few ways to tackle a problem like this: You could use source control to resurrect old versions of your keychain code, put all that code in a test app, and then try it out. You could use telemetry to understand the state of your users’ keychain items in practice. You could do what you’r

[quote='869124022, shi11, /thread/661320?answerId=869124022#869124022, /profile/shi11'] Would it be possible to get a status update? [/quote] No. Our focus here on the forums is APIs. We can’t help you with account issues because the forums are public and the details of your account are not. The standard escalation path for entitlement requests is Apple > Developer > Contact Us > Development and Technical > Entitlements. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Well, that’s weird. And it doesn’t gel with my experience. Admittedly, that was all prior to iOS 26, so it’s possible we broke something. I’m gonna try to reproduce this here in my office, but I won’t have time to do that until after the winter break. [quote='869103022, captadoh, /thread/808917?answerId=869103022#869103022, /profile/captadoh'] Are you open to me inviting you to a private Github repo? [/quote] It’s much more convenient to do this with public source code. Keep in mind that you don’t need a full app to test this. Just getting TCP to connect (or the QUIC tunnel) is sufficient to confirm that peer-to-peer Wi-Fi is working. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com