Overview

Please take a look at: FB22280049

I've encountered an issue where we need multiple domain associations with separate Apple Pay implementations. Briefly, we have a /.well-known/apple-developer-merchantid-domain-association already setup with Stripe, and now we need another, different version of the file to get setup with FreedomPay. FreedomPay insists this file represents a three-way relationship between all parties and I have no reason to disbelieve them. I'm wondering if anyone has encountered this or if there is a standard procedure. I'm currently trying to find documentation on the exact way Apple Pay verification interacts with this file to see if we can produce it dynamically.

Dear Xcode cloud support. on 30.1.2026 Xcode cloud was not able to connect to our git server. so I deleted the repository from app store connect Xcode cloud settings and deleted the Xcode cloud in app store connect for all our apps. I started to create Xcode cloud workflow from Xcode and when I want to Grant Access - Register GitLab Application - to our git repository I get and error : "504 Client Timeout. If you are using a firewall, it must be configured to accept incoming connections." git is behind VPN but the IP address ranges 17.58.0.0/18, 17.58.192.0/18, and 57.103.0.0/22 are white labeled and before 30.1.2026 it was working. I contacted the gitlab administrators and they acknowledged that during "Register GitLab Application" they see no traffic (in gltlab and proxy server) from xcode cloud. I tried "Register GitLab Application" multiple times until now with same error. It is not app specific because this error happens for all our apps. Thanks a lot yours sincerely, Zoltan Bognar More Info: Source Control Provider: git-lab self-managed, tested with web browser: safari, chrome I can provide additional info like Primary repository, App store team ID, Entity Name, Link to repository, Application ID to grant access, and bundle id. if needed.

We're developing a service that requires webtransport support in the browser. Currently, the only browser that doesn't provide support is the IOS version of Safari. Our current way forward for client use is to flag iphone and ipad as non compliant and recommend either desktop use or android. Is there any ballpark date as to when WebTransport will be included in IOS Safari (- webkit supports webtransport)?

Hi, Please review my app I’m reaching out regarding an issue with my app review process. I was expecting a call last week but unfortunately didn’t receive any contact. I would really appreciate it if someone from the team could either review the app as soon as possible or contact me directly. I’m available anytime for a call. thanks

Hi Apple Developer Support team, I am writing because I have exhausted every available support channel and need urgent manual intervention. Organization: Bedrock Residences Limited Apple ID: Temitope Moronkeji Case ID: 102844508761 Enrollment ID 333LLR3M2M Issue started: March 14, 2026 What happened: I enrolled Bedrock Residences Limited in the Apple Developer Program as an organization. I have completed the $99 payment twice. Both times I received the purchase acknowledgement email confirming the order. Neither time did I receive the membership confirmation email. My account has remained on Pending status for over 10 days. What I have tried: Contacted Apple Developer Support via email on March 14 and March 20 Zero response on both occasions The support portal will not allow me to reply to or update Case ID 102844508761 The "Get More Help" option on the support page does not allow me to submit a new request Current status: Account shows Pending "Complete your purchase" prompt still appears despite two completed payments No access to App Store Connect No membership confirmation email received on either attempt Two $99 charges on my card with nothing to show for it This is blocking an active iOS app launch for our organization. Based on reports from other developers on this forum, this appears to be a backend activation failure on Apple's side and requires manual intervention by the Developer Enrollment team. I am requesting: Manual activation of the Bedrock Residences Limited developer account Confirmation of which payment to apply and refund of the duplicate charge A direct callback or email response — not an automated reply I have been patient for 10 days. Please help.

https://developer.apple.com/documentation/DeclaredAgeRange/AgeRangeService/isEligibleForAgeFeatures returns a bool. I assume that means that it will return True for the states where their laws are in effect. The TX law and the UT/LA/AZ laws have different requirements though: TX requires the app verify the user's age on every app launch. These other states require the app verify the user's age "no more than once during each 12-month period" A future law (Brazil maybe?) might do something else. How can we determine if the user is eligible for the TX versus other state requirements?

Hi, I want to create a ControlWidget button that acts as a shortcut in the control center open a specific view within my app to show a badge. Problem: I can‘t get it to open my host app. I tried a custom myapp:// protocol - did not work, I tied AppIntent with the openAppWhenRun set to true - did not work and the strange thing is the debugger breakpoint in perform will only get triggered if this is set to false. OpenIntent did not work either even if I use a dummy swift app as host to try it out. What is the current supported way (iOS 18 and 26) to open your app when a static ControlWidget button is clicked, what could I have done wrong / am missing?

