I just submitted a build to TestFlight this morning that should have set off the same alarms as last week, but it didn't. We received no emails complaining about "ITMS-91053" violations like happened on this branch before. We've been working hard to figure out how to meet your new privacy requirements, and it's been quite frustrating. I thought I finally fixed it yesterday, but today I wanted to run a sanity test. I went back and created a build that should fail, but now that one is apparently fine as well. I'm at a complete loss.

We have a use case where we want to have two different builds of our app in TestFlight: one for the test environment and another for production. Each build has a different .env file associated with it, containing different values based on the environment. The test build will only be used by internal testers, whereas the production build will be used by both internal and external testers. I know there was a way years ago to append a suffix to the build number, something like 0.18.1-test, so we could specify which build specifically uses the test environment variables. However, when I try to submit a build to TestFlight with any alpha characters in the build number, App Store Connect rejects it with the error message: '0.18.1-test' is not a valid value for the attribute 'cfBundleShortVersionString'. Are there any current best practices or official guidelines from Apple on handling a scenario like this? What's the recommended approach for differentiating between test and production builds in TestFlight? Our first solution was to place all our test builds in VS App Center and production builds in TestFlight. However, Microsoft recently announced that VS App Center is being retired next year and recommends using TestFlight instead for iOS builds. So, we're looking for a solution that will work with TestFlight going forward.

When we try to add a tester or a group and submit for review, we get the error "There was an error processing your request. Please try again later."

Dears, I have been exploring the documentation provided by Apple regarding app data management through API requests. Specifically, I am interested in the possibility of initiating the app creation process itself using a POST API request sent via Postman or similar tools. Attached is the documentation link I've been referring to: https://developer.apple.com/help/app-store-connect/create-an-app-record/add-a-new-app Could you kindly assist me in clarifying whether it's feasible to create an entire application using such API requests? If not, I would appreciate any guidance or resources you could provide on the appropriate procedures for app creation within the Apple ecosystem. Thank you very much for your time and assistance. I look forward to your response. Warm regards,

I successfully submitted my project to App Store Connect, and got it approved for external TestFlight testing. I have made updates to my project, and am trying to submit another build, but am getting the error: "The value for key CFBundeShortVersionString[1.0] in info.plist must contain a higher version.." I attempt to change both the short bundle version, and regular bundle version to 1.1.0 without any luck. I also attempted to go into the "Versioning" within build settings to change both the current project version and marketing version to 1.1.0 without any luck. I am confused what is going on, and why my build is not just incrementing as expected. Any suggestions is very appreciated.

What if I already have an app named "A" but want to upload a new application named "A" The same thing where the old app and can still be used and the new app can still be displayed? **If there are details showing that duplicate names cannot exist, please attach them to me. thank you.

I'm about to submit a react native expo app to the ios app store. Locally the app seems to be fine but when I try testing it with test flight, it crashes on start up. Please see the attached crash log. Crash Log Any help would be greatly appreciated.

I have created a new build for my Safari web extension and distrbuted it to test flight. Test Flight says I am using the correct version - but when I go to the Setting > Extensions in Safari and enable it - it still has the old version number. App Store showing the correct version is in testing Test Flight confirming said version number Safari with the incorrect version Any idea what I am doing wrong?

There is a app I’m trying to download on my watch (watchos only app) and it’s not downloading it’s just loading only and it keeps loading until the install button shows up again hours later

In https://developer.apple.com/news/?id=x60uzbu9, it is stated that: "You’ll need to let us know whether or not you’re a trader to submit new apps to the App Store." Currently, I have an app that I submitted for Testflight beta review that is still waiting for review since 20 Mar 2024, 00:00 GMT. I have not submitted the DSA compliance since my company still need to align for the documents. Does not complying yet with the DSA affect Testflight submission?

