Hi, We've had our app rejected in review a number of times recently because the reviewer is unable to connect to our backend services. Investigation and direct communication with a representative of the App Review team has uncovered that our domain is also being blocked in Safari within the Apple network. This has also lead to the side effect of us not receiving any emails from apple.com (no submission approval/rejection confirmations) nor being able to invite new team members to our App Store Connect account as the invite is never received. We've had this issue since the end of August 2025 and have not had a resolution either through communicating with the App Reviewer nor our direct call with a representative from the App Review team. Is there some other avenue we can use to triage this issue and get it permanently resolved?

When trying to respond to a review in App Store Connect developer console, the submitted review disappears as if we never responded. It happens to different apps that we have in published state. In App Store Connect select an app Go to Ratings and Reviews Choose a review and select "Reply" Add text and press Submit The reply doesn't appear even after refreshing the page Actual result: the reply should appear underneath the review as "Developer Response" or "Developer Response Pending"

I'm building a new app that uses the new background uploads extension, unfortunately, the App Store Connect process fails with the provided EXExtensionPointIdentifier. Invalid Info.plist value. The value of the EXExtensionPointIdentifier key, com.apple.photos.background-upload, in the Info.plist of “MyApp.app/Extensions/BackgroundUploadExtension.appex” is invalid. Please refer to the App Extension Programming Guide at https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/Action.html#/apple_ref/doc/uid/TP40014214-CH13-SW1. (ID: a471e5e7-361c-487f-8554-9deda472b2bc) Confirmed that both the app and extension targets are set to 26.1 minimum. What would be the best way to resolve/fix this?

Hi everyone, solo iOS dev here. I’ve built a small focus app (“Modo”) that uses Apple’s Screen Time APIs to help curb social-media overuse. In development everything works: FamilyActivityPicker for selection, a DeviceActivityMonitor extension for schedules, and ManagedSettings shields (plus uninstall guard only while “Blocked” is active). I requested the Family Controls distribution entitlement so I can ship, but my capability request has been pending for a while and I’m not sure what the usual path forward is. What I’ve already done • Submitted the capability request (Account Holder), describing the use case (self-control / digital well-being), user consent flow,. • Implemented app + DeviceActivityMonitor + ManagedSettingsUI extensions; verified the debug build has the right entitlements and behavior. • Regenerated profiles after the request; checked codesign entitlements on the built targets. • Filed a Developer Support ticket referencing the capability request. I really appreciate any timelines, examples, or advice you can share. If an Apple engineer needs specifics (Team ID, request number), I can provide them as well. Thanks in advance!

Hi, a short question really, which boils down to... How do I make sure I have removed all usage of app groups in my Mac app store app, such that the Mac app store agrees I have! Fundamentally, what I'm trying to do is transfer my app to another developer. In previous releases of this app on the App Store, I used a shared app group container to communicate between the main app and it's (embedded) XPC service, but this blocks App Store transfer of the app to another developer. So I came up with another approach for the App and XPC service to communicate (using a URL bookmark for security scoped files to be passed to the XPC service). And then tried various things to get the app store to accept that I'm no longer using app groups. So far with no luck... removed the app groups entitlements by hand from the entitlements files used to sign the main app and the XPC service, respectively. when that didn't work, go into the Developer Portal, find the app ids for the main app and the XPC service, make sure those app ids had the app groups entitlement removed too, created a new provisioning profile for the app, based on this updated app id, downloaded it, rebuilt an app archive using this updated provisioning profile and used it to create another new release on the app store when that didn't work, found and deleted all app app groups in my developer account in the developer portal itself None of the above worked. When I try to transfer the app in App Store Connect, I still see the same message, "You can't transfer this app because of the following reasons: Sandboxed Group Container You can only transfer sandboxed apps that are not sharing a group container." I'm now pretty far from using a shared group container, so I'm puzzled why it still thinks I am? There is one last thing I can try... I noticed over the weekend that even though the entitlement is gone, there's one place in code that may or may not be run on rare occasions (hard to tell) that attempts to open the app group shared container with the code... let container = FileManager.default.containerURL(forSecurityApplicationGroupIdentifier: ...which I think is just returning nil and doing nothing. Potentially the App Store sees that attempted API access for shared group containers and assumes I'm still using app groups (even though there's no entitlement so that call will always be failing)? I can do yet another App Store update and just remove that code. But I want to get to the bottom of why it has been failing all this time. What is App Store Connect / the Mac App Store looking at that makes it think I'm still using app groups? I've tried so many things and don't want to mess users around with another App Store update unless this code above is the actual cause! Cheers p.s. It's a teamID based app group of the form... MY_TEAM_ID.s4a e.g. SWDC5K54B7.s4a

