When uploading the initial release, new builds are automatically removed from TestFlight

Hi there, I've successfully uploaded my app to App Store Connect using the Transporter app. However, it seems to be stuck in the processing state within App Store Connect. Despite uploading multiple builds, I haven't encountered any errors in my email notifications. Any insights on resolving this issue would be greatly appreciated. I am attaching a screenshot.

Regularly I invite several users to external testing and they receive an email with redeem code but when they enter the redeem code, an error message pop out show: "redeem code is expired", It is just a short time after the user is notified. Then my question is very simple but I don't find the answer: How long it takes for "the redeem code" on TestFlight expired?

suddenly getting this message for test flight installs what is going on?

I'm encountering an issue while attempting to upload my IPA to the App Store. The error message indicates a problem with the datatype of the cfBundleVersion attribute, stating that it's incorrect. Strangely, this was working fine until yesterday. It's the error log: 2024-02-09 22:16:35.852 INFO: Show Progress: Contacting Apple Services… 2024-02-09 22:16:36.729 *** Error: Error [REDACTED]ing '/Users/vagrant/deploy/[REDACTED] - Development.ipa'. 2024-02-09 22:16:36.730 *** Error: An attribute in the provided entity has the wrong type Unexpected json type provided for attribute 'cfBundleVersion'. Expected a STRING but got INTEGER (ID: xxxxx) (409) { NSLocalizedDescription = "An attribute in the provided entity has the wrong type"; NSLocalizedFailureReason = "Unexpected json type provided for attribute 'cfBundleVersion'. Expected a STRING but got INTEGER (ID: xxxxx)"; "original_server_error" = { code = "ENTITY_ERROR.ATTRIBUTE.TYPE"; detail = "Unexpected json type provided for attribute 'cfBundleVersion'. Expected a STRING but got INTEGER"; id = "xxxxx", source = { pointer = "/data/attributes/cfBundleVersion"; }; status = 409; title = "An attribute in the provided entity has the wrong type"; }; } Uploading IPA failed: exit status 1 Here's the relevant snippet from my Info.plist: <string>74</string> I've built the iOS app using React Native and deployed it via Bitrise. Any insights into why this error might be occurring and how to resolve it would be greatly appreciated. Thank you!

Using 1.1 beta 1, I am unable to download TestFlight from the App Store. All other apps work, including VisionOS and iPhone and iPadOS. Logging out / back in and rebooting the device didn't fix this. Anyone find a way to resolve this?

What is the solution here? Without access to the App Store we can't install TestFlight? Do we need to create a US account to use TestFlight?

