Overview

在使用 xode 27 真机调试项目时 报了 ibrary 'd64' not found 这个错误， 这边有用到-ld64 遇到这个问题需要怎么去解决呢？ xcode 26 没有报这个错

Seems like there is an issue in Xcode 27 beta 4 & 5 where DeviceHub doesn't show iOS 16 devices or simulators. I've checked the filters to ensure I haven't hidden anything and the are listed in the Xcode destination dropdown.

We are seeing inconsistent results from HKStatisticsCollectionQueryDescriptor on iOS 27. Using the same quantity type, statistics options, anchor date, interval components, and predicate configuration, some date ranges return the expected statistics, while other ranges unexpectedly return empty results or buckets with no quantity. The affected ranges do contain HealthKit samples: HKSampleQueryDescriptor finds samples in the same date range. HKStatisticsQueryDescriptor returns the expected value when run separately for an affected bucket. HKStatisticsCollectionQueryDescriptor returns no quantity for that same bucket. Slightly expanding or shifting the date range may cause the collection query to return data again. A simplified version of the query looks like this: let datePredicate = HKQuery.predicateForSamples( withStart: startDate, end: endDate, options: .strictStartDate ) let descriptor = HKStatisticsCollectionQueryDescriptor( predicate: .quantitySample( type: quantityType, predicate: datePredicate ), options: .cumulativeSum, anchorDate: anchorDate, intervalComponents: DateComponents(day: 1) ) let collection = try await descriptor.result(for: healthStore) collection.enumerateStatistics(from: startDate, to: endDate) { statistics, _ in let quantity = statistics.sumQuantity() print(statistics.startDate, quantity as Any) } Expected behavior Every interval containing matching samples should return the corresponding statistics, regardless of the overall requested date range. Actual behavior Some date ranges produce missing or empty buckets even though matching samples exist and an individual HKStatisticsQueryDescriptor can calculate the expected value. Changing only the date range can make the data appear or disappear. The samples are visible to the app in the affected range, so this does not appear to be explained solely by iOS 27’s Limited History authorization. This behavior was not observed with the same query flow on earlier iOS versions. Is this a known regression in HKStatisticsCollectionQueryDescriptor on iOS 27, or has the expected date-range or predicate behavior changed?

Short version: we run a sandboxed helper as a hidden service account, started at boot by an SMAppService daemon. It works, even before login. But when the user turns our app off in Background App Activity, only the daemon stops. The helper keeps running. Is this setup supported, and what's the right way to manage the helper? What we want A Developer ID signed, notarized app (not Mac App Store) with a helper that parses untrusted input. The helper should: run as a dedicated, hidden, non-login local account; use App Sandbox, with its own container; be available before anyone logs in (after FileVault unlock). What we built An unsandboxed root LaunchDaemon, registered with SMAppService.daemon, runs this at boot: launchctl bootstrap user/<serviceUID> <fixed-agent-plist> The agent plist uses LimitLoadToSessionType=Background. The helper is a nested app in the same bundle, with com.apple.security.app-sandbox=true. We don't create a GUI session, change UID after the sandbox starts, or use private APIs. What we measured macOS 27.0 (26A428), arm64, dummy data only: Register and approve: the daemon starts. The helper starts as UID 60000, its container works, and reads outside it are denied. Turn the app off in Background App Activity: the daemon gets SIGTERM and stops. The helper keeps running (same PID). Turn it back on: the daemon starts again. Its bootstrap returns exit 5, because the old helper is still loaded. Call unregister(): the daemon stops. The helper keeps running. Cold boot (tested with a plain /Library/LaunchDaemons job, not yet SMAppService): the helper started and worked before login finished. For comparison, running the same sandboxed helper as a system daemon with UserName set to this account fails before main: Incoming message euid:60000 does not match secinitd uid:0. Questions Is this setup supported for shipping, including the sandbox starting before anyone logs in? Does the approval for daemon-bundled helpers cover a helper bootstrapped into another account's domain? Our plan: when the daemon gets SIGTERM, it runs bootout on the helper and its domain, and it treats bootstrap exit 5 as "already loaded". Is that the intended pattern, or is there a supported way for the helper to follow the app's Background App Activity setting? If this setup isn't supported, what public mechanism gives a sandboxed helper its own non-root identity before login? I can share the plists, entitlements and logs from a minimal reproducer.