Is Xcode 26 required for DeclaredAgeRange APIs? We ask because there appears to be a serious legal deadline on January 1, 2026 and if Xcode 26 is required to meet this deadline, it's about to be a huge burden for us to upgrade to it over the holidays. Our app does support teenagers.

Hey guys, Just noticed that our “App Tags” tags are incorrect. According to Apple docs, “Tags are applied to your app by default, based on the metadata you provide in App Store Connect (en_US only).” The only tag that appears for my app is “video,” which is strange given that it does not have any video component and the word “video” is not included in the App Description, keywords, or anywhere else. Does anyone else have mislabeled Tags or know how to edit them?

It's been over two weeks since I accepted the updated agreement BUT when I am in App Store Connect, trying to add a new version for my app, click the + sign still show this pop up: Agreement Update The Apple Developer Program License Agreement has been updated and needs to be reviewed. For more information, go to your account on the Apple Developer website. There is no way to by pass it, meaning no way for me to add a new version at all. I need to deploy a new version for some critical bug fixes, particularly to address compatibility issues with iOS 26. In my Xcode, after archiving a new build, trying to upload it to either Distribution or TestFlight, it kept failing and showed me error "You don't have required contract for this operation.". I called Apple Support last week and was told by a Senior Staff that this happened to many developers (?) due to some maintenance issue and should resolve after Nov. 3rd, except, the issue persists. I am so frustrated. :( Exactly what happened at app store connect side?

Hi everyone, I'm the developer of Evil Neighbor games. https://play.google.com/store/apps/developer?id=Tonny+Nevel My game was decompiled and published on the App Store. With super-stupid input controls and a lot of ads. https://apps.apple.com/us/app/evil-father-simulator-game/id1660614304 It's a clone of my game: https://play.google.com/store/apps/details?id=com.juliopepe.evilfather2 I decided to make a port on the iOS App Store, as my users asked me about it. And got rejected for all 3 parts with the reason "Spam". On my own game I have sent a report for this account 4 months ago https://apps.apple.com/us/developer/manale-adle/id1671853753 (By the way, all other games are stolen too) App store is ignoring me; they sent a message to me and to him. Asked him to contact me and solve the issue. 4 months I have been waiting for a reply from them. I have sent 10+ emails, but it looks like they just put me on the ignore list. Two days ago, I tried to publish another game that I was developing during the year. And guess what, they just reject it as "4.3 Spam", probably because of 3 rejected apps on my account... I'm a real developer of these games, and I can't publish them on App Store. Looks like we are not secured by App Store. I don't know what to do; the submission team is just rejecting with the default point in the rules. If someone has an idea of what I can do, please let me know, because this injustice kills me

Issue: SKOverlay configured with a Custom Product Page identifier opens the default product page instead of the custom one on iOS 26. This works correctly on iOS 18 and earlier. Details: Custom Product Page is published and valid in App Store Connect customProductPageIdentifier is correctly set on SKOverlayAppConfiguration Same code works fine on iOS 18 and lower Code: - (void)presentSKOverlayInWindowScene:(UIWindowScene *)scene { SKOverlayAppConfiguration *config = [[SKOverlayAppConfiguration alloc] initWithAppIdentifier:@"my_app_id" position:SKOverlayPositionBottom]; config.userDismissible = YES; if (@available(iOS 15.0, *)) { [config setCustomProductPageIdentifier:@"my_apps_custom_product_page_id"]; } SKOverlay *overlay = [[SKOverlay alloc] initWithConfiguration:config]; overlay.delegate = self; [overlay presentInScene:scene]; } Are there any known iOS 26 changes affecting Custom Product Pages with SKOverlay, or is additional configuration now required. Thank you

