Overview

Hello I am looking at taking advantage of managing some features via DDM in an app. I noticed in the ServicesConfigurationFiles link (https://developer.apple.com/documentation/devicemanagement/servicesconfigurationfiles) it says You can create an executable that uses service configuration files by calling the mcf_service_path_for_service_type method in the libmanagedconfigurationfiles.dylib system library. You pass in an identifier for your service type and the method returns the file system path for the directory that contains the corresponding service configuration files. Use those files to override the standard or default configuration the executable would otherwise use. See libmanagedconfigurationfiles.h in the macOS SDK for more detail. I can't find any more references or information on mcf_service_path_for_service_type, libmanagedconfigurationfiles.dylib or libmanagedconfigurationfiles.h anywhere. Is there any information somewhere about this? Or how to use it? Or a POC small example?

I typically avoid NSMetadataQuery because I always found the API to be a bit peculiar but for this feature I'm working on I'm not sure it is worth the effort to implement this functionality in my own way. Plus it seems pretty fast. What I find strange is I set the operationQueue to get notifications off the main thread. But also when I set the queue the system yells at me anytime I make a change to NSMetadataQuery that alters the query. So I found this recommendation (requirement) in the documentation : NSMetadataQuery *query = // Initialize and set up a query [query.operationQueue addOperationWithBlock:^{ [query startQuery]; }]; I find this API design to be odd, but maybe I'm just weird. So there are a bunch of properties that can be changed while the query is already running (predicate etc.) and they implicitly stop/start the query and it seems all these calls need to be routed through the query.operationQueue like above? For example if I change the predicate while the query is already started it seems I have to: [query.operationQueue addOperationWithBlock:^{ query.predicate = predicate; }]; The query already knows its operationQueue. Why does the caller have to plumb these calls through the operation queue manually? -stopQuery does not result in an error/warning when called off the operationQueue but is doing so safe? Or do I have to do: [query.operationQueue addOperationWithBlock:^{ [query stopQuery]; }]; Really what I was expecting was to provide a queue for the notification callbacks. I wasn't expecting to manually have to confine the query to its own queue.

Hello. I have developed an application (My Pickleball) with Xcode for both iPhone and Apple Watch. I have successfully loaded said application onto my iPhone by connecting my iPhone to my MacBook Air with a cable; the application works as intended. The issue is with my Apple Watch. The application does load onto my Apple Watch, when when I select it, I get the following error: "Unable to Install 'My Pickleball - Watch' This app cannot be installed because its integrity could not be verified." Are there any thoughts as to how I could fix this? Thank you in advance. Regards, Ezequiel

Hello apple, its highly unfair that my development processed paused because I decided to migrate my account and I havent received an update concerning it.if I am missing a document or got something wrong's it not better to let me know than keep me waiting for something that takes few hours to few days.please I beg you to approve or reject my migration so I can deploy my app.

Hello, I submitted my Apple Developer Program enrollment as an organization in March 2026 and have not received any follow-up communication since the initial confirmation email. Enrollment Details: Enrollment ID: TSGVDQWT8A Enrollment Type: Organization (Company/LLC) Legal Entity: BattManager, LLC Region: United States 2FA: Enabled on Apple ID Business domain email used The initial confirmation email stated that Apple would verify my authority to bind the organization to the Apple Developer Program legal agreements, and that I would receive follow-up instructions. It has now been over two months with no additional emails, no requests for documentation, and no status change in the portal beyond "Your enrollment is being processed." I have not received any phone calls or requests for identity verification. Could an Apple team member please review enrollment TSGVDQWT8A and advise on what is needed to move this forward? I am happy to provide any additional documentation or verification required. Thank you.

I am interested in managing some configuration files for an app using Declarative Device Management (DDM) and noticed a blurb on the ServicesConfigurationFiles developer page that makes it seem like 3rd party apps can take advantage of DDM service files. But I'm not exactly sure how https://developer.apple.com/documentation/devicemanagement/servicesconfigurationfiles You can create an executable that uses service configuration files by calling the mcf_service_path_for_service_type method in the libmanagedconfigurationfiles.dylib system library. You pass in an identifier for your service type and the method returns the file system path for the directory that contains the corresponding service configuration files. Use those files to override the standard or default configuration the executable would otherwise use. See libmanagedconfigurationfiles.h in the macOS SDK for more detail I can't find any more details in the developer documentation on this. How would this be used? Could someone give an example or small POC?

I am testing a StoreKit 2 non-consumable IAP through TestFlight. Product ID: com.metabolla.plus.lifetime Type: Non-Consumable Environment: TestFlight / Sandbox Transaction.currentEntitlements keeps returning an active entitlement for this product even after: configuring a Sandbox Apple Account clearing Sandbox Purchase History reinstalling the app rebooting the device Important detail: the first TestFlight purchase was completed before configuring the Sandbox Apple Account on the device. If I temporarily change the Product ID in code, the entitlement disappears, so the issue seems tied to the original Product ID/account/receipt. Question: Can a non-consumable TestFlight purchase made before Sandbox Apple Account configuration remain associated with the original TestFlight/Apple ID identity? Is there any supported way to clear this entitlement for testing?

Hi all, has anyone experienced an issue where App Store Connect shows the app as In Review and doesn't allow you to release it to production, but under General → App Review the review appears to be completed and the status is Approved? (attached screenshots) It's been in this state for more than 3 days already. Has anyone encountered this before or knows how to resolve it? Any advice would be appreciated. I've contacted support already but no response

ENVIRONMENT Device : MacBook Pro 16,1 CPU : 6-Core Intel Core i7, 2.6 GHz RAM : 16 GB DDR4 GPU : AMD Radeon Pro 5300M + Intel UHD 630 macOS : 26.5 (Build: 25F71) Xcode : 26 (also tried Xcode 16 — same issue) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ISSUE SUMMARY Xcode crashes immediately on launch after updating to macOS 26.5. The issue started right after the macOS update — Xcode was working perfectly before. Both Xcode 26 and Xcode 16 are affected. Fresh reinstall does not help. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ERROR — xcodebuild -version output dyld: Library not loaded: @rpath/DVTSystemPrerequisites.framework/ Versions/A/DVTSystemPrerequisites Reason: code signature in DVTSystemPrerequisites.framework not valid for use in process — mapping process is a platform binary, but mapped file is not. zsh: abort xcodebuild -version ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ CRASH REPORT DETAILS Incident ID : 370D1162-4CA5-4FFE-9193-45EBD350BF85 Exception : EXC_BAD_ACCESS (SIGKILL — Code Signature Invalid) Termination : CODESIGNING, Code 2, Invalid Page Crash Date : 2026-05-14 Failing Frameworks: DVTSystemPrerequisites.framework MobileDevice.framework (/Library/Apple/System/Library/ PrivateFrameworks/MobileDevice.framework) Crashed Thread 7 Stack: dyld3::MachOFile::trieWalk dyld4::Loader::hasExportedSymbol dyld4::JustInTimeLoader::applyFixups _CFBundleLoadExecutableAndReturnError -[NSBundle loadAndReturnError:] __watchForSims_block_invoke -[OSActivityStream setDeviceDelegate:] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ WHAT I HAVE ALREADY TRIED sudo xattr -cr /Applications/Xcode.app sudo codesign --force --deep --sign - /Applications/Xcode.app sudo codesign --force --deep --preserve-metadata=identifier,entitlements --sign - /Applications/Xcode.app Re-signed DVTSystemPrerequisites.framework individually Deleted DerivedData, Xcode caches, preferences Fresh reinstall of Xcode (multiple times) Tried installing Xcode 16 — same crash Raised Apple Support Ticket: 102889658162 — no resolution received Nothing has worked. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ROOT CAUSE ANALYSIS macOS 26.5 introduced stricter platform binary validation in dyld. On Intel Mac (x86_64), this validation is rejecting Xcode's own frameworks at runtime — even after re-signing. This does not appear to be a user-fixable issue. This seems to be a macOS 26.5 regression specifically affecting Intel Mac users. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ REQUEST Is anyone else experiencing this on Intel Mac? Has anyone found a working workaround? Can Apple Engineering please investigate this as a macOS 26.5 regression for Intel Macs? My entire development workflow is blocked. Any help is greatly appreciated. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

My app has now been in “Waiting for Review” for 9 days. Because this app is a cryptocurrency wallet tied to a scheduled product launch, the delay is having a direct impact on our launch timeline, business operations, and user onboarding. We are fully prepared to assist the App Review team in any way needed and can promptly provide test accounts, additional documentation, feature explanations, compliance materials, or any other information that would help move the review forward. Request I respectfully request an update on the current status of this submission and would appreciate confirmation as to whether there are any outstanding questions or issues preventing the app from progressing through review. If anything further is needed from our side, we are ready to provide it immediately. Thank you for your time and assistance. We appreciate your help in moving this submission forward as soon as possible. App details - Apple ID: 6764380281

Hello App Review Team, Our app update has been stuck in "Waiting for Review" with no movement and no communication, and I would appreciate a manual look or escalation. App: Telegraff: call, send, receive Apple ID: 1606970462 Version: 11.6.0 Submitted: May 14 Current live version: 11.5.10 (Ready for Distribution) This is an update to an app that is already live on the App Store, not a new submission. The previous versions (11.5.9 and 11.5.10) passed review normally in March. Context I want to share proactively: we are in the middle of an official rebranding of our application — the name, branding, and positioning are being updated as part of this change. All of it is our own brand and our own product; it is not affiliated with or imitating any other company, and we hold the rights to the branding we use. We are happy to provide ownership documentation or any clarification the review team needs. The same update has already passed moderation and is live on Google Play, so our iOS and Android releases are now out of sync and we cannot ship updates to our existing iOS users, which is seriously affecting our business. What I have already tried, without result: Expedited review requests submitted several times — no effect. Multiple emails to Apple Developer Support — only automated acknowledgements, no substantive reply. Case IDs: 102902702809, 102900916785, 102894706008. The Resolution Center is unavailable because the status is still "Waiting for Review," so I cannot reach the review team directly from there. Could someone please look into whether there is an account-level or pipeline issue blocking this submission, or escalate it manually? If there is a specific concern (branding, metadata, content, or account), I will address it immediately — I just need concrete feedback instead of silence. Thank you for your help.

I'm the Account Holder and I've been stuck for over a month. In App Store Connect → Business → Paid Applications Agreement, I tick "I have read and agree" and click Agree — the page just reloads, no confirmation, status never goes Active. Because of that, my app gets rejected and my In-App Purchases are returned. In the Network tab, the submit request comes back 401 Unauthorized. Already tried (no effect): Signing from both the Business tab and the Agreements page Safari, Chrome, Firefox — private windows, no extensions, no VPN, cookies/cache cleared Re-saved my legal address; Tax and Banking sections are complete Confirmed I'm the Account Holder Developer Support hasn't resolved it. Has anyone hit this exact 401 on agreement signing — and what actually fixed it? A backend reset from Apple, some account/role detail, or did it just clear on its own after a while?

Hello, I started an Apple Developer Program enrollment, but I accidentally entered the wrong name during the process. The enrollment was not completed yet. I would like to know what is the correct way to reset, cancel, or restart the enrollment so I can submit it again with my correct legal name. I already contacted Apple Developer Support, but I have not been able to resolve the issue yet. I would appreciate any guidance on the proper next step. Thank you.

Hello, We are currently investigating an issue where our app is being terminated by the system while running in the background. At the moment, the app does not perform any significant background activity, and memory usage remains relatively low (approximately 150–200 MB). Despite this, the app is still being terminated in the background, even under conditions where other apps appear to remain active. From our investigation so far, the issue does not appear to be related to: High memory consumption Explicit background task misuse Application crashes on our side For additional context, we had previously used silent push notifications to trigger heavy upload operations in the background. Since we suspected this behavior might be contributing to the issue, we completely stopped using this mechanism approximately two weeks ago. However, the background terminations are still occurring. We would like to better understand the possible causes of this behavior. Specifically, could this be related to: Watchdog terminations Background assertion or lifecycle violations RunningBoard resource management Jetsam policies Background execution timeouts Any other system-level resource or process management constraints We would greatly appreciate any guidance on how to identify the root cause or which logs/diagnostics we should focus on to further investigate the issue. Thank you.

To the App Review and Developer Support Teams, I am writing this post to bring an ongoing issue to your attention, as standard support channels have failed to provide any resolution or clear communication. Issue Summary: We are introducing consumable IAPs (coin packs) for the first time in Ice Scream 1 and Ice Scream 2. Both apps have been reviewed and approved, however their associated IAPs remain blocked. Despite multiple resubmissions with detailed review notes and video walkthroughs, the IAPs have been repeatedly rejected without specific or actionable feedback. The equivalent IAPs submitted for Ice Scream 3, using the exact same implementation and business model, have already been approved by the App Review team. Current status per app: Ice Scream 1: App approved. IAPs have been repeatedly rejected with no specific feedback indicating what needs to be corrected. Ice Scream 2: App approved. After multiple rejections, the IAPs have been stuck in "In Review" status for over a week with no update or response. Lack of Communication: We have opened support cases for both titles and have received no response or actionable feedback. The lack of synchronization between the App Review and Support teams is causing significant operational disruptions and is directly impacting our business. Impact: Not having the monetization features active in both titles is causing direct financial loss and preventing our users from accessing content they need. Request: We request an immediate update on the status of these IAPs and clarification on why the support cases remain unanswered. We are looking for a direct escalation or a response from an Apple representative who can resolve this situation. Related apps and support cases: Ice Scream 1: Scary Horror — App ID: 1480827449 — Case ID: 102902530872 Ice Scream 2: Scary Horror — App ID: 1488473484 — Case ID: 102902529670 I look forward to a prompt resolution. Sincerely, Maria Laskurain Keplerians Horror Mobile Games

Hi everyone, We develop the Ice Scream series and are introducing consumable IAPs (coin packs) for the first time in Ice Scream 1 and Ice Scream 2. The products are straightforward: coin packs that users can spend on boosters and additional content within the game. No expiration, clear value description, standard StoreKit implementation. Here's where things stand: Ice Scream 3: consumable IAPs submitted under the same model were approved without issues. Ice Scream 1: IAPs have been rejected multiple times with no specific feedback indicating what needs to be fixed. Ice Scream 2: after multiple rejections, the IAPs have been sitting in "In Review" status for over a week with no update. With each rejection we have provided detailed review notes including step-by-step instructions to reach the Shop (which requires completing a short onboarding tutorial as a new user) and video walkthroughs showing the full purchase flow for both new and returning users. Despite this, we keep getting rejections or no response at all. We have also submitted an appeal form requesting specific clarification, but have not received any reply. A few questions: Has anyone experienced a similar situation with consumable IAPs being repeatedly rejected without actionable feedback? Is there anything specific Apple checks for consumable IAPs beyond what is covered in Guideline 3.1.1 that we might be missing? Is there any other escalation path beyond the appeal form when a review appears to be stalled? Any help or insight would be greatly appreciated. Thanks!

I have encountered the following issue on iPadOS. Has anyone experienced this issue or reported it before? Steps to Reproduce Enable Windowed Apps mode in Settings. Launch the Settings app and another app (App X), and display both in windowed mode. Use the Settings app to completely cover App X (App X becomes inactive at this point). From the Settings app, enable Full Screen Apps mode. Bring App X to the foreground. Expected Result App X becomes active when brought to the foreground. Actual Result Even after bringing App X to the foreground, it immediately becomes inactive. The issue persists even if App X is restarted. To resolve the issue, it is necessary to either restart the iPad or switch back to Windowed Apps mode. Verified OS Versions iPadOS 26.5: Reproducible iPadOS 26.4.2: Reproducible iPadOS 26.2: Not reproducible iPadOS 26.0.1: Not reproducible Additional Information According to the console logs, App X appears to remain inactive because the deactivation reason "sceneOverlap" persists.

I developed an app for the first time today and bought an iPhone 6s in 2015. The problem is that the app compatibility isn't optimal.I receive error messages when compatibility is set to iOS 6 and higher.

Hi, We've implemented age assurance logic in our app using the DeclaredAgeRange framework to comply with regulations in Brazil (Digital ECA, effective March 17, 2026) and Utah (App Store Accountability Act, effective May 6, 2026). Our implementation calls AgeRangeService.shared.isEligibleForAgeFeatures on app launch to determine whether the current user is subject to age assurance requirements, and proceeds to call requestAgeRange(ageGates:) accordingly. However, after monitoring in production since the Brazil enforcement date, we've consistently observed isEligibleForAgeFeatures returning false for users in regulated regions, with no age range data being returned. What we'd like to clarify: Is isEligibleForAgeFeatures currently returning true for users in Brazil in production (not sandbox)? For Utah — given that HB 498 pushed the developer compliance deadline to May 6, 2027, will isEligibleForAgeFeatures reflect the original May 6, 2026 activation date or the revised 2027 date? Is there a known rollout schedule or gradual activation plan for these regions that would explain why the flag remains false even after the legal enforcement dates have passed? We've seen similar reports from other developers on these forums, so it seems this may be a widespread issue rather than an implementation problem on our end. Any official guidance on the current status of the API in regulated regions would be greatly appreciated. Thanks.

Hello, I’m trying to enroll in the Apple Developer Program, but I accidentally entered my name incorrectly during the enrollment process. It seems the mistake may have been caused by autocorrect on my iPhone, and I noticed it only after the enrollment had already started. Since then, I have contacted Apple Developer Support several times, but each time I receive a email with standard instructions that do not actually resolve the issue. I am not trying to bypass any verification process — I simply need the current enrollment attempt to be reset or deleted so I can start again with my correct legal name. At the moment, I seem to be stuck: I cannot complete the enrollment correctly, and I also cannot restart the process properly. Has anyone experienced a similar issue? Is there any way to request a manual reset of an Apple Developer Program enrollment attempt, or to have the incorrect enrollment information removed so I can submit a new enrollment with the correct name? Any guidance would be greatly appreciated. Thank you.