Hello, We are contacting you regarding an issue we are currently experiencing during the App Review process related to In-App Purchases and StoreKit product retrieval. After extensive internal testing and investigation, we believe the behavior we are seeing is identical to the issue discussed in the following Apple Developer Forum thread: https://developer.apple.com/forums/thread/827016 Our application was rejected under Guideline 2.1 - Performance because the subscription plans reportedly failed to load during review. According to the review notes, the In-App Purchase product list appeared empty in the review environment, which prevented the paywall from loading correctly. We would like to provide additional technical context because, despite significant testing efforts on our side, we have been unable to reproduce this behavior outside of the App Review environment. The exact same binary that was reviewed by App Review has been thoroughly tested by us through TestFlight on multiple physical devices, including iPhone and iPad devices, using multiple Sandbox tester accounts and different network conditions. In all of our tests, the subscription system functions correctly and consistently. Specifically, we verified that: StoreKit successfully retrieves all configured subscription products RevenueCat offerings load correctly without timeout or empty states Localized pricing information is displayed properly Subscription packages appear correctly in the paywall UI Purchase flows complete successfully Restore purchases functionality works correctly Products are returned both on cold launch and repeated application launches The issue does not occur intermittently in TestFlight or Sandbox testing on our side We also carefully reviewed our App Store Connect configuration and verified the following items multiple times: All In-App Purchase subscriptions are attached to the submitted app version Product identifiers used in the application code exactly match the identifiers configured in App Store Connect All products are marked as “Cleared for Sale” Paid Applications Agreement has been accepted and remains active Tax and banking information are complete and active Subscription localization settings are configured properly Pricing information is active and visible The products are available in the storefronts being tested The submitted binary is identical to the binary tested successfully through TestFlight Additionally, we implemented defensive handling in the application to minimize the impact of temporary StoreKit failures. The application now includes: Retry logic for offerings retrieval Graceful fallback handling for empty offerings Protection against infinite loading states Additional RevenueCat and StoreKit logging UI fallbacks when products temporarily fail to load Despite these safeguards, the review feedback still indicates that the products are not being returned in the App Review environment. At this point, because the issue cannot be reproduced externally and only appears during App Review, we suspect there may be an intermittent or environment-specific issue affecting StoreKit product retrieval in the review sandbox environment. One important detail is that the exact same build consistently works in TestFlight immediately before and after submission. This makes the behavior particularly difficult for us to diagnose because there appears to be no configuration difference between our successful tests and the App Review scenario. We also understand from Apple documentation and previous App Review communication that In-App Purchases are tested within an Apple-provided sandbox environment. Based on the evidence currently available to us, the failure appears to occur specifically within that review sandbox process rather than within the application logic itself. If possible, we would greatly appreciate assistance with the following: Verifying whether StoreKit product retrieval is functioning correctly in the App Review sandbox environment Confirming whether the review device successfully established communication with App Store sandbox services Providing any available diagnostic logs related to the failed product request Confirming whether the product identifiers were visible to StoreKit during review Sharing any guidance on how we may reproduce the App Review behavior locally Clarifying whether there are known intermittent issues affecting StoreKit product loading during App Review We are fully committed to resolving the issue and ensuring complete compliance with App Store requirements. However, because the issue currently appears environment-specific and non-reproducible from our side, we are struggling to determine what additional changes are necessary. If there are any additional diagnostics, logging methods, StoreKit verification steps, or App Review recommendations you would like us to implement, we would be happy to do so immediately. Thank you very much for your assistance, support, and time. We sincerely appreciate your help in investigating this issue. Best regards, Mert Akgün

For an In-App Purchase made by a customer whose App Store account is in the Saudi Arabia storefront, where Apple acts as commissionaire and remits VAT, does Apple issue the customer any tax document (a VAT invoice or a tax receipt), or is the customer's purchase history the only record available? Apple's support article 'View your purchase history for the App Store and other Apple media services' (support.apple.com/en-us/118212) documents viewing purchase history only — the words 'receipt', 'invoice' and 'tax' do not appear on that page.

Does App Review accept multiple In-App Purchases in the same app sharing an identical display name (for example ten non-renewing subscriptions all named 'Example Digital', differing only in price and duration)? The purchase sheet always shows the price alongside the name. App Store Connect Help documents a 2–30 character limit for the display name but states no uniqueness rule.

Does changing the price of an already-approved In-App Purchase trigger a new App Review, or does the new price take effect without review? App Store Connect Help states that changes to localized information require review and that 'New pricing will go into effect immediately', but never says explicitly whether a price change alone is exempt from review. We need this for a non-renewing subscription sold in the Saudi Arabia storefront.

Can an In-App Purchase that has reached the 'Approved' state ever be deleted from App Store Connect, either in the UI or through the App Store Connect API? App Store Connect Help documents no deletion procedure and no 'deleted' status. If deletion is possible, is it blocked while the product has existing purchases, or while it is still available for sale?

Does the App Store send a CONSUMPTION_REQUEST App Store Server Notification when a customer requests a refund for a non-renewing subscription? The documentation is inconsistent: the notificationType page lists only 'a consumable In-App Purchase or auto-renewable subscription', beginRefundRequest(in:) mentions only consumables, but the Send Consumption Information endpoint states it applies to 'any product type (consumable, non-consumable, non-renewing subscription, or auto-renewable subscription)'. Which is correct for a non-renewing subscription sold in the Saudi Arabia storefront?