We have a network content-filter consisting of a main target/GUI, a FilterDataProvider extension and a FilterControlprovider extension. The app is installed via MDMs and works without issues the vast majority of times, but during testing of TestFlight builds we've found that intermittently the device fails to install the network extensions and blocks internet access. The GUI is working fine though. From the logs we can see that when this happens the device tries to start the network extensions repeatedly. The issue is solved by restarting the device. Has anyone experienced similar issues or have some ideas of what might cause this behaviour? These are some of the logs we see in Console: neagent [u E6D696F2-62FB-4262-A97C-B2006EC528C5:m (null)] [<private>(<private>)] Hub connection error: Error Domain=NSCocoaErrorDomain Code=4097 "connection to service named <BundleID>.FilterDataProvider" ugDescription=connection to service named <BundleID>.FilterDataProvider}code-block Failed to start the data extension <BundleID>.FilterDataProvider: Error Domain=NSCocoaErrorDomain Code=4097 "connection to service named <BundleID>.FilterDataProvider" ugDescription=connection to service named <BundleID>.FilterDataProvider} nehelper Denying connection from nesessionmanager (264) because it is missing the com.apple.private.network.socket-delegate entitlement nesessionmanager <BundleID>[inactive]: starting launchd Service could not initialize: posix_spawn(/private/var/containers/Bundle/Application/F84E2325-05A6-4DC2-8DD6-20C97EF43E8D/<AppName>.app/PlugIns/FilterDataProvider.appex/FilterDataProvider) failed, error 0x2 - No such file or directory nesessionmanager NEFilterPlugin(<BundleID>[inactive]): Sending start command nesessionmanager <BundleID>[inactive]: starting neagent Looking for a data extension with identifier <BundleID>.FilterDataProvider neagent [d <private>] <PKHost:0x718915550> Query: { NSExtensionIdentifier = "<BundleID>.FilterDataProvider"; NSExtensionPointName = "com.apple.networkextension.filter-data"; } neagent Found 1 data extension(s) with identifier <BundleID>.FilterDataProvider neagent Looking for a control extension with identifier <BundleID>.FilterControlProvider neagent [d <private>] <PKHost:0x718915550> Query: { NSExtensionIdentifier = "<BundleID>.FilterControlProvider"; NSExtensionPointName = "com.apple.networkextension.filter-control"; } neagent Found 1 control extension(s) with identifier <BundleID>.FilterControlProvider neagent Beginning data extension request with extension <BundleID>.FilterDataProvider neagent [u C743CE7B-9E19-4A41-BF46-91AEFB24169D:m (null)] [<private>(<private>)] Failed to start plugin; pkd returned an error: Error Domain=PlugInKit Code=4 .<AppName>.FilterDataProvider(C743CE7B-9E19-4A41-BF46-91AEFB24169D): Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch ErrorDomain Code=2 "No such file or directory" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}" UserInfo={NSLocalizedDescription=RBSLaunchRequest error trying to launch 7B-9E19-4A41-BF46-91AEFB24169D): Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0xdb88df3d0 {Error UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}} neagent Extension request with data extension <BundleID>.FilterDataProvider started with identifier (null) neagent Failed to start the data extension <BundleID>.FilterDataProvider: Error Domain=PlugInKit Code=4 "RBSLaunchRequest error trying to launch vider(C743CE7B-9E19-4A41-BF46-91AEFB24169D): Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., SIXErrorDomain Code=2 "No such file or directory" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}" UserInfo={NSLocalizedDescription=RBSLaunchRequest error trying to DataProvider(C743CE7B-9E19-4A41-BF46-91AEFB24169D): Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., SIXErrorDomain Code=2 "No such file or directory" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}} nesessionmanager NESMFilterSession[FilterDataProvider:0C4C9E40-5005-47A5-8C60-F7C8630F29DF] in state NESMFilterSessionStateStarting: plugin NEFilterPlugin(e with error: 1 nesessionmanager <BundleID>[266]: disposing neagent Initializing the delegate neagent App <BundleID> is not installed or is not valid neagent App <BundleID> is not installed or is not valid neagent Failed to find a com.apple.networkextension.filter-data extension inside of app <BundleID> neagent NEAgentSession: failed to create the delegate nesessionmanager <BundleID>[259]: Tearing down XPC connection due to setup error: Error Domain=NEAgentErrorDomain Code=2 "(null)" nesessionmanager <BundleID>[259]: XPC connection went away nesessionmanager NESMFilterSession[FilterDataProvider:0C4C9E40-5005-47A5-8C60-F7C8630F29DF]: Failed to start with error: Error Domain=NEAgentErrorDomain Code=2 "(null)"

