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!

For the past 5 days, myself and all TestFlight users with my app have been unable to access TestFlight. When opening the TestFlight app, it immediately displays "Couldn't Load Apps" "TestFlight is currently unavailable. Try Again." If you press "Try Again" over and over for several minutes it will sometimes let you access the main install page on iPhone devices, but generally it just stays locked on "Couldn't Load Apps". On iPad, it is not possible to get to the install page. This is happening across all devices (iPad and iPhone) and OS (iOS 15 to iOS 26). User who are TestFlight testers on multiple apps are unable to access their other apps because of this issue. I've uploaded a new build and version and the issue persists. I filed a feedback assistant report: FB20901217. Has anyone else experienced a similar issue?

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.

Validation failed This bundle is invalid. The icon file Runner.app/Frameworks/App.framework/flutter_assets/assets/icon/Icon-App-1024x1024@1x2.png must be in .png format. i generated the launcher icon images using flutter_launcher_icons packages & also tired different website . project build fine but when try to upload the app into TestFlight gives this error. how to fix it

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..

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

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."

We’re preparing our 2026 iOS development roadmap and need clarification on upcoming App Store submission requirements related to Xcode versions. Our team plans to migrate our apps to Xcode 26 by December 2025, and we’ve seen references indicating that Xcode 26 or later may become mandatory for App Store submissions starting April 2026. Could Apple please confirm: 1. Whether April 2026 is the official enforcement date after which builds created with earlier versions of Xcode (e.g., Xcode 16.x) will no longer be accepted for App Store submission. 2. Whether there will be any grace period or continued acceptance for builds created with older versions of Xcode beyond that date. We want to ensure our upgrade plans and release timelines are aligned with Apple’s official submission policies to prevent any disruption to our delivery schedules. Thank you for your guidance.

We’ve recently changed the name of our published app from “Gourmet Society Lloyds” to “Gourmet Society”. The current App Store link is: https://apps.apple.com/gb/app/gourmet-society-lloyds/id6447692472 After the name change, we expect the URL to look like this: https://apps.apple.com/gb/app/gourmet-society/id6447692472 However, we’re not sure whether Apple automatically updates the App Store URL (the text part before the ID) when the app name changes, and whether the old URL will continue to redirect to the new one. I couldn’t find any official Apple documentation confirming this behavior. Could someone from Apple clarify how App Store URLs are handled in such cases? Thanks in advance! Zoltan

Hi everyone, I have an app that was previously approved and published on the App Store. During the initial release, it was reviewed and approved very quickly. However, this time I submitted an app update (new version), and it has been stuck in the “In Review” status for 5 days ago with no updates or feedback from Apple. I’ve double-checked everything: metadata, privacy policy, and compliance with the App Store Review Guidelines – nothing seems off. Has anyone else experienced this with app updates (not first submissions)? Should I just wait it out or try contacting Apple at this point? Appreciate any insights. Thanks in advance!

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)

Hello Apple Developer Community, We are currently facing an authentication issue when calling the App Store Server API for subscription validation. Despite following Apple’s documentation and verifying all credentials, we consistently receive a NOT_AUTHORIZED error response. GET https://api.storekit-sandbox.itunes.apple.com/inApps/v1/transactions/appTransactions/{transactionId} Environment: Sandbox and Production (both tested, same result) Our Setup: Key ID: {Your Key ID} Issuer ID: {Your Issuer ID} Bundle ID: {Your Bundle ID} JWT Header: { "alg": "ES256", "kid": "" } JWT Payload: { "iss": "", "iat": , "exp": <timestamp + 5 minutes>, "aud": "appstoreconnect-v1", "bid": "" } Authorization Header: Authorization: Bearer Troubleshooting Steps Already Taken: Verified that .p8 key, Key ID, Issuer ID, and Bundle ID are all correctly configured and match the App Store Connect details. Confirmed that the system clock is accurate (UTC). Used appropriate endpoint (sandbox or production) based on environment. Ensured that the JWT is short-lived (under 5 minutes). Added the “Bearer” prefix correctly in the header. Tested JWT generations using Python. Issue: All requests return: { "errorCode": "NOT_AUTHORIZED" } Questions: Are there any additional claims or headers required for the subscriptions endpoint? Are there specific permissions or roles needed for the API key in App Store Connect? Is there a way to get more detailed logs or diagnostics for this NOT_AUTHORIZED response? Does the App Store Server API require a different aud or bid structure for certain endpoints? We already contacted Apple Developer Support, but they suggested posting here for engineering-level guidance. Any insight or examples of a working JWT + request for this endpoint would be greatly appreciated.

Love the new web-based App Store that launched today! I’m really hoping Apple will eventually provide a JSON/REST API for search results. Google doesn’t officially offer one either, but because of how the Play Store works for Chrome and Android, developers can use a third-party library like google-play-scraper. For small independent developers like myself, it’s a bit of a disadvantage being priced out of expensive data brokers such as Sensor Tower, who are obviously scraping the App Store anyway. It’s also uncomfortable knowing those companies harvest data from App Store Connect while charging us to access analytics based on our own apps. Would it be too much to ask for an official—or even semi-official—way to retrieve country-specific keyword rankings for apps?

My submission was rejected twice for "framing in the preview video". I couldn't understand why because there was no framing. Then on the 2nd rejection I noticed an included screenshot. The screen shot wasn't from my new preview video but from the old (they are very old) preview videos that are currently approved and live on the app store. Why did this happen? Because I had uploaded my new videos to the app update and decided before submitting I would run an A/B test to make sure they performed as well or hopefully better. When I went to the "Product Page Optimization" section I found my new videos already there. However... The new preview videos were in the "Original Product Page" and the old videos were in "Treatment A". I asked ChatGPT about this and it said not to worry it was a known quirk. What has obviously happened is that when the reviewer reviewed my Product Page Opt test they were presented with the old videos from Treatment A and not the new videos which were in "Original Product Page", as proven by the screenshot from the old, approved, live, video. I've submitted my app update but you seem to be just sitting on it now. I'm guessing because I'm black marked as not fixing an issue and constantly resubmitting unfixed. Please don't punish me for your mistakes....

My application has reached a testing quota of 10,000 testers, including those who have not participated for an extended period. Consequently, new testers are unable to join. I attempted to delete these testers by selecting the “Delete” button in the “Testers” section on the AppConnect page. However, their status only changed from “Installed” to “Deleted,” and they still count towards the quota. Could anyone provide guidance on how to resolve this issue?

I've reached maximum number of testers for my app. That's why I've deleted all testers from TestFlight to clean testers list and invite new and old testers again by public link. But deleted testers are still count in "All testers", but in "Deleted testers" filter. And the error "You’ve added the maximum number of external testers for this app" still occurs. Is this how it's supposed to work or is this a bug?