I am developing CineZoom, part of CameraControl, a remote camera-direction system (macOS app controlling an iPhone capture engine). Its core requirement is a smooth, repeatable cinematic zoom. On iPhone 17 Pro (iOS 26.5.1), using the physical Back Ultra Wide camera at 3840x2160, 60 fps, a single native ramp(toVideoZoomFactor:withRate:) from 1.7x to 2.1x over 5 seconds shows a visible stutter. I isolated it with a minimal diagnostic app (no networking) and analysed four tripod recordings frame by frame, in two locations with different lighting. The results are consistent across all four: Jitter below 2.0x: while the zoom factor is below 2.0, the image centre shifts about 2.8 px RMS between consecutive frames (peaks ~5 px), alternating almost every frame (26-28 Hz). Above 2.0x, during the same ramp at the same speed, it drops to 1.2-1.5 px. Sharpness step at 2.0x: centre-crop sharpness drops by 23-31% within a few frames exactly when the zoom factor crosses 2.0. There is no consistent effect at the reported secondaryNativeResolutionZoomFactors value (1.7838). The zoom command path itself is correct: the zoom measured from the image matches videoZoomFactor throughout, with no dropped or duplicated frames. Questions: Is this expected behaviour for the Ultra Wide camera in this zoom range? Is the jitter related to video stabilization or to how the sensor crop is positioned in this readout mode? Is there a public API that reports or controls the zoom factor at which this transition happens, so an app can plan around it? What configuration do you recommend for a smooth continuous video zoom across 1.7x-2.1x on this camera (format, stabilization mode, constituent-camera switching)? Are there existing APIs that would let an app detect or compensate this (per-frame stabilization/crop metadata, consistent processing during zoom, or a reduced-processing video stream)? I have a full technical report, per-frame measurements, charts and the original recordings, and I am happy to share them. Thank you!

I’m developing an independent project in Scotland called Isla Watson. The architecture is built around a simple principle: the model is replaceable; the identity is not. Long-term memory, persistent internal state and identity are designed to remain outside the foundation model, allowing local models to act as replaceable reasoning and language components without resetting the companion. I’m now exploring whether Apple Silicon and MLX could provide the long-term local compute platform for the system — including specialist Mac nodes for reasoning, memory, speech and perception, with distributed inference when larger models are required. A particular area of interest is whether multiple Macs can be used in two complementary ways: as independent specialist agents during normal operation; and as a distributed MLX inference group when a larger model exceeds the capacity of one machine. The first technical study I’d like to establish is a reproducible 1-node → 2-node baseline, measuring model capacity, unified-memory use, time to first token, generation throughput, power consumption, agent concurrency and distributed scaling efficiency. The wider research goal is to keep persistent identity and state independent from whichever foundation model is currently providing language and reasoning. I’d particularly value guidance from anyone working with MLX distributed inference, Thunderbolt/RDMA multi-Mac setups, or local agent architectures. I’ve also posted an architecture-level overview in the MLX GitHub community and have a one-page public brief available for anyone interested in the wider design. https://github.com/ml-explore/mlx/discussions/4482

Since the XCode 27 came out with the device hub, I can't found the option "External Display"! This is outrageous, since I have an app that only works with a external display connected! This menu existed on the menu bar of the simulators, but since the simulators was replaced by the device hub, I can't debug or test my app anymore!

可以部署在本地，可以自动提取agent的上下文和工作并整理成记忆，用以约束智能体的工作，突破智能体上下文和llm上下文的限制，目前实测可以存储2.8万条记忆，提取速度38ms，我想跟大家讨论一下，他的应用面如何？

My enrollmet is pending, apple asked to me call them. But I don't know the number and I can't find it in the web page.

Hello, I recently received a Pending Termination Notice for my Apple Developer Program membership. The notice states that my account was identified as having provided false or fraudulent account information, documentation, or representations. I respectfully disagree with this finding. All information and documents I provided to Apple during enrollment and throughout my Developer Program membership are genuine and accurate. I have not intentionally provided false information, fraudulent documentation, or misrepresented my identity. I have complete original supporting documentation available and am fully willing to provide it again to Apple for verification, including identity and other relevant account verification documents. I have already been advised to submit an appeal to the App Review Board within the stated 30-day period, which I intend to do. I would appreciate guidance from anyone who has experienced a similar situation: Is there any additional verification process I should request as part of the appeal? Is there a recommended way to provide supporting identity documents for manual verification? Should I also contact Apple Developer Support in addition to submitting the App Review Board appeal? Is there anything specific that should be included when requesting reconsideration of a Developer Program termination related to Developer Identity? I am fully prepared to cooperate with Apple and provide any documentation necessary to verify the authenticity of my account information. My intention is simply to resolve any misunderstanding or discrepancy and have my Apple Developer Program membership reconsidered after verification. Thank you for any guidance.