We've been using React Native and Expo Go to develop a mobile application, however when building and testing using TestFlight, we run into an unexpected error where the app crashes after interacting with one button but that same button doesn't crash in Expo Go. (To add, we have 2 buttons on a screen, both which do very similar actions but only one crashes in TestFlight.) Below is the error log with some stack traces. Anyone else experience something similar to this? Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Terminating Process: ClimateFund [5827] Triggered by Thread: 2 Application Specific Information: abort() called Last Exception Backtrace: 0 CoreFoundation 0x198ee269c __exceptionPreprocess + 164 1 libobjc.A.dylib 0x191177c80 objc_exception_throw + 60 2 ClimateFund 0x100a34fd4 0x1008e8000 + 1363924 3 ClimateFund 0x100aa32b0 0x1008e8000 + 1815216 4 ClimateFund 0x100aa3ae4 0x1008e8000 + 1817316 5 CoreFoundation 0x198e27794 __invoking___ + 148 6 CoreFoundation 0x198e2722c -[NSInvocation invoke] + 428 7 CoreFoundation 0x198e27054 -[NSInvocation invokeWithTarget:] + 64 8 ClimateFund 0x100a644c4 0x1008e8000 + 1557700 9 ClimateFund 0x100a66514 0x1008e8000 + 1565972 10 ClimateFund 0x100a66164 0x1008e8000 + 1565028 11 libdispatch.dylib 0x1a0deb6a8 _dispatch_call_block_and_release + 32 12 libdispatch.dylib 0x1a0ded300 _dispatch_client_callout + 20 13 libdispatch.dylib 0x1a0df4894 _dispatch_lane_serial_drain + 748 14 libdispatch.dylib 0x1a0df53c4 _dispatch_lane_invoke + 380 15 libdispatch.dylib 0x1a0e00004 _dispatch_root_queue_drain_deferred_wlh + 288 16 libdispatch.dylib 0x1a0dff878 _dispatch_workloop_worker_thread + 404 17 libsystem_pthread.dylib 0x202e1b964 _pthread_wqthread + 288 18 libsystem_pthread.dylib 0x202e1ba04 start_wqthread + 8 Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0: 0 libsystem_kernel.dylib 0x1e0555178 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x1e0554f10 mach_msg2_internal + 80 2 libsystem_kernel.dylib 0x1e0554e28 mach_msg_overwrite + 436 3 libsystem_kernel.dylib 0x1e0554c68 mach_msg + 24 4 CoreFoundation 0x198e2bb1c __CFRunLoopServiceMachPort + 160 5 CoreFoundation 0x198e29a14 __CFRunLoopRun + 1208 6 CoreFoundation 0x198e29478 CFRunLoopRunSpecific + 608 7 GraphicsServices 0x1dc3aa4f8 GSEventRunModal + 164 8 UIKitCore 0x19b24d62c -[UIApplication _run] + 888 9 UIKitCore 0x19b24cc68 UIApplicationMain + 340 10 ClimateFund 0x1008efa3c 0x1008e8000 + 31292 11 dyld 0x1bbb62dcc start + 2240 Thread 1: 0 libsystem_pthread.dylib 0x202e1b9fc start_wqthread + 0 Thread 2 name: Dispatch queue: com.facebook.react.ExceptionsManagerQueue Thread 2 Crashed: 0 libsystem_kernel.dylib 0x1e055dfbc __pthread_kill + 8 1 libsystem_pthread.dylib 0x202e1f680 pthread_kill + 268 2 libsystem_c.dylib 0x1a0ea5b90 abort + 180 3 libc++abi.dylib 0x202d49ff8 abort_message + 132 4 libc++abi.dylib 0x202d39f90 demangling_terminate_handler() + 348 5 libobjc.A.dylib 0x19117ada4 _objc_terminate() + 144 6 libc++abi.dylib 0x202d493bc std::__terminate(void (*)()) + 16 7 libc++abi.dylib 0x202d49360 std::terminate() + 108 8 libdispatch.dylib 0x1a0ded314 _dispatch_client_callout + 40 9 libdispatch.dylib 0x1a0df4894 _dispatch_lane_serial_drain + 748 10 libdispatch.dylib 0x1a0df53c4 _dispatch_lane_invoke + 380 11 libdispatch.dylib 0x1a0e00004 _dispatch_root_queue_drain_deferred_wlh + 288 12 libdispatch.dylib 0x1a0dff878 _dispatch_workloop_worker_thread + 404 13 libsystem_pthread.dylib 0x202e1b964 _pthread_wqthread + 288 14 libsystem_pthread.dylib 0x202e1ba04 start_wqthread + 8

Hello, we have a pretty big macOS pkg (12 GB) that we upload on AppStoreConnect. When uploading manually via Transporter, everything works perfectly, but when we are automating this upload in script (via "xcrun altool --upload-app --apiKey"), the upload starts correctly, but we end up having an error after around 25 minutes. Setting request length to: 511 Web service call (lookupSoftwareForBundleId) result: { ErrorCode = 401; ErrorMessage = "Failure to authenticate."; Errors = ( "Failure to authenticate." ); NSUnderlyingError = "Error Domain=MZJSONServiceClientErrorDomain Code=401 \"Failure to authenticate.\" \U2026"; } When reducing the package size (to around 6GB), the same script runs perfectly. Anyone else has that problem, or even better, a solution?

Hi, I left a team some time back, so I have no access to any developer privileges anymore, as intended. However, I continue to get automatic TestFlight emails about new updates the current devs are making. If I click the unsubscribe link at the bottom of the email it just generates an email with my OWN address in the TO field, which is ridiculous, as I have no access to the project. I do not even have the email of the current developer, so I don't have a practical recourse here. Please fix this Apple!

If I try to run Instrument's logger for an app downloaded from TestFlight it says "Permission to debug app name was denied". "Recover Suggestion: The app must be debuggable and signed with 'get-task-allow'. How do you make the app debuggable? (I tried creating an archive with the scheme set to Debug, but after uploading that to TestFlight, it doesn't appear. So presumably its not possible to upload an app built with debug scheme builds to TF?). Therefore how can I make a TF build debuggable?, and how to sign it with get-task-allow? Does it have to be a developer distribution .ipa rather than a TestFlight build to enable Instruments/Logger to run it?

Hello, this morning logged in to my app store connect developer account and its all blank, no apps is present. THanks!

