apple pencil battery life

I’m building an app that edits files in iCloud and uses an NSFilePresenter to monitor changes. When a conflict occurs, the system calls presentedItemDidGain(_:). In that method, I merge the versions by reading the current (canonical) version using NSFileVersion.currentVersionOfItem(at:) and the conflicting ones using NSFileVersion.unresolvedConflictVersionsOfItem(at:). This generally works, but sometimes, if two devices edit the same file at the same time, each device sees its own local version as the current one. For example: Device A writes fileVerA (slightly later in real time) Device B writes fileVerB On Device A all works fine, currentVersionOfItem returns fileVerA, as expected, and unresolvedConflictVersionsOfItem returns [fileVerB]. But on Device B, currentVersionOfItem returns fileVerB!? And unresolvedConflictVersionsOfItem returns the same, local file [fileVerB], without any hint of the other conflicting version, fileVerA. Later, the newer version from the Device A arrives on Device B as a normal, no

Hello Everyone! I recently got a termination notice. I've already sent an appeal 20 days back, I did get the response saying they'll not change the decision which is really a big problem! I've been developing apps and have been supporting my family for quite some time. But because of a small-mistake, I lost my entire account (Although I've made changes and re-submitted, but the app which got the removal isn't going for review) Anyone can you please help? I never got any kind of warning from Apple and I understood that since I'm using a commercial API, I could use it in my title, but it triggered removal of my entire account. Here's the notice I got: Upon further review of the activity associated with your Apple Developer Program membership, it's been determined that your membership has been used for dishonest or fraudulent activity, in violation of the Apple Developer Program License Agreement and the Developer Code of Conduct (App Review Guideline 5.6). Given the severity of the id

We have an IOUserSCSIPeripheralDeviceType00 class DEXT supporting USB attached devices. With some high-capacity drives, the default setPowerState can exceed 20s to complete. This triggers a kernel panic, although this drive behavior is not unexpected. With a kernel extension implementing similar functionality we see no such problem as it appears from reading of Apple open source the timeout was 100s. What changes will allow setPowerState to complete without the kernel panic? kernel panic report excerpt attached. panic-full-2025-09-04-063127.0003.txt

Hi , This is regarding the ApplePayRecurringPayment Request and Apple Pay on Web functionality. Does Apple Pay on web providing functionality that collects payments from the stored credit card issuer bank (or) it only provides secured wallet functionality that provides a token which then has to be utilized to send a seperate payment request through a third party payment gateway to collect the payments from the credit card issuer bank. thanks

With the latest (26) version of Apple's developer tools, is there a way to manually attach a debugger (other than lldb) to an iOS app launched with devicectl device process launch --start-stopped? In the past, this was possible via the ios-deploy third-party tool (now defunct), which provided a debugserver port. This information is notably missing when using devicectrl – although the process ID of the launch process is provided, and the tool is clearly aimed at letting you launch and attach to processes from the command line. lldb can, of course, attach via its built-in support for this using the device set of commands. But I'm explicitly looking for a way to attach my own debugger via the GDB-compatible debug proxy.

Hi everyone, Our recent app update was rejected under Guideline 2.1 – App Completeness, with the note: “The app was unresponsive when we tapped on Sign in with Apple.” Device: iPad Air (5th generation) OS: iPadOS 26.1 However, we’ve tested this thoroughly and can’t reproduce the problem at all. Here’s what we’ve done so far: Tested both on simulator and real devices (iPhone and iPad). Tried combinations of: Logged in / not logged in to iCloud Apple ID linked / not linked to our app In all cases, Sign in with Apple works as intended — no freezing or unresponsiveness. We also recorded videos showing successful sign-in on simulator (iPad Air, iOS 26) and iPhone 13 mini simulator: We replied to App Review asking whether they were using a simulator (since “Sign in with Apple” often fails there unless the test Apple ID is properly set up). We also provided steps and links explaining that you need to: Create a test account with a real email. Sign in at iCloud.com, and com