Posts under App & System Services topic

Post

Replies

Boosts

Views

Activity

New features for APNs token authentication now available
Team-scoped keys introduce the ability to restrict your token authentication keys to either development or production environments. Topic-specific keys in addition to environment isolation allow you to associate each key with a specific Bundle ID streamlining key management. For detailed instructions on accessing these features, read our updated documentation on establishing a token-based connection to APNs.
0
0
4.3k
Feb ’25
Meet State Reporting and the new MetricKit
Hello developers! Thank you for your dedication to creating apps with great performance. We’re excited to kick off another year of partnering with you on improving power and performance in your apps. At WWDC26, check out the following new things in the latest platform SDKs and Xcode 27 beta for performance. You can also join us online for a Power and Performance Group Lab on Tuesday, June 9 at 11 AM Pacific. Meet State Reporting and the new MetricKit State reporting: The new StateReporting framework lets your application express its state to downstream tools like Instruments and MetricKit. Make your telemetry and traces much more useful by adopting this simple API. MetricKit: In the 27 releases, the Swift-first MetricManager API replaces the MXMetricManager API. Combined with State Reporting, the new MetricKit provides more granular metrics to isolate performance problems faster. It also provides a more expressive API that is great to use in Swift, with improved Swift concurrency and Codable support. With this year’s releases, the MXMetricManager API is considered legacy. ▶️ To learn more, watch Meet the new MetricKit. Discover new features in Xcode organizer Metric goals: Xcode organizer now provides a goal metric for Battery Usage, Disk Writes, Hang Rate, Hitches, Memory, and Storage metrics, allowing you to prioritize performance engineering across more areas. Generate recommendations: Quickly resolve the highest impact performance issues in your app by using Generate Recommendations for Crash, Energy, Disk Write, Hang and Launch diagnostics. Insights overview: The new insights overview in Xcode organizer summarizes high-impact performance regressions for metrics and diagnostic reports, helping you plan and prioritize performance engineering work. Storage metrics: Storage metrics are now available in Xcode organizer, allowing you to monitor your app's Documents & Data and App Size across releases and catch regressions in cache usage and bundle size. Hitches metric: The new Hitches metric replaces the Scrolling metric in the organizer and now displays hitches for all animations in your app, giving you a comprehensive view of animation performance. ▶️ To learn more about other advancements in Xcode, watch What’s new in Xcode 27. Improve app responsiveness with Instruments Foundation Models: The Foundation Models instrument is redesigned with a tree view that lets you drill into individual requests, inspecting tool call arguments and results, inference prompts and responses, and token statistics. Use it to understand caching behavior, measure latency, and optimize throughput. System Trace: System calls, VM faults, and thread states are now unified into a single plot, with a new blending algorithm that stays readable even at high density. Once you spot something worth investigating, left/right key navigation lets you follow a thread's activity step by step, and the inspector provides quick actions like pinning the thread that made another thread runnable. System Trace now also draws thread priority and QoS over time, making it easier to identify priority inversions and unexpected QoS degradations that affect responsiveness. Swift Concurrency: New Main Actor and Global Concurrent Executor tracks let you visualize running tasks and executor queue depth over time, making it easier to spot task scheduling delays and actor contention. Tasks are now grouped into collections for faster navigation. Swift Tasks, Actors, and Executors instruments can now surface Call Trees, Flame Graphs, and Top Functions scoped to each entity — so you can pinpoint exactly where concurrency overhead lives. Top Functions: Helper functions and runtime internals can be expensive but hard to spot in a standard call tree. The new aggregation mode in Top Functions surfaces any function's total execution time across the entire call stack, making it easy to identify and prioritize hidden hotspots. Run Comparison: Compare call tree data across builds to identify regressions and performance wins. Results can be explored as an outline, flame graph, or top functions — choose whichever view best fits your workflow. ▶️ To learn more about profiling your app with Instruments, watch “Profile, fix, and verify: Improve app responsiveness with Instruments” ▶️ To learn about Foundation Models optimization, watch “Debug and profile agentic app experiences with Instruments”. If you have any questions about using State Reporting or the new MetricKit, create a post on the forums. For help creating a post, see Tips on writing a forum posts.
0
0
1.9k
Jun ’26
MKMapItem addressRepresentations fullAddress singleLine does not always work and provides the address in multiline
Hello, I’m trying to display in my app the full address of an MKMapItem in a single line. I notice the following function does not always return single line but contains newlines. https://developer.apple.com/documentation/mapkit/mkaddressrepresentations/fulladdress(includingregion:singleline:) I provide the list of some identifiers so you can check what’s wrong. "I39866265D4A8562A", // 🟢 works "IF233A1E949A5566C", // 🟢 works "ICA31B6B98E02A528", // 🔴 does not work "ICA31B6B98E02A528", // 🔴 does not work "I9E00A04BFCB9718D", // 🔴 does not work "IFACDC4BC25712413", // 🔴 does not work "I74135A4F7C7FE654", // 🔴 does not work "IFE4A3BC4FEFA53E0", // 🔴 does not work You can check this FB25681688 Thank you, Regards, Axel
0
0
4
38m
StoreKit 2 returns USA storefront and USD price in TestFlight despite Japanese Apple Account
Hello, I'm developing an iOS app that uses StoreKit 2 for an auto-renewable subscription. I'm experiencing an issue where StoreKit returns the US storefront and USD pricing in TestFlight, even though the device's Apple Account and Sandbox Apple Account are configured for Japan. Environment App: YonsanmaruTimer (430タイマー) App version: 1.2.0 (TestFlight build 4) Bundle ID: com.manyouen.YonsanmaruTimer Product ID: com.manyouen.YonsanmaruTimer.plusassist.monthly StoreKit 2 Xcode Archive configuration: Release App Store Connect configuration The subscription is configured with the following prices: Japan: ¥200/month, with a one-month free trial United States: $0.99/month The app is intended for distribution in Japan. Observed behavior When fetching the subscription product using Product.products(for:), I log the current storefront and product price. The result is: Storefront: USA Price: $0.99 Currency: USDAs a result, the subscription price displayed in the app using product.displayPrice is $0.99 instead of ¥200. What I have already checked The device's Apple Account country/region for Media & Purchases is Japan. TestFlight is installed using my regular Japanese Apple Account. I created a new Sandbox Apple Account with Japan as its country/region and signed in through Settings → Developer → Sandbox Apple Account. The storefront still returns USA after restarting the TestFlight app. The app is archived using the Release build configuration. In an earlier subscription purchase test, Apple's native purchase confirmation sheet displayed ¥200, even though the app's product display price was $0.99. Questions Why would Storefront.current return USA in TestFlight under these conditions? Is this expected behavior in the TestFlight sandbox environment? Could this behavior also occur after the app is released on the App Store? Is there any additional account, device, or App Store Connect configuration I should check? I would like to ensure that the subscription price displayed in my app matches the price shown in Apple's purchase confirmation sheet before submitting the app for review. Any guidance would be greatly appreciated. Thank you.
0
0
69
11h
Sandbox IAP: AuthKit succeeds, then AMSServerErrorDomain -5000 (cancel-purchase-batch)
Every sandbox purchase of our auto-renewable subscriptions cancels right after AuthKit sign-in succeeds. It's blocking our 1.0 release. Filed as FB25469063, no reply yet. Capacitor iOS app, bundle io.xrplive.app, 1.0.0 (TestFlight), products io.xrplive.app.pro.monthly / .yearly, iPhone 17 Pro Max on iOS 27.0.1, StoreKit via @capgo/native-purchases. Console on every attempt: (1) AMSAuthKitUpdateTask: "The AuthKit authentication succeeded." (2) Then: Error Domain=AMSServerErrorDomain Code=-5000 UserInfo={failureType=-5000, m-allowed=false, cancel-purchase-batch=true, customerMessage=Check the account information you entered and try again.} Also AMSErrorDomain Code=100 (Authentication Failed), Code=2 ("Password reuse not available for account"), and a 401 from sandbox.itunes.apple.com/commerce/messages/app/inbox. We already fixed a purchase(confirmIn:) presentation issue. This failure is in sandbox verification after a successful sign-in, which we can't fix from the client. Is -5000 with cancel-purchase-batch a known sandbox account or commerce issue? Is there a sandbox tester or storefront state that fixes it when AuthKit succeeds but verification still fails?
1
0
67
11h
Virtualization.framework — stop completion and storage release
Hello Apple Developer Support, We are evaluating a macOS VM controller using VZVirtualMachine and would appreciate clarification: Does stop(completionHandler:) have any documented maximum completion time? What should a controller do if completion never arrives? After successful completion, are all backend writes finished and disk-image resources released, or is additional teardown required? What documented sequence establishes that the VM’s complete writable storage set—including disk images and macOS auxiliary storage—can safely be deleted, replaced or restored? Do these guarantees depend on caching/synchronization mode or macOS version? We understand that forced stop does not guarantee a clean guest shutdown or application consistency. Our question concerns host-side storage quiescence and resource release. Documentation references would be helpful. Thank you.
0
0
84
16h
Driver approval pending
Hi team, It has been nearly a month since we submitted our driver approval request (3DRN3G5AMB), and it is currently still pending. This prolonged delay is severely impacting our operations, and as there is no self-service option for us to expedite this on our end, we urgently need your assistance to move this forward. Could you please check the status of this request with the relevant team and let us know what is causing the hold-up, or how we can escalate it? Thank you for your prompt help with this
1
0
59
17h
What is actually needed for a HID device to be picked up as a GCController?
I am trying to interface with a custom USB Device that uses a CAN bus for communication and turn it in to a game controller that the GameController Framework recognizes. I have it creating a Virtual HID device just fine and applications that read the HID information directly read the state just fine. But the ones that are using the GameController framework are saying there are no game controllers found. If the HID device descriptor saying it's a Joystick or GamePad is not enough, what else is needed?
0
0
76
1d
How should a macOS app determine when to call requestAgeRange for California users?
Apple documents that AgeRangeService.isEligibleForAgeFeatures returns false on macOS, while requestAgeRange can still return a declared age range on supported Macs. What Apple-provided signal, if any, should a native AppKit app check before calling requestAgeRange to determine whether a California age-bracket request applies? Is requiredRegulatoryFeatures intended for this case? Does the answer differ for an iPad app running on an Apple silicon Mac? For existing installations on macOS 15, is there a supported App Store mechanism to obtain the signal when the OS framework is unavailable? A pointer to the relevant API documentation, minimum OS versions, or a macOS sample would help.
0
0
84
1d
Updating an FSKit module to use the new Handler protocols
I have a file system extension that currently uses the various now-deprecated Operations protocols. I have a few questions about moving to the new Handler protocols. First, my module is going to maintain backwards compatibility with macOS Sequoia for the foreseeable future, but I would also like to be able to take advantage of new FSKit features for users who are on newer OS versions. What approach would you recommend: Having an FSVolume conform to both the various Operations and Handler protocols (e.g. both FSVolumeKernelOffloadedIOOperations and FSVolume.KernelOffloadedIOHandler with the latter tagged with @available) an immediate issue I see trying to do this is I run into the error Method 'activate(options:)' with Objective-C selector 'activateWithOptions:replyHandler:' conflicts with previous declaration with the same Objective-C selector when trying to conform to both FSVolume.Handler and FSVolume.Operations. Having two separate FSVolume implementations, one used for older OS versions with Operations support and one used on newer OS versions with Handler support? Keeping the use of pre-existing Operations protocols while only using the Handlers for newer features (e.g. things like SeekRegionHandler) Second, I see at https://developer.apple.com/documentation/fskit/fsvolumehandlerresult/requestedattributes that I must populate all requested attributes. Does this value only have a meaning if the initializer for the actual concrete result type has an initializer that takes in a FSItem.Attributes instance, or is there some way I’m supposed to populate those? (As a concrete example, FSCheckAccessResult has init(accessAllowed:) which doesn’t take in any attributes.)
6
0
966
1d
Enrollment in dev program stuck
Case ID: 30000008563290, submitted Nov 7. I am unable to enroll in the Apple Developer program. I get a message stating "Unable to enroll at this time". I have a submitted a couple of email follow-ups and have not received a response. I am able to provide identification documents if necessary. I had a phone call and the support team member was unable to help - She said she couldn't see why it was blocked, and that she would escalate to a supervisor. I am hoping someone from the Apple support team can take a look and help me enroll. I have attempted both web enrollment and enrolling via iphone developer app. Thanks in advance.
1
0
84
1d
"IOSurface creation failed" drawing to CGContext
(more details on StackOverflow) I'm getting messages like the following, SOMETIMES, when I draw to a CGContext IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5207703552; IOSurfaceAllocSize = 9461418; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } call to context.draw(): context.draw(photo.image, in: CGRect(x: 0, y: top, width: width, height: height), byTiling: false) The results are just fine, so the draw seems to be working. It also, most often, draws without producing this error, but it fails pretty often. I'm not sure where to begin looking to sort out what I might need to do differently to avoid this error message in the console. Complete code: import Foundation import SwiftUI func generateSpritesImage(thumbPhotos: [Photo], width: Int, filename: URL) -> [Int] { var indices = [Int]() let totalHeight = thumbPhotos.reduce(0) { $0 + $1.heightOfImage(ofWidth: width) } debugPrint("creating context") let context = CGContext(data: nil, width: width, height: totalHeight, bitsPerComponent: 8, bytesPerRow: 0, space: CGColorSpace(name: CGColorSpace.sRGB)!, bitmapInfo: CGImageAlphaInfo.noneSkipLast.rawValue)! var top = totalHeight for photo in thumbPhotos { let height = photo.heightOfImage(ofWidth: width) indices.append(top - totalHeight) top -= height debugPrint("drawing \(photo.filteredFileURL())") context.draw(photo.image, in: CGRect(x: 0, y: top, width: width, height: height), byTiling: false) } debugPrint("write jpeg") writeJpegFromContext(context: context, filename: filename) return indices } func writeJpegFromContext(context: CGContext, filename: URL) { let cgImage = context.makeImage()! let bitmapRep = NSBitmapImageRep(cgImage: cgImage) let jpegData = bitmapRep.representation(using: NSBitmapImageRep.FileType.jpeg, properties: [:])! try! jpegData.write(to: filename) } sample of output: "drawing 0002-_MG_8542.jpg" "drawing 0003-_MG_8545.jpg" "drawing 0004-_MG_8550.jpg" IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5211357184; IOSurfaceAllocSize = 9983331; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } "drawing 0005-_MG_8555.jpg" IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5221351424; IOSurfaceAllocSize = 10041215; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } "drawing 0006-_MG_8562.jpg" "drawing 0007-_MG_8563.jpg" IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5376163840; IOSurfaceAllocSize = 10109756; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } "drawing 0008-_MG_8584.jpg" "drawing 0009-_MG_8618.jpg" IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5394612224; IOSurfaceAllocSize = 8425564; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } "drawing 0010-_MG_8627.jpg" "drawing 0011-_MG_8649.jpg" "drawing 0012-_MG_8658.jpg" "drawing 0013-_MG_8665.jpg" "drawing 0014-_MG_8677.jpg" "drawing 0015-_MG_8675.jpg" "drawing 0016-_MG_8676.jpg" "drawing 0017-IMGP0873.jpg" "drawing 0018-_MG_8719.jpg" "drawing 0019-_MG_8743.jpg" ...
4
1
2.8k
1d
macOS: pre-established stop mechanism when a VM supervisor stops progressing
I am evaluating a bounded workload host using Virtualization.framework on Apple silicon. This is a question about supported architecture and API contracts, not a report of a reproduced bug. No particular macOS release has yet been qualified for this design; please identify the releases and prerequisites to which an answer applies. I have read the discussions about cleanup after the VM-owning application terminates: https://developer.apple.com/forums/thread/848542 https://developer.apple.com/forums/thread/850709 I understand that this cleanup is different from an externally observable, time-bounded teardown guarantee. I am not asking again for a replacement application's handle to a VM whose owner has already died. The unresolved case is different: A host application owns a VM, but its serial VM-control queue is no longer progressing. A separate supervisor is intended to initiate the fallback stop action against that application. An external stop trigger occurs. The supervisor is then lost or stops progressing before it enters the signal operation; the VM-owning application remains alive. Loss of the supervisor role does not necessarily mean that its process has exited, so a process-exit notification cannot be assumed. Complete host or kernel failure is not part of this scenario. Is there a supported public mechanism that can be established before workload preparation and retain authority to act on the same target application after this loss, without requiring another action by the supervisor or progress on the VM-control queue? For any such mechanism, I would particularly appreciate clarification of: How its authority is bound to the intended target during incomplete setup, including process creation that has begun but has not returned a usable target identity. Assuming an already-running watchdog leaves this setup boundary unanswered. Which actor performs the remaining action when the supervisor cannot, and what lifecycle, privilege and progress assumptions that actor requires. Whether any documented progress bound applies when a required operation does not return. The design requirement is completion of the whole prescribed stop/escalation attempt, including required failure-handling steps, within 10 seconds of the same first external trigger. Starting a timer or entering a signal call is not equivalent to completing that attempt. This is not a request for unconditional successful process or VM termination. A supported narrower mechanism, or an explicit statement that macOS provides no such contract for this case, would also be useful. I am looking for public interfaces and their documented limits, not private helper-process identities or kernel implementation details. Thank you.
8
0
123
1d
StoreKit says purchase succeeded but didn't, AppStore.sync() throws error Unable to Complete Request
One user of my app reached out reporting an interesting in-app purchase issue. Has anyone encountered this or have an idea what's going on here? Proceed to purchase the non-consumable IAP in the app downloaded from the App Store iOS shows the price sheet as expected Confirm with the side button iOS shows an alert "You've already purchased this. Would you like to get it again for free?" Tap OK iOS shows an alert "You're all set. Your purchase was successful." Tap OK The app's content remains locked Tap Restore Purchases iOS shows an alert to sign (with the same account shown in step 2) Input the password and tap OK iOS shows an alert "Unable to Complete Request" (which is the error.localizedDescription thrown from AppStore.sync())
4
0
456
1d
All auto-renewable subscriptions returning expirationIntent = 5 after resolving an agreement issue (StoreKit 1 and StoreKit 2)
Hello, We are currently seeing errors when validating receipts for every auto-renewable subscription purchased through both StoreKit 1 and StoreKit 2. Details below. Case 1 — StoreKit 1 Calling https://buy.itunes.apple.com/verifyReceipt with the subscription receipt returns: "status": 21006, "expiration_intent": "5" Case 2 — StoreKit 2 Calling https://api.storekit.itunes.apple.com/inApps/v1/subscriptions and reading the most recent transaction (LastTransactionsItem) returns status 3. Within JWSRenewalInfoDecodedPayload: autoRenewStatus = 1, expirationIntent = 5 Timeline We believe renewals stopped processing for essentially all auto-renewing subscribers of our app as of 2026-09-18 09:30 KST (UTC+9). After resolving an agreement/licensing issue on our side, new purchases and some receipt validations recovered as of 2026-09-21 11:49 KST. However, most existing receipts still return expirationIntent = 5 when we query receipt validation or subscription status. Questions Is any action required on our side — a server-side change, a configuration change in App Store Connect, or a further review of our agreements? Now that the agreement issue is resolved, when are the renewals that were left pending during the outage expected to be processed? Any guidance would be appreciated. Thank you.
1
0
305
1d
Network Extension Issue - No cfil verdict callback registered - (27.3 beta 2)
I've filed FB25612343 in case others see it as well where 27.3b2 seems to cause issues with our network extension transparent proxy. The sysdiagnose shows the failure inside Network Extension, in the redirector process. Those lines (flow is closed for writes, Failed to write flow Data, No cfil verdict callback registered) are Apple's. There is no crash.Has anyone else seen issues on the latest beta?
6
0
131
1d
macOS: Can an XPC audit token prove that a peer belongs to a specific launchd job instance?
I'm designing a security-sensitive macOS service using a protected launchd daemon and a separate bootstrap supervisor. The daemon's executable and launchd plist are intended to be protected from modification by unprivileged users. The job uses a SpawnConstraint to restrict which signed executable launchd may start. During the initial XPC handshake, the supervisor must determine whether the sender is the current process launched by one specific launchd job, rather than another independently started process running the same signed executable. I understand that: Spawn constraints restrict the executable that launchd may start. XPC peer code-signing requirements can authenticate a sender's code identity. A valid signature, Team ID, audit token or PID alone does not necessarily establish the sender's originating launchd job or current launch instance. My question: Is there a supported public macOS API or documented mechanism that allows a receiver to verify that the sender of an XPC message belongs to a specific launchd job label and its current launch instance, with OS-backed evidence rather than application-supplied claims? If not, is this association intentionally unavailable through public APIs? What architecture does Apple recommend when the receiver must distinguish a launchd-managed daemon from another process running the same signed executable? I'm particularly interested in avoiding PID-reuse races and avoiding the disclosure of authorization material before the peer is authenticated. I'm looking for a supported design, not private APIs or undocumented launchctl behavior. Thank you.
6
0
113
1d
App stuck in "Waiting for Review" after resubmission + pending individual-to-organization conversion
Hi everyone, I'm hoping someone (or someone from Apple) can help or share their experience. My first iOS app was rejected under Guideline 2.3.6 for an Age Rating answer. I corrected the Age Rating as instructed, replied in App Store Connect, and resubmitted on 18 November. It has been in "Waiting for Review" since then. Everything on my side appears complete: Agreements, tax forms and banking are all Active App Compliance items are all Active App Privacy is published No new messages from App Review I have also requested to convert my developer account from Individual to Organization (I've received my D-U-N-S number), but haven't heard back from Membership support yet. A few questions: Can a pending Individual-to-Organization conversion hold up an app review? Is anyone else seeing longer than usual "Waiting for Review" times at the moment? How long did your account conversion take, and is there a faster way to reach Membership support? Any advice would be really appreciated. Thank you!
0
0
83
1d
App Store Server API mass renewal date extension remains incomplete for 11 days
Hello, I submitted a mass subscription renewal date extension request using the App Store Server API on September 9, 2026. The request was accepted successfully. However, when I check the request using getStatusOfSubscriptionRenewalDateExtensions, the status continues to return: complete: false As of September 20, the request has remained incomplete for 11 days. Request details: Extension: 1 day Reason: temporary service interruption Environment: Production The documentation states that a mass renewal date extension may take hours or even days to complete, but I have not been able to find guidance for a request that remains incomplete this long. Only three subscribers were affected by the service interruption, and I have their originalTransactionId values. I am considering using the individual subscription renewal date extension API instead. My questions are: Is it expected for a mass renewal date extension request to remain complete: false for 11 days? Could this mass request still complete at a later date? Is there any way to cancel or determine whether this mass request is stuck? If I extend the three affected subscriptions individually now, is there a risk that the pending mass request could later complete and extend them a second time? I would like to compensate the affected subscribers as soon as possible while avoiding duplicate extensions. Thank you for any guidance.
1
0
340
1d
TestFlight: StoreKit returns CHN/CNY but purchase sheet shows USD
I see different storefronts in StoreKit product queries and Apple’s purchase sheet when testing through TestFlight. Xcode-installed builds work normally. iPhone — iOS 26.6 (23G71), US Media & Purchases account Both StoreKit 1 and StoreKit 2 return CHN/CNY. The app displays CNY 128 for a non-consumable, but Apple’s sandbox purchase sheet shows USD 29.99 for the same product. This reproduces in a standalone 177-line Swift sample using Product.displayPrice directly, with no third-party dependencies, currency conversion, or local .storekit configuration. Reloading products and signing out of the sandbox account did not resolve it. Mac Catalyst — macOS 26.3 (25D125), China purchase account The original TestFlight app returns USA/USD. Purchasing shows “Account Not In This Store” and asks to switch to China, although the purchase account is already set to China. The Mac symptom has not yet been verified in the standalone sample. Reproduction on the affected iPhone: install via TestFlight, load products and log Storefront.current plus the SK1 storefront, open the purchase sheet for the same product, then compare currencies. No completed purchase is needed. Built with Xcode 26.1 (17B55). Has anyone found a workaround for this TestFlight-only mismatch? Should the app handle storefront updates differently, and which additional diagnostics would help distinguish a device/account-session issue from a StoreKit service issue? Feedback: FB24873070. A focused sample and diagnostic evidence are prepared for Apple Developer Technical Support. Reproduction on other devices/accounts is not yet confirmed.
1
0
306
1d
New features for APNs token authentication now available
Team-scoped keys introduce the ability to restrict your token authentication keys to either development or production environments. Topic-specific keys in addition to environment isolation allow you to associate each key with a specific Bundle ID streamlining key management. For detailed instructions on accessing these features, read our updated documentation on establishing a token-based connection to APNs.
Replies
0
Boosts
0
Views
4.3k
Activity
Feb ’25
Meet State Reporting and the new MetricKit
Hello developers! Thank you for your dedication to creating apps with great performance. We’re excited to kick off another year of partnering with you on improving power and performance in your apps. At WWDC26, check out the following new things in the latest platform SDKs and Xcode 27 beta for performance. You can also join us online for a Power and Performance Group Lab on Tuesday, June 9 at 11 AM Pacific. Meet State Reporting and the new MetricKit State reporting: The new StateReporting framework lets your application express its state to downstream tools like Instruments and MetricKit. Make your telemetry and traces much more useful by adopting this simple API. MetricKit: In the 27 releases, the Swift-first MetricManager API replaces the MXMetricManager API. Combined with State Reporting, the new MetricKit provides more granular metrics to isolate performance problems faster. It also provides a more expressive API that is great to use in Swift, with improved Swift concurrency and Codable support. With this year’s releases, the MXMetricManager API is considered legacy. ▶️ To learn more, watch Meet the new MetricKit. Discover new features in Xcode organizer Metric goals: Xcode organizer now provides a goal metric for Battery Usage, Disk Writes, Hang Rate, Hitches, Memory, and Storage metrics, allowing you to prioritize performance engineering across more areas. Generate recommendations: Quickly resolve the highest impact performance issues in your app by using Generate Recommendations for Crash, Energy, Disk Write, Hang and Launch diagnostics. Insights overview: The new insights overview in Xcode organizer summarizes high-impact performance regressions for metrics and diagnostic reports, helping you plan and prioritize performance engineering work. Storage metrics: Storage metrics are now available in Xcode organizer, allowing you to monitor your app's Documents & Data and App Size across releases and catch regressions in cache usage and bundle size. Hitches metric: The new Hitches metric replaces the Scrolling metric in the organizer and now displays hitches for all animations in your app, giving you a comprehensive view of animation performance. ▶️ To learn more about other advancements in Xcode, watch What’s new in Xcode 27. Improve app responsiveness with Instruments Foundation Models: The Foundation Models instrument is redesigned with a tree view that lets you drill into individual requests, inspecting tool call arguments and results, inference prompts and responses, and token statistics. Use it to understand caching behavior, measure latency, and optimize throughput. System Trace: System calls, VM faults, and thread states are now unified into a single plot, with a new blending algorithm that stays readable even at high density. Once you spot something worth investigating, left/right key navigation lets you follow a thread's activity step by step, and the inspector provides quick actions like pinning the thread that made another thread runnable. System Trace now also draws thread priority and QoS over time, making it easier to identify priority inversions and unexpected QoS degradations that affect responsiveness. Swift Concurrency: New Main Actor and Global Concurrent Executor tracks let you visualize running tasks and executor queue depth over time, making it easier to spot task scheduling delays and actor contention. Tasks are now grouped into collections for faster navigation. Swift Tasks, Actors, and Executors instruments can now surface Call Trees, Flame Graphs, and Top Functions scoped to each entity — so you can pinpoint exactly where concurrency overhead lives. Top Functions: Helper functions and runtime internals can be expensive but hard to spot in a standard call tree. The new aggregation mode in Top Functions surfaces any function's total execution time across the entire call stack, making it easy to identify and prioritize hidden hotspots. Run Comparison: Compare call tree data across builds to identify regressions and performance wins. Results can be explored as an outline, flame graph, or top functions — choose whichever view best fits your workflow. ▶️ To learn more about profiling your app with Instruments, watch “Profile, fix, and verify: Improve app responsiveness with Instruments” ▶️ To learn about Foundation Models optimization, watch “Debug and profile agentic app experiences with Instruments”. If you have any questions about using State Reporting or the new MetricKit, create a post on the forums. For help creating a post, see Tips on writing a forum posts.
Replies
0
Boosts
0
Views
1.9k
Activity
Jun ’26
MKMapItem addressRepresentations fullAddress singleLine does not always work and provides the address in multiline
Hello, I’m trying to display in my app the full address of an MKMapItem in a single line. I notice the following function does not always return single line but contains newlines. https://developer.apple.com/documentation/mapkit/mkaddressrepresentations/fulladdress(includingregion:singleline:) I provide the list of some identifiers so you can check what’s wrong. "I39866265D4A8562A", // 🟢 works "IF233A1E949A5566C", // 🟢 works "ICA31B6B98E02A528", // 🔴 does not work "ICA31B6B98E02A528", // 🔴 does not work "I9E00A04BFCB9718D", // 🔴 does not work "IFACDC4BC25712413", // 🔴 does not work "I74135A4F7C7FE654", // 🔴 does not work "IFE4A3BC4FEFA53E0", // 🔴 does not work You can check this FB25681688 Thank you, Regards, Axel
Replies
0
Boosts
0
Views
4
Activity
38m
StoreKit 2 returns USA storefront and USD price in TestFlight despite Japanese Apple Account
Hello, I'm developing an iOS app that uses StoreKit 2 for an auto-renewable subscription. I'm experiencing an issue where StoreKit returns the US storefront and USD pricing in TestFlight, even though the device's Apple Account and Sandbox Apple Account are configured for Japan. Environment App: YonsanmaruTimer (430タイマー) App version: 1.2.0 (TestFlight build 4) Bundle ID: com.manyouen.YonsanmaruTimer Product ID: com.manyouen.YonsanmaruTimer.plusassist.monthly StoreKit 2 Xcode Archive configuration: Release App Store Connect configuration The subscription is configured with the following prices: Japan: ¥200/month, with a one-month free trial United States: $0.99/month The app is intended for distribution in Japan. Observed behavior When fetching the subscription product using Product.products(for:), I log the current storefront and product price. The result is: Storefront: USA Price: $0.99 Currency: USDAs a result, the subscription price displayed in the app using product.displayPrice is $0.99 instead of ¥200. What I have already checked The device's Apple Account country/region for Media & Purchases is Japan. TestFlight is installed using my regular Japanese Apple Account. I created a new Sandbox Apple Account with Japan as its country/region and signed in through Settings → Developer → Sandbox Apple Account. The storefront still returns USA after restarting the TestFlight app. The app is archived using the Release build configuration. In an earlier subscription purchase test, Apple's native purchase confirmation sheet displayed ¥200, even though the app's product display price was $0.99. Questions Why would Storefront.current return USA in TestFlight under these conditions? Is this expected behavior in the TestFlight sandbox environment? Could this behavior also occur after the app is released on the App Store? Is there any additional account, device, or App Store Connect configuration I should check? I would like to ensure that the subscription price displayed in my app matches the price shown in Apple's purchase confirmation sheet before submitting the app for review. Any guidance would be greatly appreciated. Thank you.
Replies
0
Boosts
0
Views
69
Activity
11h
Sandbox IAP: AuthKit succeeds, then AMSServerErrorDomain -5000 (cancel-purchase-batch)
Every sandbox purchase of our auto-renewable subscriptions cancels right after AuthKit sign-in succeeds. It's blocking our 1.0 release. Filed as FB25469063, no reply yet. Capacitor iOS app, bundle io.xrplive.app, 1.0.0 (TestFlight), products io.xrplive.app.pro.monthly / .yearly, iPhone 17 Pro Max on iOS 27.0.1, StoreKit via @capgo/native-purchases. Console on every attempt: (1) AMSAuthKitUpdateTask: "The AuthKit authentication succeeded." (2) Then: Error Domain=AMSServerErrorDomain Code=-5000 UserInfo={failureType=-5000, m-allowed=false, cancel-purchase-batch=true, customerMessage=Check the account information you entered and try again.} Also AMSErrorDomain Code=100 (Authentication Failed), Code=2 ("Password reuse not available for account"), and a 401 from sandbox.itunes.apple.com/commerce/messages/app/inbox. We already fixed a purchase(confirmIn:) presentation issue. This failure is in sandbox verification after a successful sign-in, which we can't fix from the client. Is -5000 with cancel-purchase-batch a known sandbox account or commerce issue? Is there a sandbox tester or storefront state that fixes it when AuthKit succeeds but verification still fails?
Replies
1
Boosts
0
Views
67
Activity
11h
Virtualization.framework — stop completion and storage release
Hello Apple Developer Support, We are evaluating a macOS VM controller using VZVirtualMachine and would appreciate clarification: Does stop(completionHandler:) have any documented maximum completion time? What should a controller do if completion never arrives? After successful completion, are all backend writes finished and disk-image resources released, or is additional teardown required? What documented sequence establishes that the VM’s complete writable storage set—including disk images and macOS auxiliary storage—can safely be deleted, replaced or restored? Do these guarantees depend on caching/synchronization mode or macOS version? We understand that forced stop does not guarantee a clean guest shutdown or application consistency. Our question concerns host-side storage quiescence and resource release. Documentation references would be helpful. Thank you.
Replies
0
Boosts
0
Views
84
Activity
16h
Driver approval pending
Hi team, It has been nearly a month since we submitted our driver approval request (3DRN3G5AMB), and it is currently still pending. This prolonged delay is severely impacting our operations, and as there is no self-service option for us to expedite this on our end, we urgently need your assistance to move this forward. Could you please check the status of this request with the relevant team and let us know what is causing the hold-up, or how we can escalate it? Thank you for your prompt help with this
Replies
1
Boosts
0
Views
59
Activity
17h
What is actually needed for a HID device to be picked up as a GCController?
I am trying to interface with a custom USB Device that uses a CAN bus for communication and turn it in to a game controller that the GameController Framework recognizes. I have it creating a Virtual HID device just fine and applications that read the HID information directly read the state just fine. But the ones that are using the GameController framework are saying there are no game controllers found. If the HID device descriptor saying it's a Joystick or GamePad is not enough, what else is needed?
Replies
0
Boosts
0
Views
76
Activity
1d
How should a macOS app determine when to call requestAgeRange for California users?
Apple documents that AgeRangeService.isEligibleForAgeFeatures returns false on macOS, while requestAgeRange can still return a declared age range on supported Macs. What Apple-provided signal, if any, should a native AppKit app check before calling requestAgeRange to determine whether a California age-bracket request applies? Is requiredRegulatoryFeatures intended for this case? Does the answer differ for an iPad app running on an Apple silicon Mac? For existing installations on macOS 15, is there a supported App Store mechanism to obtain the signal when the OS framework is unavailable? A pointer to the relevant API documentation, minimum OS versions, or a macOS sample would help.
Replies
0
Boosts
0
Views
84
Activity
1d
Updating an FSKit module to use the new Handler protocols
I have a file system extension that currently uses the various now-deprecated Operations protocols. I have a few questions about moving to the new Handler protocols. First, my module is going to maintain backwards compatibility with macOS Sequoia for the foreseeable future, but I would also like to be able to take advantage of new FSKit features for users who are on newer OS versions. What approach would you recommend: Having an FSVolume conform to both the various Operations and Handler protocols (e.g. both FSVolumeKernelOffloadedIOOperations and FSVolume.KernelOffloadedIOHandler with the latter tagged with @available) an immediate issue I see trying to do this is I run into the error Method 'activate(options:)' with Objective-C selector 'activateWithOptions:replyHandler:' conflicts with previous declaration with the same Objective-C selector when trying to conform to both FSVolume.Handler and FSVolume.Operations. Having two separate FSVolume implementations, one used for older OS versions with Operations support and one used on newer OS versions with Handler support? Keeping the use of pre-existing Operations protocols while only using the Handlers for newer features (e.g. things like SeekRegionHandler) Second, I see at https://developer.apple.com/documentation/fskit/fsvolumehandlerresult/requestedattributes that I must populate all requested attributes. Does this value only have a meaning if the initializer for the actual concrete result type has an initializer that takes in a FSItem.Attributes instance, or is there some way I’m supposed to populate those? (As a concrete example, FSCheckAccessResult has init(accessAllowed:) which doesn’t take in any attributes.)
Replies
6
Boosts
0
Views
966
Activity
1d
Enrollment in dev program stuck
Case ID: 30000008563290, submitted Nov 7. I am unable to enroll in the Apple Developer program. I get a message stating "Unable to enroll at this time". I have a submitted a couple of email follow-ups and have not received a response. I am able to provide identification documents if necessary. I had a phone call and the support team member was unable to help - She said she couldn't see why it was blocked, and that she would escalate to a supervisor. I am hoping someone from the Apple support team can take a look and help me enroll. I have attempted both web enrollment and enrolling via iphone developer app. Thanks in advance.
Replies
1
Boosts
0
Views
84
Activity
1d
"IOSurface creation failed" drawing to CGContext
(more details on StackOverflow) I'm getting messages like the following, SOMETIMES, when I draw to a CGContext IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5207703552; IOSurfaceAllocSize = 9461418; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } call to context.draw(): context.draw(photo.image, in: CGRect(x: 0, y: top, width: width, height: height), byTiling: false) The results are just fine, so the draw seems to be working. It also, most often, draws without producing this error, but it fails pretty often. I'm not sure where to begin looking to sort out what I might need to do differently to avoid this error message in the console. Complete code: import Foundation import SwiftUI func generateSpritesImage(thumbPhotos: [Photo], width: Int, filename: URL) -> [Int] { var indices = [Int]() let totalHeight = thumbPhotos.reduce(0) { $0 + $1.heightOfImage(ofWidth: width) } debugPrint("creating context") let context = CGContext(data: nil, width: width, height: totalHeight, bitsPerComponent: 8, bytesPerRow: 0, space: CGColorSpace(name: CGColorSpace.sRGB)!, bitmapInfo: CGImageAlphaInfo.noneSkipLast.rawValue)! var top = totalHeight for photo in thumbPhotos { let height = photo.heightOfImage(ofWidth: width) indices.append(top - totalHeight) top -= height debugPrint("drawing \(photo.filteredFileURL())") context.draw(photo.image, in: CGRect(x: 0, y: top, width: width, height: height), byTiling: false) } debugPrint("write jpeg") writeJpegFromContext(context: context, filename: filename) return indices } func writeJpegFromContext(context: CGContext, filename: URL) { let cgImage = context.makeImage()! let bitmapRep = NSBitmapImageRep(cgImage: cgImage) let jpegData = bitmapRep.representation(using: NSBitmapImageRep.FileType.jpeg, properties: [:])! try! jpegData.write(to: filename) } sample of output: "drawing 0002-_MG_8542.jpg" "drawing 0003-_MG_8545.jpg" "drawing 0004-_MG_8550.jpg" IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5211357184; IOSurfaceAllocSize = 9983331; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } "drawing 0005-_MG_8555.jpg" IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5221351424; IOSurfaceAllocSize = 10041215; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } "drawing 0006-_MG_8562.jpg" "drawing 0007-_MG_8563.jpg" IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5376163840; IOSurfaceAllocSize = 10109756; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } "drawing 0008-_MG_8584.jpg" "drawing 0009-_MG_8618.jpg" IOSurface creation failed: e00002c2 parentID: 00000000 properties: { IOSurfaceAddress = 5394612224; IOSurfaceAllocSize = 8425564; IOSurfaceCacheMode = 0; IOSurfaceName = CMPhoto; IOSurfacePixelFormat = 1246774599; } "drawing 0010-_MG_8627.jpg" "drawing 0011-_MG_8649.jpg" "drawing 0012-_MG_8658.jpg" "drawing 0013-_MG_8665.jpg" "drawing 0014-_MG_8677.jpg" "drawing 0015-_MG_8675.jpg" "drawing 0016-_MG_8676.jpg" "drawing 0017-IMGP0873.jpg" "drawing 0018-_MG_8719.jpg" "drawing 0019-_MG_8743.jpg" ...
Replies
4
Boosts
1
Views
2.8k
Activity
1d
macOS: pre-established stop mechanism when a VM supervisor stops progressing
I am evaluating a bounded workload host using Virtualization.framework on Apple silicon. This is a question about supported architecture and API contracts, not a report of a reproduced bug. No particular macOS release has yet been qualified for this design; please identify the releases and prerequisites to which an answer applies. I have read the discussions about cleanup after the VM-owning application terminates: https://developer.apple.com/forums/thread/848542 https://developer.apple.com/forums/thread/850709 I understand that this cleanup is different from an externally observable, time-bounded teardown guarantee. I am not asking again for a replacement application's handle to a VM whose owner has already died. The unresolved case is different: A host application owns a VM, but its serial VM-control queue is no longer progressing. A separate supervisor is intended to initiate the fallback stop action against that application. An external stop trigger occurs. The supervisor is then lost or stops progressing before it enters the signal operation; the VM-owning application remains alive. Loss of the supervisor role does not necessarily mean that its process has exited, so a process-exit notification cannot be assumed. Complete host or kernel failure is not part of this scenario. Is there a supported public mechanism that can be established before workload preparation and retain authority to act on the same target application after this loss, without requiring another action by the supervisor or progress on the VM-control queue? For any such mechanism, I would particularly appreciate clarification of: How its authority is bound to the intended target during incomplete setup, including process creation that has begun but has not returned a usable target identity. Assuming an already-running watchdog leaves this setup boundary unanswered. Which actor performs the remaining action when the supervisor cannot, and what lifecycle, privilege and progress assumptions that actor requires. Whether any documented progress bound applies when a required operation does not return. The design requirement is completion of the whole prescribed stop/escalation attempt, including required failure-handling steps, within 10 seconds of the same first external trigger. Starting a timer or entering a signal call is not equivalent to completing that attempt. This is not a request for unconditional successful process or VM termination. A supported narrower mechanism, or an explicit statement that macOS provides no such contract for this case, would also be useful. I am looking for public interfaces and their documented limits, not private helper-process identities or kernel implementation details. Thank you.
Replies
8
Boosts
0
Views
123
Activity
1d
StoreKit says purchase succeeded but didn't, AppStore.sync() throws error Unable to Complete Request
One user of my app reached out reporting an interesting in-app purchase issue. Has anyone encountered this or have an idea what's going on here? Proceed to purchase the non-consumable IAP in the app downloaded from the App Store iOS shows the price sheet as expected Confirm with the side button iOS shows an alert "You've already purchased this. Would you like to get it again for free?" Tap OK iOS shows an alert "You're all set. Your purchase was successful." Tap OK The app's content remains locked Tap Restore Purchases iOS shows an alert to sign (with the same account shown in step 2) Input the password and tap OK iOS shows an alert "Unable to Complete Request" (which is the error.localizedDescription thrown from AppStore.sync())
Replies
4
Boosts
0
Views
456
Activity
1d
All auto-renewable subscriptions returning expirationIntent = 5 after resolving an agreement issue (StoreKit 1 and StoreKit 2)
Hello, We are currently seeing errors when validating receipts for every auto-renewable subscription purchased through both StoreKit 1 and StoreKit 2. Details below. Case 1 — StoreKit 1 Calling https://buy.itunes.apple.com/verifyReceipt with the subscription receipt returns: "status": 21006, "expiration_intent": "5" Case 2 — StoreKit 2 Calling https://api.storekit.itunes.apple.com/inApps/v1/subscriptions and reading the most recent transaction (LastTransactionsItem) returns status 3. Within JWSRenewalInfoDecodedPayload: autoRenewStatus = 1, expirationIntent = 5 Timeline We believe renewals stopped processing for essentially all auto-renewing subscribers of our app as of 2026-09-18 09:30 KST (UTC+9). After resolving an agreement/licensing issue on our side, new purchases and some receipt validations recovered as of 2026-09-21 11:49 KST. However, most existing receipts still return expirationIntent = 5 when we query receipt validation or subscription status. Questions Is any action required on our side — a server-side change, a configuration change in App Store Connect, or a further review of our agreements? Now that the agreement issue is resolved, when are the renewals that were left pending during the outage expected to be processed? Any guidance would be appreciated. Thank you.
Replies
1
Boosts
0
Views
305
Activity
1d
Network Extension Issue - No cfil verdict callback registered - (27.3 beta 2)
I've filed FB25612343 in case others see it as well where 27.3b2 seems to cause issues with our network extension transparent proxy. The sysdiagnose shows the failure inside Network Extension, in the redirector process. Those lines (flow is closed for writes, Failed to write flow Data, No cfil verdict callback registered) are Apple's. There is no crash.Has anyone else seen issues on the latest beta?
Replies
6
Boosts
0
Views
131
Activity
1d
macOS: Can an XPC audit token prove that a peer belongs to a specific launchd job instance?
I'm designing a security-sensitive macOS service using a protected launchd daemon and a separate bootstrap supervisor. The daemon's executable and launchd plist are intended to be protected from modification by unprivileged users. The job uses a SpawnConstraint to restrict which signed executable launchd may start. During the initial XPC handshake, the supervisor must determine whether the sender is the current process launched by one specific launchd job, rather than another independently started process running the same signed executable. I understand that: Spawn constraints restrict the executable that launchd may start. XPC peer code-signing requirements can authenticate a sender's code identity. A valid signature, Team ID, audit token or PID alone does not necessarily establish the sender's originating launchd job or current launch instance. My question: Is there a supported public macOS API or documented mechanism that allows a receiver to verify that the sender of an XPC message belongs to a specific launchd job label and its current launch instance, with OS-backed evidence rather than application-supplied claims? If not, is this association intentionally unavailable through public APIs? What architecture does Apple recommend when the receiver must distinguish a launchd-managed daemon from another process running the same signed executable? I'm particularly interested in avoiding PID-reuse races and avoiding the disclosure of authorization material before the peer is authenticated. I'm looking for a supported design, not private APIs or undocumented launchctl behavior. Thank you.
Replies
6
Boosts
0
Views
113
Activity
1d
App stuck in "Waiting for Review" after resubmission + pending individual-to-organization conversion
Hi everyone, I'm hoping someone (or someone from Apple) can help or share their experience. My first iOS app was rejected under Guideline 2.3.6 for an Age Rating answer. I corrected the Age Rating as instructed, replied in App Store Connect, and resubmitted on 18 November. It has been in "Waiting for Review" since then. Everything on my side appears complete: Agreements, tax forms and banking are all Active App Compliance items are all Active App Privacy is published No new messages from App Review I have also requested to convert my developer account from Individual to Organization (I've received my D-U-N-S number), but haven't heard back from Membership support yet. A few questions: Can a pending Individual-to-Organization conversion hold up an app review? Is anyone else seeing longer than usual "Waiting for Review" times at the moment? How long did your account conversion take, and is there a faster way to reach Membership support? Any advice would be really appreciated. Thank you!
Replies
0
Boosts
0
Views
83
Activity
1d
App Store Server API mass renewal date extension remains incomplete for 11 days
Hello, I submitted a mass subscription renewal date extension request using the App Store Server API on September 9, 2026. The request was accepted successfully. However, when I check the request using getStatusOfSubscriptionRenewalDateExtensions, the status continues to return: complete: false As of September 20, the request has remained incomplete for 11 days. Request details: Extension: 1 day Reason: temporary service interruption Environment: Production The documentation states that a mass renewal date extension may take hours or even days to complete, but I have not been able to find guidance for a request that remains incomplete this long. Only three subscribers were affected by the service interruption, and I have their originalTransactionId values. I am considering using the individual subscription renewal date extension API instead. My questions are: Is it expected for a mass renewal date extension request to remain complete: false for 11 days? Could this mass request still complete at a later date? Is there any way to cancel or determine whether this mass request is stuck? If I extend the three affected subscriptions individually now, is there a risk that the pending mass request could later complete and extend them a second time? I would like to compensate the affected subscribers as soon as possible while avoiding duplicate extensions. Thank you for any guidance.
Replies
1
Boosts
0
Views
340
Activity
1d
TestFlight: StoreKit returns CHN/CNY but purchase sheet shows USD
I see different storefronts in StoreKit product queries and Apple’s purchase sheet when testing through TestFlight. Xcode-installed builds work normally. iPhone — iOS 26.6 (23G71), US Media & Purchases account Both StoreKit 1 and StoreKit 2 return CHN/CNY. The app displays CNY 128 for a non-consumable, but Apple’s sandbox purchase sheet shows USD 29.99 for the same product. This reproduces in a standalone 177-line Swift sample using Product.displayPrice directly, with no third-party dependencies, currency conversion, or local .storekit configuration. Reloading products and signing out of the sandbox account did not resolve it. Mac Catalyst — macOS 26.3 (25D125), China purchase account The original TestFlight app returns USA/USD. Purchasing shows “Account Not In This Store” and asks to switch to China, although the purchase account is already set to China. The Mac symptom has not yet been verified in the standalone sample. Reproduction on the affected iPhone: install via TestFlight, load products and log Storefront.current plus the SK1 storefront, open the purchase sheet for the same product, then compare currencies. No completed purchase is needed. Built with Xcode 26.1 (17B55). Has anyone found a workaround for this TestFlight-only mismatch? Should the app handle storefront updates differently, and which additional diagnostics would help distinguish a device/account-session issue from a StoreKit service issue? Feedback: FB24873070. A focused sample and diagnostic evidence are prepared for Apple Developer Technical Support. Reproduction on other devices/accounts is not yet confirmed.
Replies
1
Boosts
0
Views
306
Activity
1d