I've been getting an error when I try to install an app uploaded to Testflight that says "Could not install AppName, the requested app is not available or does not exist", two weeks ago I uploaded an app and all fine, but uploaded again several and in different ways and still gives the same error, check everything and nothing has worked, I do not know if it is the xcode or operating system (I have mac os sonoma 14. 3.1), but everything is validated well and uploaded, the problem is that it does not install, I need help, I have tried everything and I do not know what to do.

Hey everyone, I'm aware that subscriptions purchased via TestFlight expire more quickly according to schedule dictated by the sandbox environment. But what about non-consumables? Can non-consumable purchases via TestFlight be refunded in any way? I've been looking around and can't find that information.

Anyone else having issues with uploading apps into Appstore Connect? I will upload them and everything will show successful. It will show on Testflight briefly, then disappear about 30-60seconds later. I know there was an issue last week for 3days but shows corrected. I have tried uploading with transport and also xcode directly.

Users on TestFlight have started seeing this crash. Any suggestions?

Hi, I am acting as a tester for an app being developed by an external contractor and have run into an issue recently. The contractor originally sent me a test flight invite to my corporate email. At the time I didn't have a corporate phone or Apple ID tied to my corporate email so I redeemed the test flight invite on my personal phone which is logged in with my personal Apple ID even though it was sent to my corporate email. This setup worked fine. I have since received a corporate phone and am trying to switch over and we are running into some issues. Because I didn't want to log into my corporate phone with my personal credentials at setup time, I created a new Apple ID with my corporate email address. This is the same address that was used above when testing on my personal phone. I had the developer send me a new invite as the original one was months old and no longer value, but every time I attempt to redeem it, I always received an "invalid or revoked" error. We have tried several things. They confirmed that they removed the original tester account (not sure if that's the right term) that was used with my personal phone before inviting me again and have since tried multiple times to invite me. So far none of the invites seem to work on either phone now. Appreciate any advice. Thanks. Mike

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?

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!

Hi, I would love to disable app sandbox completely, because my music application requires extended filesystem permissions. Like reading configuration files from $HOME and enabling services through sockets. The UI toolkit I am using endorses IPC mechanism. cheers, Joël

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?

My iOS Testflight App is crashing immediately after download/start (on all physical devices) iOS Console says: SwiftData/DataUtilities.swift:1093: Fatal error: Unable to parse keypath for non-PersistentModel Type The code is probably it is during self.modelContainer = try ModelContainer( for: Model1.self, Model2.self, Model3.self, Model4.self, configurations: ModelConfiguration(isStoredInMemoryOnly: isPreview)) modelContainer.mainContext.autosaveEnabled = true The app runs fine on physical devices in run scheme (debug or release) I have no clue how to solve this. Any ideas?

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

Xcode Cloud succeeds in building the Release configuration of the app, but whenever deployment preparation is set to "TestFlight and App Store" the last step fails with: ITMS-90035: Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “{AppName}.app/{AppName}” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing. When I build for release (with manual signing) everything works as expected and uploading to TestFlight for external testing works. I have tried to removed every imported framework, library, file etc. only keeping the bare minimum and still Xcode Cloud fails with the same error. I even created a new empty project but I still get the same error. My only guess is that something is off with the automatically generated certificates (or provisioning profiles) that Apple creates. Is there any way to figure out what specifically makes the signing fail? Is there a way to reset Xcode Cloud to clear all data and caches, revoke all certificates and remove all accosiated provisioning profiles?

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!

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.