I have two release trains going in TestFlight: The App Store version v1.0(0) with bug fixes v1.0(1), v1.0(2), etc. The next feature version with additional functionalities of the app v1.1(0), v1.1(1), v1.1(2), etc. Is there any way to have v1.0(x) be for internal testing, and have v1.1(x) be for external testing? I really need to start external testing the next release of the app in TestFlight, while also bug fixing the current version of the app in TestFlight. Thanks!

Hi, I build my application bundle by makefile and later using productbuild to create an application installer. This works fine. But as uploading it to apple using Transporter I get these 2 error messages. #01 error message: Asset validation failed (90242) The product archive is invalid. The Info.plist must contain a LSApplicationCategoryType key, whose value is the UTI for a valid category. For more details, see "Submitting your Mac apps to the App Store". (ID: f25a48a4-8e89-4824-9f22-a6bc2fb90193) #02 error message: Asset validation failed (90259) Bad Bundle Executable. You must include a valid CFBundleExecutable key in your bundle's information property list file. (ID: c3d9f35a-5a27-4cc6-bba8-56cf514c3ad9) Here is my Info.plist <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>CFBundleDevelopmentRegion</key> <string>English</string> <key>CFBundleExecutable</key> <string>GSequencer</string> <key>CFBundleGetInfoString</key> <string>6.4.3, Copyright 2005-2024 Joel Kraehemann</string> <key>CFBundleIconFile</key> <string>GSequencer.icns</string> <key>CFBundleIdentifier</key> <string>com.gsequencer.GSequencer</string> <key>CFBundleInfoDictionaryVersion</key> <string>6.0</string> <key>CFBundlePackageType</key> <string>APPL</string> <key>CFBundleShortVersionString</key> <string>6.4.3</string> <key>CFBundleSignature</key> <string>????</string> <key>CFBundleVersion</key> <string>6.4.3</string> <key>NSHumanReadableCopyright</key> <string>Copyright 2005-2024 Joel Kraehemann, GNU General Public License.</string> <key>LSMinimumSystemVersion</key> <string>11.0</string> </dict> </plist> Here are the 2 binaries in MacOS directory: ls -1 gsequencer-macos/build/universal/GSequencer.app/Contents/MacOS/ GSequencer gsequencer_macos_install Please help me to fix. regards, Joël

Hi, All of my TestFlight builds expired themselves and I can't submit any new builds for external testing. The general error message I see is "There was an error processing your request. Please try again later." and looking at the console I see a more specific error "API Response Error: TF_BETA_APP_REVIEW_RESPONSE". I've sent a couple of emails to support but I haven't heard anything back yet. What's going on with App Store Connect these days? It's so unreliable.