Hello, I am experiencing a persistent TestFlight installation issue affecting multiple unrelated apps under the same Apple Developer account. For all affected apps: Builds upload successfully to App Store Connect Processing completes normally Builds appear in TestFlight Internal and external testing can be enabled Public links generate correctly However, when attempting to install the app via TestFlight, the installation fails with the error: “The requested app is not available or doesn’t exist.” This occurs: For internal testers For external testers Across different Apple IDs Across different devices With newly created apps After incrementing build numbers After re-uploading builds After signing out/in of TestFlight After regenerating provisioning profiles After creating entirely new app entries The issue currently affects: • TubeChat AI – Apple ID 6752591427 • Vibex – Apple ID 6756860663 • vigilAI – Apple ID 6757738356 Since multiple unrelated apps are impacted in the same way, this appears to be an account-level or App Store Connect backend issue rather than a code signing or project configuration problem. Has anyone encountered a similar situation where TestFlight distribution fails across all apps within a developer account? Any guidance would be greatly appreciated.

Setup: Xcode 26.3. MacOS Tahoe 26.3.1 Signed in for Coding Intelligence with Claude Pro plan. For the first 3 prompts Claude responded normally. Afterwards it always responds with "Your request couldn't be completed."

Hello, I'm using videotoolbox superresolution API in MACOS 26: https://developer.apple.com/documentation/videotoolbox/vtsuperresolutionscalerconfiguration/downloadconfigurationmodel(completionhandler:)?language=objc, when using swift, it's ok, when using objective-c, I get error when downloading model with downloadConfigurationModelWithCompletionHandler: [Auto] MA-auto{_failedLockContent} | failure reported by server | error:[com.apple.MobileAssetError.AutoAsset:MissingReference(6111)] [Auto] MA-auto{_failedLockContent} | failure reported by server | error:[com.apple.MobileAssetError.AutoAsset:UnderlyingError(6107)_1_com.apple.MobileAssetError.Download:47] Download completion handler called with error: The operation couldnxe2x80x99t be completed. (VTFrameProcessorErrorDomain error -19743.)

We've noticed, that size of our ipa started to vary from time to time. We've found that all the difference was in the LC_CODE_SIGNATURE command under the _LINKEDIT segment of binary. The main reason of that change was the different number of hash slots due to different value of page size: 4096 on macOS SEQUOIA and 16384 on macOS TAHOE. So the size of the final binary was dependent on the machine, it was produced on. I didn't find out any information on why the default page size changed on TAHOE. Apple’s codesign supports a --pagesize argument. For regular builds that setting can be passed via OTHER_CODE_SIGN_FLAGS=--pagesize 16384. But it seems that xcodebuild export ...` completely ignores it: i've tried to pass invalid size (not the power of two), and the export still succeded. I've also managed to get xcodebuild logs via log stream --style compact --predicate 'process == "xcodebuild" OR process == "codesign"' --level trace They have no occurrences of --pagesize: 2026-03-24 13:43:27.236 Df xcodebuild[93993:a08c53] [IDEDistributionPipeline:verbose] invoking codesign: <NSConcreteTask: 0x8a1b21bd0; launchPath='/usr/bin/codesign', arguments='( "-f", "-s", 8C38C4A2CB0388A3DB6BAEFE438F20E044EE6CB2, "--entitlements", "/var/folders/w_/5t00sclx2vlcm4_fvly7wvh00000gn/T/XcodeDistPipeline.~~~T3Dcdf/entitlements~~~c2srXx", "--preserve-metadata=identifier,flags,runtime,launch-constraints,library-constraints", "--generate-entitlement-der", "--strip-disallowed-xattrs", "-vvv", "/var/folders/w_/5t00sclx2vlcm4_fvly7wvh00000gn/T/XcodeDistPipeline.~~~T3Dcdf/Root/Payload/App.app/Frameworks/FLEXWrapper.framework" )'> So here I have some questions: How is the default page size selected? Why the default page size may change between SEQUOIA and TAHOE? How to provide page size to xcodebuild's export or it's a bug that it doesn't look at the value of OTHER_CODE_SIGN_FLAGS?

Hi, Our client currently has an FPS deployment certificate generated with SDK version 4 that is still actively used in production. They would like to generate an additional certificate using SDK version 26. Before doing so, they just want to confirm: Will the existing SDK 4 certificate remain unaffected and still visible in the Apple Developer portal? Any considerations they should keep in mind? Thanks! :)

pkgbuild on Tahoe (26.3.1) fails to build packages if any directory name contains non-ascii characters. pkgbuild is able to build successfully with the same source data on previous versions on macOS, so this is a regression and prevents us from build able to build our products on macOS 26. Example that demonstrates the issue: mkdir -p MyAppData/Taishōgoto echo "Testing" >> MyAppData/Taishōgoto/Content.txt pkgbuild --identifier com.example.MyAppData --install-location '/Library/Application Support/MyAppData' --root MyAppData myappdata.pkg Error messages: parent directory ./Taishōgoto does not exist pkgbuild: error: Cannot write package to "myappdata.pkg". (The file “package.bom” couldn’t be saved in the folder “NSIRD_pkgbuild_52fPuN”.) I have submitted this via Feedback Assistant (FB22312299). I have not found a workaround. Tried copying pkgbuild from Sequoia but the problem persisted, probably because the buggy code is in PackageKit rather than the tool itself.