Hi, I am still unable to complete my Apple Developer Program enrollment. My Apple Developer Support case number is 102973696378. Developer Support previously informed me that the issue appeared to be caused by a mismatch between the trusted phone numbers on my Apple Account and my enrollment region. At that time, my account had both a Pakistan (+92) number and a UK (+44) number. Following Apple Support’s instructions, I removed the UK (+44) number several days ago. My Apple Account now only has my Pakistan (+92) trusted phone number, and I am enrolling using Pakistan as my country/region with my Pakistani identification details. However, I am still receiving the same error: “Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time.” Since the phone number mismatch has already been corrected, I believe the previous enrollment attempt or old region information may still be associated with my account. Could Apple Developer Support please manually reset or clear my Apple Developer Program enrollment so I can submit a fresh enrollment? Case ID: 102973696378 I would appreciate any help in getting the enrollment reset. Thank you.

When I use my iPhone to scan the apple pay QR code in chrome, the url is https://applepaydemo.apple.com/apple-pay-js-api, I keep geting the "Service Unavailable" error. Wonder know if you guys meet this error as well? Btw, the QR code feature needs IOS 18.

Hello, I’m encountering a persistent code-signing verification failure when installing a development build on a registered physical iPhone. The project builds and signs successfully in Xcode, and the .app is transferred to the device. However, the installation fails when installd verifies the app’s signature. The relevant error is: Failed to verify code signature of Runner.app: 0xe8008018 The identity used to sign the executable is no longer valid. Domain: MIInstallerErrorDomain Code: 13 LegacyErrorString: ApplicationVerificationFailed Domain: IXUserPresentableErrorDomain Code: 14 Failure Reason: The app cannot be installed because its integrity could not be verified. Environment macOS: 26.6.2 (25G83) Xcode: 27.0 (27A266a) iOS: 26.6.2 (23G90) Device: iPhone15,4 Architecture: arm64 Installation method: Xcode Run on a registered physical device Signing type: Apple Development Provisioning: Development provisioning profile Important account history Our Apple Developer Program account was previously suspended and was later reinstated by Apple. Apple Developer Support has checked the account and stated that the membership account currently appears normal. However, development builds signed by this Team are still rejected by the device with 0xe8008018. This makes us suspect that the membership itself was restored, but some signing-related backend state may not have been fully restored or propagated, such as: Development certificate trust or revocation state Registered-device installation authorization Provisioning-profile validity A restriction or risk flag associated with the previous suspension Synchronization between the Developer account system and Apple’s device-side certificate trust services What I have verified The Apple Developer Program membership is active. The physical iPhone is registered with the Developer Team. The Bundle ID matches the provisioning profile. The build uses an Apple Development certificate and a development provisioning profile. The application builds successfully. Xcode completes the signing phase successfully. The resulting app contains an embedded provisioning profile. The app is successfully transferred to the device. The failure occurs during device-side signature verification, not during compilation or transfer. Cleaning and rebuilding the project produces the same result. The original missing-product-path issue has been resolved; Xcode is now installing the correct Runner.app. I have also reviewed Apple’s certificate documentation and discussions involving the same 0xe8008018 error. Some developers report that the same device accepts an app signed with another Apple ID or Team while rejecting builds signed by the affected paid Developer Team. I also found reports involving Sideloadly where forcing a different installation mode once and then returning to Apple ID signing caused the signing flow to recover. That exact workaround is not applicable here because this is a normal Xcode development build, not third-party IPA sideloading. However, it suggests that refreshing signing state on Apple’s side may affect the result. Questions Can a Developer Program membership appear active while the Team’s development certificates are still treated as revoked or invalid by device-side trust services? After a previously suspended account is reinstated, is there a separate process for restoring or resynchronizing development-signing privileges? Is there a way to determine whether this Team still has a backend restriction or stale certificate-revocation state? Has anyone resolved this without switching to a different Apple ID or Developer Team? What diagnostic files would be most useful for confirming whether this is a Team-level backend issue? Apple Developer Support case reference: 102975363424. I can provide an .xcresult, signed IPA, embedded provisioning profile, certificate details, and complete installation logs privately if requested. Thank you.

Hi, Safari shows a “Deceptive Website” warning for https://mim-kulinariya.com/. It’s a simple café menu with prices and contact details. No login, payments, personal data collection forms or tracking scripts. It’s hosted on GitHub Pages with a valid Let’s Encrypt certificate. I submitted a review request through websitereview.apple.com but have received no response at all. The warning discourages customers from visiting our website. Could someone from Apple please help expedite the review or explain how to escalate this? If a specific page or resource triggered the warning, please let us know so we can address it promptly. Thank you.