I'm really new into Development I have macos App I upload 2 builds to TestFlight were working Fine But the Third Build Crashed on TestFlight user Machine but on my machine working just fine from Xcode or TestFlight on my machine. Appreciate if someone helped here is crashlog: Process: Shaheed [814] Path: /Applications/Shaheed.app/Contents/MacOS/Shaheed Identifier: com.inno.Shaheed Version: 0.1 (4) App Item ID: 6474969425 Code Type: ARM-64 Parent Process: launchd [1] User ID: 501 Date/Time: 2024-02-05 20:19:32.6035 +0300 OS Version: macOS 14.2.1 (23C71) Report Version: 12 Anonymous UUID: Time Awake Since Boot: 270 seconds System Integrity Protection: enabled Crashed Thread: 0 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x000000019d3c51e8 Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5 Terminating Process: exc handler [814] Thread 0 Crashed: 0 libswiftCore.dylib 0x000000019d3c51e8 _assertionFailure(_:_:file:line:flags:) + 268 (AssertCommon.swift:144) 1 SwiftData 0x00000001fed53e08 specialized static ModelContainer.currentContainer(_:) + 920 (ModelContainer.swift:144) 2 SwiftData 0x00000001fedd02d4 _DefaultBackingData.init(for:) + 364 (BackingData.swift:106) 3 SwiftData 0x00000001fedd50f0 _DefaultBackingData.__allocating_init(for:) + 60 4 SwiftData 0x00000001fed8aec0 static PersistentModel.createBackingData<A>() + 76 (PersistentModel.swift:42) 5 Shaheed 0x00000001026d9670 specialized ItemSD.init(id:supplierName:purchaseDate:unit:currency:name:quantity:price:salePrice:itemID:floor:container:cell:) + 576 (@__swiftmacro_7Shaheed6ItemSD5ModelfMm_.swift:2) 6 Shaheed 0x0000000102707798 ItemSD.init(id:supplierName:purchaseDate:unit:currency:name:quantity:price:salePrice:itemID:floor:container:cell:) + 100 (ItemModel.swift:0) 7 Shaheed 0x0000000102707798 ItemSD.__allocating_init(id:supplierName:purchaseDate:unit:currency:name:quantity:price:salePrice:itemID:floor:container:cell:) + 124 (ItemListView.swift:39) 8 Shaheed 0x0000000102707798 closure #1 in closure #2 in closure #1 in ItemListView.body.getter + 532 9 SwiftUI 0x00000001b9a7ac30 NavigationStack.init<>(root:) + 128 (NavigationStack.swift:126) 10 Shaheed 0x0000000102707574 closure #2 in closure #1 in ItemListView.body.getter + 92 (ItemListView.swift:38) 11 SwiftUI 0x00000001b9483a2c closure #1 in SheetPresentationModifier.body(content:) + 188 (SheetPresentation.swift:277) 12 SwiftUI 0x00000001b94835e4 SheetPresentationModifier.body(content:) + 960 (SheetPresentation.swift:276) 13 SwiftUI 0x00000001b881776c ModifierBodyAccessor.updateBody(of:changed:) + 1560 (CustomViewModifier.swift:293) 14 SwiftUI 0x00000001b9fca69c closure #1 in DynamicBody.updateValue() + 564 (DynamicProperty.swift:453) 15 SwiftUI 0x00000001b9fca214 DynamicBody.updateValue() + 664 (DynamicProperty.swift:445) 16 SwiftUI 0x00000001b9a4cb6c partial apply for implicit closure #1 in closure #1 in closure #1 in Attribute.init<A>(_:) + 32 (<compiler-generated>:0) 17 AttributeGraph 0x00000001ba5837a4 AG::Graph::UpdateStack::update() + 512 (ag-graph-update.cc:578) 18 AttributeGraph 0x00000001ba583fe0 AG::Graph::update_attribute(AG::data::ptr<AG::Node>, unsigned int) + 424 (ag-graph-update.cc:719) 19 AttributeGraph 0x00000001ba592828 AG::Subgraph::update(unsigned int) + 848 (ag-subgraph.cc:752) 20 SwiftUI 0x00000001b9e8a2dc GraphHost.flushTransactions() + 384 (GraphHost.swift:617) 21 SwiftUI 0x00000001b9e8b7c0 closure #1 in closure #1 in closure #1 in closure #1 in GraphHost.asyncTransaction<A>(_:id:mutation:style:mayDeferUpdate:) + 24 (GraphHost.swift:540) 22 SwiftUI 0x00000001b95345ec partial apply for closure #1 in ViewGraphDelegate.updateGraph<A>(body:) + 28 (<compiler-generated>:0) 23 SwiftUI 0x00000001b9f60e84 closure #1 in ViewRendererHost.updateViewGraph<A>(body:) + 108 (ViewRendererHost.swift:139) 24 SwiftUI 0x00000001b9f5f6e0 ViewRendererHost.updateViewGraph<A>(body:) + 96 (ViewRendererHost.swift:136) 25 SwiftUI 0x00000001b952cdb4 ViewGraphDelegate.updateGraph<A>(body:) + 84 (ViewGraph.swift:34) 26 SwiftUI 0x00000001b9e8b788 closure #1 in closure #1 in closure #1 in GraphHost.asyncTransaction<A>(_:id:mutation:style:mayDeferUpdate:) + 200 (GraphHost.swift:539) 27 SwiftUI 0x00000001b9e8b674 closure #1 in closure #1 in GraphHost.asyncTransaction<A>(_:id:mutation:style:mayDeferUpdate:) + 72 (GraphHost.swift:538) 28 SwiftUI 0x00000001b97dc464 thunk for @escaping @callee_guaranteed () -> () + 28 (<compiler-generated>:0) 29 SwiftUI 0x00000001b8db3778 static NSRunLoop.flushObservers() + 116 (StandardLibraryAdditions.swift:903) 30 SwiftUI 0x00000001b8db36e4 closure #1 in static NSRunLoop.addObserver(_:) + 36 (StandardLibraryAdditions.swift:878) 31 SwiftUI 0x00000001b8db380c @objc closure #1 in static NSRunLoop.addObserver(_:) + 56 (<compiler-generated>:0) 32 CoreFoundation 0x000000018dbbadf0 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36 (CFRunLoop.c:1789) 33 CoreFoundation 0x000000018dbbacdc __CFRunLoopDoObservers + 532 (CFRunLoop.c:1902) 34 CoreFoundation 0x000000018dbb99f8 CFRunLoopRunSpecific + 684 (CFRunLoop.c:3423) 35 HIToolbox 0x0000000198168448 RunCurrentEventLoopInMode + 292 (EventLoop.c:455) 36 HIToolbox 0x00000001981680d8 ReceiveNextEventCommon + 220 (EventBlocking.c:311) 37 HIToolbox 0x0000000198167fdc _BlockUntilNextEventMatchingListInModeWithFilter + 76 Sorry for this long crashlog