Hello everyone. We have an app that has been on the App Store for several years, originally distributed for iOS and iPadOS only. Recently, we enabled Mac (Designed for iPad) and started distributing macOS-compatible builds. Current situation: The app is available and downloadable from the macOS App Store and runs correctly on Apple Silicon Macs. The same app/build appears in TestFlight on macOS, but cannot be installed. TestFlight shows the message: “This app can only be tested on an iOS device.” This suggests the app itself is Mac-compatible, but TestFlight is treating the build as iOS-only. Environment and checks performed: Mac is Apple Silicon. App Store Connect app-level availability for Mac (Designed for iPad) is enabled. The app is not Mac Catalyst; it is a UIKit iOS/iPadOS app. Distribution is done via GitLab CI. CI uploads use an App Store provisioning profile (Apple Distribution), not development or ad-hoc. iPhone and iPad TestFlight installs work as expected. Info.plist verification: UIRequiredDeviceCapabilities was originally present (armv7) and has since been: removed entirely, build number incremented, new builds uploaded to TestFlight. No other hardware capability requirements are declared. LSRequiresIPhoneOS = true remains unchanged. No other plist keys that should exclude macOS are present. CI / build considerations: The same uploaded build is accepted by App Store Connect and distributed successfully on the macOS App Store. This tells us the binary itself is valid for macOS, but TestFlight applies additional or different eligibility checks. At the moment we think that TestFlight eligibility may depend on build metadata, scheme/configuration flags, or internal App Store Connect state that differs from App Store distribution. Questions: Are there known cases where a build is valid for macOS App Store distribution but not eligible for macOS TestFlight installation? Does anyone know if TestFlight applies stricter or different platform gating than the App Store for “Mac (Designed for iPad)” apps? Are there specific build settings (e.g. SUPPORTS_MAC_DESIGNED_FOR_IPAD, TARGETED_DEVICE_FAMILY, scheme/config mismatches) that can affect TestFlight macOS eligibility independently of App Store eligibility? Is there an authoritative way in App Store Connect to inspect why a specific TestFlight build is marked as “iOS-only” for macOS? Any insight into TestFlight-specific eligibility rules for “Mac (Designed for iPad)” would be appreciated, especially given that App Store distribution for macOS is already working. I hope we're missing something very basic, and not that the app can't be tested as is for the mac, because it's useful to have our QA team test it on the mac.

Was working before, no longer working this week. Trying to sign in to my Claude Pro account via Xcode Intelligence. Goes to browser, I login, and accept authorization in Claude then redirect back to Xcode is reject. Everytime, multiple browsers, and even trying the add "/" that others have noted for other cases.

Hey there, We are being incorrectly blocked by Time Limits since the iOS 26 update released earlier this year. We are receiving complaints from parents that set a screentime limit for "All apps", and then add an exception for us, that they are still getting blocked by the OS after a certain period of time. While we originally thought this was fixed in 26.1, we have recently been made aware it still occurs. Has anyone else experienced this issue? Is there something we can do from our side to protect ourselves from this? Telling customers to remove their "All app" limit isn't really practical given our customer base, so we're looking to see if there's something on Apple's end or our end that can alleviate this.

Hi everyone, my Digital Services Act (DSA) status in App Store Connect has been “In Review” for over a week. Is this normal? The app is already available in 178 countries, but it can’t be released in the EU (my home market) solely because this DSA isn’t approved yet. How long did it take for you? Is there anything that helps speed up the DSA review? Thanks for any insights.

Focus on improving onboarding, reducing friction, and delivering quick value so users form a habit early. Use analytics to identify drop-off points and continuously refine the experience. Increase spending by introducing clear value-driven upgrades, limited-time offers, and personalized recommendations. Reward loyal users and test pricing strategies to find what converts best.

Hi all, Submitted first ever app for review to app store and got rejected. My app isn't live and I have demo accounts too which they seemed to use. For context my app is free on launch, no in app transactions, and it is a marriage app. What I did not account for is them going through apple sign in and right now I have no way to catch that so that account doesn't mix with real users. I've thought about adding a tap feature and disclosing it, so they tap something x times and it is marked as reviewer account, but that violates guideline 2.3.1. Also thought about adding just visible text for reviewers, but then real users would see that too so its a no go. Asked Claude and it says to try Sandbox Receipt Detection, which should work for a free app, but I'm not sure and would rather ask then implement, submit and find out it doesn't work. Appreciate any help y'all can give me! Thanks!