Hey guys 👋🏼 I'm trying to publish my first App, but it's not working and sadly the Support didn't have an answer too. Maybe someone experienced the same thing. Yesterday I enrolled in the Developer Program and today my account was switched from an individual to a corporation account (to display my business name instead of my private name). I got an email that the switch was successful. When Archiving the app in Xcode and trying to distribute I get this error message: "App Record Creation failed due to an invalid attribute. Request failed with error code "ENTITY_ERROR.ATTRIBUTE.REQUIRED", and reason "The provided entity is missing a required attribute You must provide a value for the attribute 'companyName' with this request"" Fits to the thing the support said to me, I should go to appstoreconnect to add my first app there and then I should ask me to create my company name. But it doens't. I just get an error with no information what to do. All Agreements are signed, banking information is filled out … Maybe someone can read something out of the xcode log? IDEDistributionAppStoreConnect.log Theres no way for me to set the Company name and resolve this issue. Any ideas? 🙏🏼 Thanks in advance 🙌🏻

Summary App Store Connect validation (Transporter) is rejecting a build that includes a ReplayKit Broadcast Upload extension. The validator reports that RPBroadcastProcessMode is “not specified”, but the shipped IPA’s Upload appex Info.plist has the key at the documented nested path, and Apple’s own analyser (swinfo) shows the same key/value. Error (Transporter 409) “Invalid Info.plist value. The value for the key 'RPBroadcastProcessMode' in bundle BeamRoomHost.app/PlugIns/BeamRoomUpload2.appex is invalid. RPBroadcastProcessMode value must be 'RPBroadcastProcessModeSampleBuffer' or 'RPBroadcastProcessModeMP4Clip'. The key was not specified.” Example error ID seen: 94ec8b42-ef1b-44e8-9d70-2c76458e1bb3 Environment • Xcode 26.0.1 (17A400) • macOS 15.6 (24G84) • Transporter 1.3.4 (13410) • App Apple ID: 6752822011 • Host bundle: com.conornolan.BeamRoomHost • Upload appex bundle: com.conornolan.BeamRoomHost.BeamRoomUpload2 • Version/Build: 0.9.4 (14) Most recent reproduction: 2025-10-02 ~09:00 GMT+1 Proof the key exists (from the IPA) Inside the IPA at: Payload/BeamRoomHost.app/PlugIns/BeamRoomUpload2.appex/Info.plist NSExtension.NSExtensionPointIdentifier = com.apple.broadcast-services-upload NSExtension.NSExtensionAttributes.RPBroadcastProcessMode = RPBroadcastProcessModeSampleBuffer Proof from Apple’s analyser (swinfo) for the same IPA asset-description.plist contains: … RPBroadcastProcessMode = RPBroadcastProcessModeSampleBuffer … Minimal plist shape used (Upload appex Info.plist) CFBundleDevelopmentRegionen-GB CFBundleExecutable$(EXECUTABLE_NAME) CFBundleIdentifier$(PRODUCT_BUNDLE_IDENTIFIER) CFBundleInfoDictionaryVersion6.0 CFBundleName$(PRODUCT_NAME) CFBundlePackageTypeXPC! CFBundleShortVersionString$(MARKETING_VERSION) CFBundleVersion$(CURRENT_PROJECT_VERSION) MinimumOSVersion26.0 NSExtension NSExtensionPointIdentifiercom.apple.broadcast-services-upload NSExtensionPrincipalClass$(PRODUCT_MODULE_NAME).SampleHandler NSExtensionAttributes RPBroadcastProcessModeRPBroadcastProcessModeSampleBuffer What we’ve tried • Fresh Upload appex target from Xcode template + NEW bundle ID. • Minimal Info.plist (only keys above). • Also tried a top-level duplicate of RPBroadcastProcessMode in addition to the nested key. • Tried RPBroadcastProcessModeMP4Clip (disposable build) → still reported “key not specified”. • Organizer vs Transporter uploads. • Xcode 26.0 → 26.0.1. In every case the IPA and swinfo show the key/value, yet ASC reports “not specified”. Questions • Is there a current ingest/validator issue where RPBroadcastProcessMode is not read from the nested path in Upload appex Info.plist? • Are there any additional expectations for ReplayKit Upload appex in ASC validation beyond the documented nested key? • Any recommended workaround while this is investigated? Cross-references • Feedback Assistant ID: FB20412340 (contains full IPA, asset-description.plist, screenshots, and a short Transporter screen recording). • Developer Support case: 102707552863. • Recent x-apple-request-uuid example: 30aa2221-3df3-10a2-b161-b59df37f080c. • SHA-256 for the ZIP of artefacts attached in Feedback: f7397c13e85d4ef0f5722ea75821ad04d51fe5f103ed03dbac646d3902e91227. Happy to provide a minimal repro project if helpful. Thanks in advance for any guidance or confirmation from the ASC/build-processing side.

