Apple Maps Guides

That could be a little problematic to have all gateways in the same domain because as far as I understand, Apple provides the domain verification files per platform integrator, so the gateway that provided you with the verification file is your integrator. And I am not sure how Apple treats multi-integrator platforms. Is it possible for you to register as a merchant, decrypt the payload as a merchant and then send the transaction to gateways for authorization? That might be a better solution.

I do not think it is related to China as I live in Europe and get the same problem on my work MacBook Pro. The weird thing is that I get mixed results from a playground in Xcode (see attached pictures). Both ready to go and Model assets are unavailable. My managed macBook Pro has a profile that blocks only two things from Apple Intelligence: Allow integration with external intelligence services (macOS 15.2 or later) Allow Apple Intelligence: external intelligence workspace IDs (macOS 15.3 or later) I'm on Tahoe 26.0.1 and Apple M2 Pro. Any suggestion to allow me to run Foundation Models on my Mac? (At home, on my private MacBook Pro, everything works as expected)

For me, custom sounds do seem to be working but they do not loop, which effectively makes them useless as an alarm. For now, I've disabled the custom sound feature in my app and I just set the sound to .default. I plan to enable the feature if/when Apple fixes it.

I filed a bug report (FB20465338) but I also want to note some more details here in case this is useful to someone: When navigating back/forward in a WebView or WKWebView, the page suddenly jumps up. The reason appears to be that WebKit automatically adds some padding to the top of the webpage to account for the unsafe nav bar area, but it then forgets to account for this padding when navigating back/forward. The effect is especially pronounced if you swipe back/forward. When swiping you see a static preview of the incoming page, but when you release the swipe, the page suddenly jumps up. As far as I can tell, this has always been an issue, but before iOS 26 it wasn't really a problem because the WebView would usually be flush against a solid nav bar. However, in iOS 26, this bug is problematic because Apple is asking us to flow the web content behind the nav bar; indeed, this is the default behavior of a WebView. There's effectively no good solution in iOS 26 because you basically have two choices:

[quote='860620022, dreisicht, /thread/802464?answerId=860620022#860620022, /profile/dreisicht'] the project is open source anyway. [/quote] Yeah, but if you send me a binary then I don’t have to mess around with build systems (-: [quote='860620022, dreisicht, /thread/802464?answerId=860620022#860620022, /profile/dreisicht'] Here is the zipped .app [/quote] Thank you! This layout is much what I’d expected: mach-o-images.txt Note I’m using the FindMachO.sh script from here. Or, as a hierarchy: hierarchy.txt That is, you have a vast array of code embedded within the Contents/Resources directory. It’s feasible to sign and distribute this. It doesn’t follow the rules in Placing content in a bundle, but this particular structure is tolerable, at least for the moment [1]. So, to sign this you need to generate a list of these code items, sort them in dependency order, and sign each one in that order. This is pretty much the process described in Creating distribution-signed code for macOS. Share and Enjoy — Quinn “The

interferon, 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. You wrote: How much should I worry about this error? That depends on what the backtrace looks like. If the backtrace leads to your code, that’s something you should worry about. If the backtrace only shows system code, that makes this log noise, as defined here. [quote='860615022, pi80223, /thread/802423?answerId=860615022#860615022, /profile/pi80223'] I've seen this error message too when running a very simple SwiftUI app [/quote] I tried that here in my office and didn’t see the log. Specifically: Using Xcode 26.0.1 on macOS 15.6.1, I created a new project from the macOS > App target, choosing SwiftUI as the language. I ran that on my iOS 26.0 (23A341) test device (by a strange coincidence, it’s also an iPhone 16). I waited for 10 seconds. Then swiped up from bottom to send it to the background. And it’s a bummer I can’t reproduce it because I might be able to learn mor

Are you able to actually use the migrated keychain items? I’ve seen cases where items are migrated but, because of the way that they’re protected, you can see the item but, when you go to use it, the unwrap fails with an error. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='860540022, sjmills, /thread/802525?answerId=860540022#860540022, /profile/sjmills'] Do you suggest that I add a 2nd bug report requesting a new app extension technology API? [/quote] Nope. FB5703360 has landed in the right place. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m not sure what your goal of that post was. I understand that you’re crashing due to an unrecognized selector exception. As I mentioned above, that’s almost certainly caused by a memory management error and you need to debug that rather than try to mask the problem. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='856112022, Evozi, /thread/73148?answerId=856112022#856112022, /profile/Evozi'] How about iOS 26? [/quote] AFAICT the limits are unchanged on iOS 26. If you’d like to see bigger limits, the best way to get that feedback in front of the folks who have the power to enact change is file it in Feedback Assistant. Make sure include details about what you’re trying to do and why the current limits are negatively affecting your users. Please post your bug number, just for the record. Also, keep in mind that iOS 26 runs on old devices which are significantly more memory constrained than the shiny new hardware you might be using. My daughter may one day have to give up her iPhone SE (2nd generation), and thus accepted the new reality of Face ID, but today is not that day (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='860505022, jameseasylog, /thread/799838?answerId=860505022#860505022, /profile/jameseasylog'] I would guess this is because iOS 16 and earlier doesn't have Sectigo root certificates loaded [/quote] It’d be better to check rather than guess. Which brings me back to this comment: [quote='857543022, DTS Engineer, /thread/799838?answerId=857543022#857543022'] There’s a bunch of links … in Networking Resources. [/quote] Networking Resources include various links to the Apple Support articles that explain which root certificates are installed on which versions of iOS. I’m not able to speak for Sectigo, obviously, but a quick ’net search for Sectigo Public Server Authentication Root R46 suggests that they are in the process of transitioning from one root to another. If iOS 16 compatibility is important to you, I recommend that you discuss this with them. It’s possible that they might have some advice for how to tweak your server to be compatible. Share and Enjoy — Quinn “The Eskimo!” @ Developer Tec

So, the code under test takes a trust object (SecTrust) and returns an allow / deny decision based on the public keys in the certificates in the chain? If so, you could solve this problem by having you test hardness create the trust object using the basic X.509 policy (SecPolicyCreateBasicX509()) rather than TLS policy (SecPolicyCreateSSL(_:_:)). ps You’re probably aware of this, but ATS supports public key pinning via the NSPinnedDomains property. If that works for you, it’s a lot easier than doing this in code. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com