+1 to everyone here. While the thread has been viewed thousands of times, there aren't really that many actual posts (and that's across 6+ years) so I wonder if this is a much smaller issue than it seems. Alternatively, I wonder if this isn't the right place to file this issue in the first place. To rule out the latter possibility, I went ahead and opened a ticket to Apple via the Feedback Assistant (case ID FB13585955) where I also referenced this thread. If I hear back from them (not sure how public the feedback tickets are), I'll try to update this thread with the findings. Even if this issue doesn't affect many developers, I hope Apple will at least provide us with some debug steps. Otherwise, it's just educated guesses, which is very time-consuming (and wasteful).

I'm analyzing an app which is doing some processing with contacts, and stress testing it with tens and tens of thousands of contacts which are being processed. The code is being processed within DispatchQueue.global(qos: .background).async {) When the app moves to the foreground the processing starts and continues after the app moves to the background. What I've noticed is that if the app is downloaded from TestFlight, then ~20 seconds after moving to the background, a dialog is displayed saying the App Crashed. Though it hasn't actually "crashed" in the usual sense of crash - there's no crash log present on the device nor in TestFlight if the crash is reported nor is there anything reported to Crashlytics. In addition the is still displayed in the iPhone task manager, also ApplicationWillTerminate() isn't called so it wasn't killed by the OS. This doesn't happen if the app is installed via Xcode and then run (not run via Xcode, installed via Xcode, then run independently from Xcode). When running via TestFlight installation I can see the OS logging" ReportCrash recordCrashEvent; isBeta 1 app stored Received a beta app crash notification. What's going on here, why is TestFlight reporting this? Is it erroneously reporting the background processing after 20 seconds as a crash? Is there anything the app should be doing in this situation that it isn't? Otherwise why is TF popping up that dialog?

I'm trying to add a member of my team to the Testlfight app because they're saying that they were removed. If I go to the Testflight group and try to add them there, they don't show up in the list despite being a tester. If I try to add them as a tester by finding them in "All Testers", selecting them, and doing "Add to group", I get the error: "An error has occurred. Try again later." The API request and response looks like this: Request URL: https://appstoreconnect.apple.com/iris/v1/betaGroups/[redacted uuid]/relationships/betaTesters Request Method: POST Status Code: 409 Conflict Response: { "errors" : [ { "id" : "7d7f28bc-60e5-438e-9a29-f17e14b533bc", "status" : "409", "code" : "STATE_ERROR", "title" : "The request cannot be fulfilled because of the state of another resource.", "detail" : "Tester(s) cannot be assigned" } ] } I don't think this person was ever removed, so it looks like their account is stuck in a state where they're in the group but also not in the group. Any ideas for a fix?

We submitted our app last night for review with version number 7.22.1 (binary has MARKETING_VERSION = 7.22.1). While in the review queue, we continued development on a feature for the next release (7.22.2). We then finished development of the feature, and uploaded the build to App Store Connect so we could send it via test flight to our QA team. (using fastlane deliver code snippet below) This appears to have automatically updated the version number of the app in status "Waiting for Review" to 7.22.2, although the build associated appears to still be the binary with MARKETING_VERSION = 7.22.1. As of this morning the app was reviewed and approved with binary of 7.22.1 but the app store connect version number says 7.22.2. Apple Support wasn't that helpful, they didn't seem to grasp the exact sequence of events. They also told me I had no choice but to release 7.22.2 as the version code. Thankfully they were incorrect, we were able to cancel the release, decrement the version down to 7.22.1 again, and resubmit for review. Has anyone else experienced this? Is it to be expected that an app version currently in review would automatically have its version number changed if a separate build is uploaded to App Store Connect? Below are the automated emails from App Store Connect which highlight the issue we observed: 8:06 PM The status of your app has changed to Waiting for Review. App Version Number: 7.22.1 1:54 AM The following build has completed processing: Platform: iOS Build Number: 4 Version Number: 7.22.2 3:39 AM The status of your app has changed to In Review. App Version Number: 7.22.2 6:23 AM The status of your app has changed to Pending Developer Release. App Version Number: 7.22.2 Fastlane Deliver code snippet: deliver( api_key: api_key, skip_screenshots: true, skip_metadata: true, ignore_language_directory_validation: true, precheck_include_in_app_purchases: false, submit_for_review: false, force: true )