apple pencil battery life

This smells like a Safari-side change/regression in the capability probe, not in the payment sheet itself. Treat applePayCapabilities() as advisory only for now. Implement a graceful fallback: always show the button when Apple Pay is supported, then try to launch a session. Use canMakePayments() (and optionally canMakePaymentsWithActiveCard) only to influence prominence, not eligibility. This is consistent with Apple’s guidance and long-standing WebKit advice. File a bug with reproducibles via Feedback Assistant. Assume this is a Safari capability-probe issue (and possibly anti-fingerprinting collateral) rather than your integration. Don’t block Apple Pay on the probe; keep the button visible and let the session tell you the truth. This both fixes your users today and aligns you with Apple/WebKit’s recommended UX.

You shouldn't need to set the key as it defaults to false. Might want to check out: https://developer.apple.com/documentation/technologyoverviews/adopting-liquid-glass Has very good guides for both UIKit and SwiftUI. Sad that Apple doesn't give a UIKit code example.

To be clear, I tested this with UIDesignRequiresCompatibility=TRUE. I don't know if this is the case for @jwcarr and I haven't tested this with glass Sliders. Also, flattered that I got an Apple Recommended badge, but not sure I deserve it for that post.

With card present environments, what's happening there is Apple Pay is sending the DPAN and cryptogram to the terminal, and terminal completes the charge. However, in card not present environments, from a payment processing UX perspective, the user has to see the amount they are confirming for pre-authorization. Otherwise it could lead to fraud cases. You could consider talking to your gateway or bank for Credential On File (COF) if you want to implement something similar to card present environments: You can save the card with a symbolic amount (or zero if the banks allow it) and then use the card you saved for the actual charge. But please beware that Credential On File brings its own set of rules and implementation requirements.

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