I got a mail telling me developers need to update the age rating for all of their apps. I checked the documentation in the help section, but it seems there is no edit button at the top of the App Information section, nor a way to edit the age questionnaire. Do developers really need to create a new version of all of their apps just to answer 3 new questions on that form? *I'm not sure if I can even edit after uploading a new version as I haven't tried. Please fix it to be editable or update the information in the help section. It is also confusing. It says "Action required" in the mail, but App Store Connect notifications seem to suggest Apple will automatically adjust the rating themselves if I do nothing, and doing nothing is fine.

I can't sign "Paid Apps Agreement". I see its status as new. How can i solve this problem? I don't see button to click it.

I got message in "AppStore connect" saying that there is a new version of the new version of the agrrement (Your Paid Applications agreement has a new version)When clicking on the "Agree" button for the renew for the Paid app agreement i get an error message saying there is a problem, but not what problem,. This is the error message. "We are currently unable to process your request. Please try again later."Ive gottten this message for several weeksl I have been trying different versions, with the same result. I even tried to send a support case to apple, but the request has been unanswered for 3.5 weeks now. I diont know what to do..

I recently released the first version of my app, and it was discoverable via App Store search. After pushing an update with bug fixes and improved keywords/category, the new version went live and showed as “Ready for Sale” within hours. However, since the update, the app no longer appears in App Store search results - even when searched using its exact name. It’s still accessible through the direct link. Any insights or guidance would be greatly appreciated!

"ASO in 2025 is more algorithm-driven, with a stronger focus on user engagement signals like retention and in-app actions. Keyword relevance still matters, but quality and user experience now play a bigger role in ranking boosts."

Hello, Our Xcode Cloud builds are successfully archiving but fail every time during the "Export archive for app-store distribution" step. The issue appears to be a persistent authentication failure with App Store Connect that we are unable to resolve. Primary Error: The build logs show a critical authentication failure. IDEDistribution.critical.log shows: App Store Connect request for store configuration failed for account Session Proxy Provider... Unable to authenticate with App Store Connect. DVTITunesSoftwareService.log specifies the error is DVTITunesSoftwareServiceFoundation.DVTServicesSessionProviderCredentialITunesAuthenticationContextError.proxy. The build process eventually terminates during the IDEDistributionSymbolsStep with an Rsync failed error, which we believe is a symptom of the earlier authentication failure. Troubleshooting Already Performed: We have already taken the following steps without success: Verified the account used for the integration has "Account Holder" and "Admin" roles. Confirmed that Xcode Cloud's automatic signing is working correctly and is able to create new provisioning profiles. Thoroughly checked the App Store Connect web UI under Users and Access > Integrations > Xcode Cloud for a way to reset the connection, but no such option exists. Removed and re-added the Apple ID in the Xcode application's settings (Xcode > Settings > Accounts) on a local Mac. Our hypothesis is that the integrated authentication session between Xcode Cloud and App Store Connect is invalid or stale, and there is no user-facing way to reset it. Has anyone else encountered this "Session Proxy Provider" authentication error with Xcode Cloud? Is there a known solution or a different method to force a re-authentication of the service connection? Any guidance from Apple engineers or other developers would be greatly appreciated. (Developer Support Case: 102717975870)

have successfully created subscription with all metaData: Localization(inside subscription and also for subscription group), logo, description and also screenshots but subscription shows missing metadata instead of ready to submit causing flutter app package inAppPurchase to not found the subscription id or product it. Flutter code level : Future<void> _loadSubscriptions() async { Set<String> kSubscriptionIds = {'monthly_689'}; ProductDetailsResponse response = await _inAppPurchase.queryProductDetails(kSubscriptionIds); if (response.notFoundIDs.isNotEmpty) { kLog("Subscription IDs not found: ${response.notFoundIDs}"); } print("God it works seriously"); print(response.notFoundIDs); print(response.productDetails); print(response.error); subscriptions.value = response.productDetails; } Says: Subscription IDs not found is been logged I try with storekit it works!!! but as apple asking me we test on sandbox environment and it's not working I also created sandbox account login with same credentials and test it not works. Point is package I used in flutter not finding the above product_id I successfully added subscription group, localization, image and all still why my subscription not found ?

主app有2个扩展，主app的bundleID 有了家庭控制的分发权限，但是2个扩展申请了家庭控制的分发权限，一直没有给。导致我现在上传不了app到app store connect 中。一直在等待给权限！！！，app要等着发布