Does the App Store Connect API support viewing the developer's operation logs on App Store Connect, such as setting the build version to expire?

Hello, everyone, I have been having problems with builds uploaded to TestFlight for a couple of weeks now. These , from the app (iPhone, iPad, Mac), are not downloading. If I try I get an error message saying the app is unavailable or does not exist. If I try to add a build to an external tester group I get the warning : There was an error while processing your request. Please try again later. Checking in the browser termianel I noticed the error : Failed to load resource: the server responded with a status of 422 () with in : message: "API Response Error: TF_BETA_APP_REVIEW_RESPONSE" I've tried everything but can't figure out how to fix it. Can anyone. give me a hand? Do you know what is going on?

Xcode crashes when i'm validating/distributing my archived app for testflight testing purposes. I have previously submitted two versions of the same app, and didn't have this problem. The only changes are the source code (which successfully builds and runs on the ios simulator or different android machines), and the Version (which is currently 0.0.8, while the previous were 0.0.6, 0.0.7) Whenever I press the button for validate app/distribute app, the process crashes. I recorded the screen and found that it crashes on validating "Runner.app". I have tried doing the steps below, and none of them are working. Any hints of solving this issue would help a lot. checked that my apple developer account has agreed to all terms of use updated macOS, xcode, cocoapods to the latest version deleted all developer/xcode cache files and rearchived the source code and revalidated the app uninstalled and reinstalled xcode tried increasing the application version/build version in xcode checked my version number consists of three integers (0.0.8, 0.0.9, etc) the xcode build ios/device is selected identical to the one installed on my mac m1 (iphone 15 pro max, ios 17.2) FYI This is the report i got after xcode crashed. Translated Report (Full Report Below) Process: Xcode [33912] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 15.3 (22618) Build Info: IDEApplication-22618000000000000~2 (15E204a) App Item ID: 497*** App External ID: 863*** Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 5** Date/Time: 2024-03-16 00:55:26.7732 +0900 OS Version: macOS 14.4 (23E214) Report Version: 12 ... System Integrity Protection: enabled Crashed Thread: 7 Dispatch queue: com.apple.root.default-qos Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Xcode [33912] Application Specific Information: abort() called Application Specific Signatures: success ==================================== Any type of help or advice is welcome. Thanks.

I received an email that says, although submission for TestFlight review was successful, you may want to correct the following issues in your next submission for TestFlight review. Once you've corrected the issues, upload a new binary to App Store Connect. I am aware of the one minor issue that needs to be corrected. Which we will upload soon. What I don't understand is that the email says that the Test review was successful but yet My status is still saying waiting for review. Can I get some clarification please....

Hello, during development of a simple game for iPhone and iPad, I'm using a Swift package to keep track of app launches — this does not collect any user-related information. Only the device model, iOS version and build version number are reported by the package, which automatically also includes the originating IP address. While looking at the Swift package reports, I'm seeing a few unexpected entries: launches from devices that do not belong to any testers (established by looking at the device models) launches from builds that have been expired in App Store Connect launches from IP addresses apparently from the Apple WAN (established by looking up the addresses via e.g. whois) A single public link to a TestFlight build was shared with a single group of testers — none of which have the device models described above in 1. This link has been expired as soon as I noticed the unexpected entries. But the entries keep coming, and they mostly coincide with new TestFlight builds — although the launches do not come from the new builds, but rather from older ones. Has anyone experienced something similar with TestFlight builds...? Thank you, D.

My archived xcode builds show that they have been successfully uploaded to testflight but once in the appstore they do not appear. Is there anyone else with the same problem?