apple pencil battery life

Hello everyone, Our app was recently rejected under Guideline 5.0 – Legal (U.S. Sanctions Compliance). Apple review reported that the binary contains the following domain: https://lib.eshia.ir However, after extensive investigation: • The app does NOT connect to this domain • The app does NOT provide services to sanctioned regions • The domain does NOT exist in our source code, API calls, or UI • Network logs confirm no outgoing requests to this host We suspect the reference is coming from a bundled third-party dependency dataset (possibly a public suffix / domain validation / fraud detection list embedded in a framework). We already: Extracted IPA Scanned all source files Ran strings on the main binary Checked networking layer But we still cannot identify which framework contains this entry. Questions: Has anyone faced a sanctions rejection due to a domain inside a compiled SDK dataset? Is Apple expecting removal of the exact string from the binary even if unused? How do you typically ident

Hello, I recently purchased the Apple Developer Program and the payment is visible in my Apple subscriptions as active. However, when I open the Apple Developer app, I see the message:“Enrollment through the Apple Developer app is not available for this Apple Account.” When I follow the link to enroll via the website, it asks me to pay again even though I have already been charged. I have contacted support twice but haven’t received a response yet. It seems like my enrollment is stuck or not finalized. Has anyone experienced this before? How did you resolve it? Thanks in advance.

Description: I’m encountering an issue where the Apple Watch’s watchOS version is lower than the deployment target specified in my Xcode project. For example, my Watch device is running watchOS 10.6, but my app’s deployment target is set to watchOS 9.6 or 10.6, and Xcode shows an error stating: Error: “watchOS version doesn’t match the app’s deployment target.” Could someone clarify how to properly handle this version mismatch? Environment: Xcode 26 iPhone: iOS 18 Apple Watch: watchOS 10.6 Any guidance or best practices would be appreciated.

Hello, My app has been in Waiting for Review status for more than 48 hr. I have previously published 3 apps, and my last approval was in October. Normally, my apps move to “In Review” within 24–48 hours, so this delay is unusual. There are no messages in the Resolution Center and no visible issues in App Store Connect. Is this delay normal currently, or should I contact Apple Developer Support? Thank you.

During Apple Pay in-app provisioning (EV_ECC_v2), our iOS app successfully obtains the issuer provisioning certificates and generates cryptographic material. The flow fails when Apple posts the card blob to Apple’s broker (card creation step), returning HTTP 500 from .../broker/v4/devices/{SEID}/cards. Steps: Call issuerProvisioningCertificates?encryptionVersion=EV_ECC_v2 → 200 OK; returns ECC leaf + Apple Root CA chain; nonce=2a831be4. 2. Build {encryptedCardData, activationData, ephemeralPublicKey} 3. POST /broker/v4/devices/{SEID}/cards Expected: 200 OK on /broker/v4/devices/{SEID}/cards, or 5xx with a descriptive error if payload/cryptography is invalid. Observed: 500 Internal Server Error from Apple broker on /cards (labeled “eligibility” in PassKit logs), causing a terminal failure in Wallet UI.

Whats to code to warm it up once? Saw this in a developer video but cannot find it. Prevent cold run within an application. Thank you in advance!

My MacBook Pro M5 running MacOS Tahoe 26.3 beta fails to detect two identical ASUS ROG Swift OLED PG32UCDM monitors simultaneously. Only one display is recognized at a time. One potential root cause might be that both monitors report identical binary EDID serial numbers (0x01010101), and the MacBook Pro M5 appears to use this value exclusively for display identity rather than combining it with other more detailed information (e.g., port, or alphanumeric serial number). I've verified that the monitor EDID binary serial numbers are in fact identical -- however the alphanumerical serial numbers are not identical. NOTE: This behavior is specific to the MacBook Pro M5 — when connecting both monitors via usb-c to a Mac Mini M4 Pro running the same MacOS Tahoe 26.3 beta, the monitors work fine. The OS detects both and assigns different names to them (PG32UCDM (1) and PG32UCDM (2)). NOTE: I could be wrong about this root cause, I don't have a way to disprove it, though the fact the monitors work fine on a Mac Mini is