I'm encountering an issue with my TestFlight builds that were uploaded and submitted for App Store review. After uploading my application to TestFlight, it was working fine for 10 days. However, one day after submitting the app for review, all the versions of my builds changed to expired. I'm unsure why this is happening, as the expiration date shown in my developer panel indicates that my builds should be valid for 80 days. I've also checked my distribution certificate and provisioning profile, and they are both still valid. This issue is concerning as I'm not sure if it will affect the App Store review process, and I have not received any feedback from the App Store review team yet. I'm also unsure if this issue is related to the expiration date shown in my developer panel or if there is some other underlying issue. Has anyone else experienced this issue with TestFlight builds expiring prematurely after submitting for App Store review? Is there anything I can do to resolve this issue and ensure that my app remains accessible on TestFlight? Any help or advice would be greatly appreciated. Thank you in advance for your assistance.

I have a managed workflow expo app which I am trying to submit to App Store. The build was successful but the submission from project directory (cannot use xCode due to managed workflow) fails with the error " Asset validation failed The app references non-public selectors in Payload/{appName}.app/{appName}: _isKeyDown, _modifiedInput, _modifierFlags My eas.json looks like this: { "cli": { "version": ">= 3.7.2" }, "build": { "development": { "distribution": "internal", "ios": { "resourceClass": "m1-medium" }, "developmentClient": true, "android": { "buildType": "apk", "gradleCommand": ":app:assembleRelease" } }, "preview": { "distribution": "internal", "ios": { "resourceClass": "m1-medium" }, "developmentClient": true, "android": { "buildType": "apk", "gradleCommand": ":app:assembleRelease" } }, "production": { "ios": { "resourceClass": "m1-medium" }, "developmentClient": true, "android": { "buildType": "apk", "gradleCommand": ":app:assembleRelease" } } }, "submit": { "production": { "ios": { "appleId": "******", "ascAppId": "******", "appleTeamId": "******", } } } } And my app.json like this: { "expo": { "name": "******", "slug": "******", "version": "1.0.1", "orientation": "portrait", "icon": "./assets/icon.png", "userInterfaceStyle": "light", "splash": { "image": "./assets/splash.png", "resizeMode": "contain", "backgroundColor": "#ffffff" }, "assetBundlePatterns": [ "**/*" ], "ios": { "supportsTablet": true, "bundleIdentifier": "******", }, "android": { "adaptiveIcon": { "foregroundImage": "./assets/adaptive-icon.png", "backgroundColor": "#ffffff" }, "package": "******", }, "web": { "favicon": "./assets/favicon.png" }, "extra": { "eas": { "projectId": "******", } }, "plugins": [ [ "expo-image-picker", { "photosPermission": "The app accesses your videos to let you share them with your friends." } ] ] } } I have no clue as to what goes wrong here and unfortunately all other solutions referencing this error refer to xCode settings which can be altered, but again not an option here since I am using the managed workflow of expo... Any help would be much appreciated!

I can receive the email for inviting me to join development team, and after I accept invitation, I was granted as the admin And then I invited myself to join the Internal Testing of TestFlight. But unfortunately whatever how many times I try to Resend Invite, I couldn't receive any email. Does anyone can help me with that?

Hello, I have a question regarding the presentCodeRedemptionSheet() function. I'm implementing an offer code input feature in a Unity app and currently testing it on TestFlight. However, when I tap the text field, the keyboard doesn't appear as shown in the attached image. If I flip the iPhone, the keyboard then shows up. Is this phenomenon specific to TestFlight or Sandbox? I am testing this issue on the following two environments, and the problem occurs in both cases. The iPhones are models sold in Japan. iPhone 11 Pro, iOS 16.4.1 iPhone 12 Pro, iOS 15.7.1 Any help or suggestions would be greatly appreciated. Thank you!

Hello everyone, I am no longer to access all of my TestFlight betas. I tried contacting Apple Support but they have not helped me with the situation. This message only started occurring a few days ago. I am running iOS 16.4.1 Message: TestFlight Unavailable Device vendor ID is missing or not available. Try again. Steps taken: -Deleted and re-installed Testflight App -Restarted iPhone 13 Pro Max Screenshot at imgur link below https://imgur.com/a/DJZJ5Y0 Any help would be appreciated to get TestFlight back up and running Thank-you, Shawn Osborne

I'm trying to test my IAP subscriptions. Testing in the Sandbox environment has been kind of a nightmare, because it sometimes returns out of date information on the phone and the server events are either never delivered or delivered very late, etc. It makes testing nigh impossible. So I'm trying to test via TestFlight, because that is, at least, working in the production environment and delivers events more quickly and seems to return the correct data when I query the StoreKit2 APIs. However, it's using my REAL Apple Id for the purchases (no charges though), and after it has auto-renewed my subscription 12 times... then it NEVER will auto-renew ever again (as far as I can tell). Even if I resubscribe, the subscription immediately dies at the end of that period. It's making testing impossible again... and I can't find a way to clear TestFlight purchases similar to the way I can clear purchases for Sandbox users. At this point, I have -no- confidence that my Apple IAP Subscriptions are going to work correctly and I don't seem to have a way that I can test them properly in order to gain that confidence. Is there any way to clear purchases in TestFlight or any way to allow more than 12 renewals in TestFlight?

Anyone is experiencing this issue? Today without any reason we can think of, all of our builds were expired on Testflight. Without knowing what happened, then we tried to add a new build, that it it seems to be in good shape on Testflight, even with the mark green meaning is ready to be tested. Even though, by trying to install the app on iOS using TF, we are getting a message saying "The requested app is not available"

Hi, Since yesterday (May 11, 2023) I can no longer send an update on TestFlight for the Apple Developer account of a client on which I am admin. It gives me the following error: The last time I sent a version to TestFlight was May 4, 2023 and I had no problem. With other client applications I have no problem sending my updates to TestFlight. I have no problem connecting to Apple Connect with my Apple ID, I can see that I am an admin on the Apple Developer account. My config: macOS 13.3.1 (a) Xcode Version 14.3 (14E222b) Regards Tof

I don't know how this happened or how to reset this, but I can't test the StoreKit part of my TestFlight app anymore. When I try to retrieve or buy products (IAPs), I get all kinds of strange behavior. I think it is caused by storekitagent thinking the app is in "Xcode sandbox environment". One of the errors from storekitagent looks like this: [51852D62] [LoadSubscriptionStatusTask]: Subscription status request failed with error - Error Domain=NSURLErrorDomain Code=-1003 "A server with the specified hostname could not be found." UserInfo={AMSStatusCode=0, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <468756B3-DA53-4FED-B35C-E093954C27D8>.<1>, NSErrorFailingURLKey=http://localhost:49828/inApps/subscriptions?guid=98DD60024C21&reason=push, _kCFStreamErrorDomainKey=10, _NSURLErrorRelatedURLSessionTaskErrorKey=( "LocalDataTask <468756B3-DA53-4FED-B35C-E093954C27D8>.<1>" ), NSLocalizedDescription=A server with the specified hostname could not be found., NSErrorFailingURLStringKey=http://localhost:49828/inApps/subscriptions?guid=98DD60024C21&reason=push, NSUnderlyingError=0x122f638d0 {Error Domain=kCFErrorDomainCFNetwork Code=-1003 "(null)" UserInfo={_NSURLErrorNWPathKey=satisfied (Path is satisfied), interface: lo0, _kCFStreamErrorCodeKey=-72000, _kCFStreamErrorDomainKey=10}}, _kCFStreamErrorCodeKey=-72000} It looks like it's trying to connect to a local server instead of contacting Apple's App Store servers. I'm on the latest macOS and Xcode. Any help is greatly appreciated:) Thanks!

I know i have a unhandled language exception error. But i am trying ro figure it out how to solve it becasue i can not run the app on xCode due to some ruby error with my OS system architecture. Incident Identifier: A011440F-61F1-455D-B86D-4C0E3983DD08 Hardware Model: iPhone15,3 Process: Lendy [19096] Path: /private/var/containers/Bundle/Application/4667EE27-D077-4D7E-A8D0-F28843A3A765/Lendy.app/Lendy Identifier: xxxxxxxxxxxxxxx Version: 1.0.0 (2) AppStoreTools: 14E221 AppVariant: 1:iPhone15,3:16 Beta: YES Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: xxxxxxxxxxx [11413] Date/Time: 2023-06-16 12:28:47.1227 -0300 Launch Time: 2023-06-16 12:28:46.8610 -0300 OS Version: iPhone OS 16.5 (20F66) Release Type: User Baseband Version: 1.70.02 Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Triggered by Thread: 1 Last Exception Backtrace: 0 CoreFoundation 0x19a1dccb4 _exceptionPreprocess + 164 (NSException.m:202) 1 libobjc.A.dylib 0x1932783d0 objc_exception_throw + 60 (objc-exception.mm:356) 2 Lendy 0x100c5a198 RCTFatal + 568 (RCTAssert.m:147) 3 Lendy 0x100ccd154 -[RCTExceptionsManager reportFatal:stack:exceptionId:extraDataAsJSON:] + 476 (RCTExceptionsManager.mm:77) 4 Lendy 0x100ccd998 -[RCTExceptionsManager reportException:] + 1292 (RCTExceptionsManager.mm:147) 5 CoreFoundation 0x19a245c04 invoking + 148 (:-1) 6 CoreFoundation 0x19a1f3cb4 -[NSInvocation invoke] + 428 (NSForwarding.m:3377) 7 CoreFoundation 0x19a1f36cc -[NSInvocation invokeWithTarget:] + 64 (NSForwarding.m:3474) 8 Lendy 0x100c88198 -[RCTModuleMethod invokeWithBridge:module:arguments:] + 388 (RCTModuleMethod.mm:584) 9 Lendy 0x100c8a310 facebook::react::invokeInner(RCTBridge*, RCTModuleData*, unsigned int, folly::dynamic const&, int, (anonymous namespace)::SchedulingContext) + 452 (RCTNativeModule.mm:183) 10 Lendy 0x100c89f98 facebook::react::RCTNativeModule::invoke(unsigned int, folly::dynamic&&, int)::$_0::operator()() const + 68 (RCTNativeModule.mm:104) 11 Lendy 0x100c89f98 invocation function for block in facebook::react::RCTNativeModule::invoke(unsigned int, folly::dynamic&&, int) + 112 (RCTNativeModule.mm:95) 12 libdispatch.dylib 0x1a16a1320 _dispatch_call_block_and_release + 32 (init.c:1518) 13 libdispatch.dylib 0x1a16a2eac _dispatch_client_callout + 20 (object.m:560) 14 libdispatch.dylib 0x1a16aa534 _dispatch_lane_serial_drain + 668 (queue.c:3885) 15 libdispatch.dylib 0x1a16ab0a4 _dispatch_lane_invoke + 384 (queue.c:3976) 16 libdispatch.dylib 0x1a16b5cdc _dispatch_workloop_worker_thread + 648 (queue.c:6507) 17 libsystem_pthread.dylib 0x1f9f84ddc _pthread_wqthread + 288 (pthread.c:2618) 18 libsystem_pthread.dylib 0x1f9f84b7c start_wqthread + 8 (:-1) Kernel Triage: VM - (arg = 0x0) pmap_enter retried due to resource shortage Thread 0 name: Thread 0: 0 libsystem_kernel.dylib 0x00000001d913fc84 mach_msg2_trap + 8 (:-1) 1 libsystem_kernel.dylib 0x00000001d9152b54 mach_msg2_internal + 80 (mach_msg.c:201) 2 libsystem_kernel.dylib 0x00000001d9152e2c mach_msg_overwrite + 540 (mach_msg.c:0) 3 libsystem_kernel.dylib 0x00000001d91401c8 mach_msg + 24 (mach_msg.c:323) 4 CoreFoundation 0x000000019a24c024 __CFRunLoopServiceMachPort + 160 (CFRunLoop.c:2622) 5 CoreFoundation 0x000000019a24d250 __CFRunLoopRun + 1208 (CFRunLoop.c:3005) 6 CoreFoundation 0x000000019a2523ec CFRunLoopRunSpecific + 612 (CFRunLoop.c:3418) 7 GraphicsServices 0x00000001d571735c GSEventRunModal + 164 (GSEvent.c:2196) 8 UIKitCore 0x000000019c5df6e8 -[UIApplication _run] + 888 (UIApplication.m:3782) 9 UIKitCore 0x000000019c5df34c UIApplicationMain + 340 (UIApplication.m:5372) 10 Lendy 0x0000000100b68cc0 main + 80 (main.m:7) 11 dyld 0x00000001b9752dec start + 2220 (dyldMain.cpp:1165) Thread 1 name: Thread 1 Crashed: 0 libsystem_kernel.dylib 0x00000001d9146558 __pthread_kill + 8 (:-1) 1 libsystem_pthread.dylib 0x00000001f9f8b118 pthread_kill + 268 (pthread.c:1670) 2 libsystem_c.dylib 0x00000001a1703178 abort + 180 (abort.c:118) 3 libc++abi.dylib 0x00000001f9ec9bf8 abort_message + 132 (:-1) 4 libc++abi.dylib 0x00000001f9eb9444 demangling_terminate_handler() + 348 (:-1) 5 libobjc.A.dylib 0x000000019327dea4 _objc_terminate() + 144 (objc-exception.mm:498) 6 libc++abi.dylib 0x00000001f9ec8fbc std::__terminate(void (*)()) + 16 (:-1) 7 libc++abi.dylib 0x00000001f9ec8f60 std::terminate() + 56 (:-1) 8 libdispatch.dylib 0x00000001a16a2ec0 _dispatch_client_callout + 40 (object.m:563) 9 libdispatch.dylib 0x00000001a16aa534 _dispatch_lane_serial_drain + 668 (queue.c:3885) 10 libdispatch.dylib 0x00000001a16ab0a4 _dispatch_lane_invoke + 384 (queue.c:3976) 11 libdispatch.dylib 0x00000001a16b5cdc _dispatch_workloop_worker_thread + 648 (queue.c:6507) 12 libsystem_pthread.dylib 0x00000001f9f84ddc _pthread_wqthread + 288 (pthread.c:2618) 13 libsystem_pthread.dylib 0x00000001f9f84b7c start_wqthread + 8 (:-1)

How can I test app without TestFlight?

Hi everyone I 'm trying to distribute my app with Testflight. When trying to submit a new build, I get the following errors: I 'm using Xcode 15 beta 2. Can anyone help me?

Hi, I am testing out an update for my app in macOS Sonoma. I first installed the App Store version of my app on the device running macOS Sonoma, and it ran fine. I then installed an updated version of my app through TestFlight (built with macOS Ventura SDK), but when I run this updated version, I get prompted ”MyApp differs from previously opened versions. Are you sure you want to open it?". Why is this happening? Is this warning only because the app is updated through TestFlight, or do I need to do something to prevent this warning from happening when I update my app through the App Store? I see this mentioned in an Apple security update:: App Sandbox now associates your macOS app with its sandbox container using its code signature. The operating system asks the person using your app to grant permission if it tries to access a sandbox container associated with a different app. For more information, see Accessing files from the macOS App Sandbox. My app is already sandboxed, and I'm not trying to access a different app's sandbox container, just my own. For the TestFlight build, it probably also uses the same Release configuration that the App Store build uses. I might have changed my provisioning profiles recently because they expired. Would that affect this and cause a prompt to be showed? Would love to know more about this prompt and how to avoid it. Thanks.

Hi, I have an existing Mac app that stores some important values in the keychain. I am working on an update for the app, which was working fine while I was testing with debug builds. But when I build the app for Release and test the update using TestFlight, on trying to access the keychain item, I get prompted by the system: "MyApp wants to use your confidential information stored in "SyncSettingsValue" in your keychain" And the user now has to enter their password and click on "Allow", "Always Allow" or Deny. Obviously this is a really bad experience, and clicking on Deny will stop many features for the user. Why is this happening? I've updated the app 100s of times before and I've never had this problem. I don't believe I'm messing around with any certificate or provisioning profile since the last update, which was only a few weeks ago. How do I find out what is causing the problem here? Or is this a TestFlight issue that won't happen to users when they update through the App Store?

Xcode: Version 15.0 beta 2 (15A5161b) iPhone: iOS 17.0 (21A5268h) Run from Xcode to Simulator or my iPhone, build successfully, install failed with the same error: My widget extension target info.plist file looks like the image below, and it worked find with all the previous Xcode version. After adding the key NSExtensionPrincipalClass like this: I can install my app to simaltor and my device, however, when archive and upload to the App Store (for TestFlight testing), i got another error (the first one is related to this issue, the second i could not figure out what it is):

Hello, I want to resend invite to internal testers in TestFlight because they haven't accepted the invitation. Unfortunately, when I click on the "Resend invite", a prompt is displayed asking me to confirm that I "want to resend this invite". The "Cancel" button of this prompt is working and unshow this confirmation. The "Resend" button seems to do not work. Nothing happens when we click on this button. Especially internal testers does not receive any invitation. I've already tried all of the following actions on Chrome and Safari : remove the tester from the group and reinvite him remove the entire group and reinvite all the testers create a new group Could you help me ?

Hello, I have a flutter project where my team is pushing changes for an ios app. We have tested locally with no issue and unit tested it. About a week ago we received the following error when we distribute the app. App Store Connect access for “******” is required. Add an account in the Accounts preference pane. Please try again, and if issue persists file a bug report at "https://feedbackassistant.apple.com." Our signing has not changed, nor has our permissions in the app. I have reached out to support several times and they literally said they aren't tech savvy and I should go here. With links too the code signing docs even though already had it booked marked. I get it, app markets are a pain on any platform. Do I have to resign again cause apple updated something? I am definitely not a fan of apple's code signing process. I would rather just automate this if there is a better solution. We tried CodeMagic but keep running into issues with that as well.

I wanted to bring to your attention an issue recently identified regarding the accessibility of existing production core data on our TestFlight app. Following the completion of a core data migration process, accessing the aforementioned production data has become temporarily unavailable on the TestFlight platform. If I install the testflight app getting a new instance of core data. whereas in production another instance of core data. respectively after lightweight migration data are not merging.

I regularly come across Mac developers who have an app in the Mac App Store but are unable to submit it to TestFlight. This post explains a common cause of that problem. If you have any questions or comments about this, start a new thread and tag it with Provisioning Profiles and TestFlight so that I see it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" TestFlight, Provisioning Profiles, and the Mac App Store A provisioning profile authorises a device to run your app. For historical reasons, not all Mac apps need a provisioning profile. A Mac app only needs a profile if it uses a restricted entitlement, that is, an entitlement that must be authorised by a profile. For more background on this, see TN3125 Inside Code Signing: Provisioning Profiles and, specifically, its Entitlements on macOS section. IMPORTANT Your Mac App Store apps must be signed with the App Sandbox Entitlement, but that entitlement is unrestricted. This means that many Mac App Store apps ship without a provisioning profile, and that’s absolutely fine. However, these apps run into problems with TestFlight. To submit an app to TestFlight, it must have a provisioning profile. If you attempt to submit an app without a profile to TestFlight, it’ll fail with an error like this: ITMS-90889: Cannot be used with TestFlight because the bundle at 'MyApp.app' is missing a provisioning profile. Main bundles are expected to have provisioning profiles in order to be eligible for TestFlight. The fix is to give your app a profile. How you do this depends on how you build your app. Fix an app built with Xcode If you build your app with Xcode, the fix is relatively straightforward: Sign your app with a restricted entitlement. This causes Xcode’s code signing machinery to kick in. If you have automatic code signing enable, Xcode will sort this all out for you. If you use manual signing, Xcode will highlight the problems you need to solve. A good restricted entitlement to use is the Keychain Access Groups Entitlement. Enable this by adding Keychain Sharing to the Signing & Capabilities editor for your app. You have two options here: Leave the Keychain Groups list empty. This will fix this problem while having no effect on any keychain code in your app. Use this as an opportunity to switch to the data protection keychain. In this case you might want to add one or more keychain access groups. For an explanation as to why you might want to switch to using the data protection keychain, see TN3137 On Mac keychain APIs and implementations. For more information about keychain access groups, see Sharing Access to Keychain Items Among a Collection of Apps Fix an app built outside of Xcode If you don’t use Xcode to build your app: Use Developer > Account > Identifiers to create an App ID for your app. Remember that your App ID is the combination of an App ID prefix and your app’s bundle ID. For new App IDs, use your Team ID as the App ID prefix. Use Developer > Account > Profiles to create a macOS App Development provisioning profile for that App ID. Use Developer > Account > Profiles to create a Mac App Store distribution provisioning profile for that App ID. Update your build system to embed a provisioning profile into your app. Use the profile from step 2 for development-signed builds and the one from step 3 for distribution-signed builds. For information about where to place the profile, see Placing Content in a Bundle. Add the following to your .entitlements: A com.apple.application-identifier property whose value is your App ID A com.apple.developer.team-identifier property whose value is your Team ID Build your app and check your work by dumping the entitlements claimed by your app and the entitlements authorised by your provisioning profile. For the specific commands to use, see TN3125 Inside Code Signing: Provisioning Profiles. WARNING In step 1, if your team has any unique App ID prefixes registered, the Developer website might default to using one of those legacy values rather than your Team ID (r. 70571514). If the App ID Prefix value is a popup, select your Team ID from the list. If the App ID value is a read-only copy of your Team ID, your team has no unique App ID prefixes, and so the Developer website always uses your Team ID as the App ID prefix. IMPORTANT In step 5, make sure that your .entitlements file is only applied to the app itself, not to any nested code. For more on this, see the Entitlements and Nested Code section below. Historically you might have been able to get away with using single .entitlements file for all your code. Once you start adding restricted entitlements, like com.apple.application-identifier, this bad practice will cause problems. For general information about how to sign and package apps outside of Xcode, see Creating Distribution-Signed Code for Mac and Packaging Mac Software for Distribution. Entitlements and Nested Code An App Store app might contain the following code; The app itself Nested libraries, like a framework or a dynamic library Nested executables, like a helper tool or an app extension Step 5 in the previous section specifically refers to the entitlements of the main app. When it comes to nested code, the first case is easy: Never add entitlements to nested libraries. It doesn’t do anything useful and can prevent your code from running. The story with nested executables is more nuanced. To start, every nested executable must be signed with at least one entitlement because: All App Store executables must be sandboxed. You enable the App Sandbox with the com.apple.security.app-sandbox entitlement. In many cases a nested executable only needs unrestricted entitlements, like com.apple.security.app-sandbox and com.apple.security.inherit. In that case the nested code doesn’t need a provisioning profile. If a nested executable uses restricted entitlements, it needs a provisioning profile to authorise the use of those entitlements, and its own unique App ID to tie the executable to the profile. Place this profile in the nested executable’s bundle, according to the rules in Placing Content in a Bundle. IMPORTANT The nested code can’t ‘piggyback’ off the app’s provisioning profile. It needs its own profile with its own unique App ID. Revision History 2023-08-17 Added the Entitlements and Nested Code section. Made other minor editorial changes. 2023-07-17 First posted.

I started building a new app with Xcode 15, and I uploaded a few builds to TestFlight with it. Now I'm trying with 15b4, and I'm getting: Invalid Toolchain. Your app was built with an unsupported SDK or version of Xcode. If you plan to submit this build to the App Store, make sure you are using the versions listed in https://help.apple.com/xcode/mac/current/#/devf16aefe3b or later. (ID: 0c544ce8-53ee-4122-b4a9-467a3d766349) Is this a bug? They've always allowed TestFlight builds with pre-release toolchans, havn't they? How else can you ensure your app is ready for the new OS version if you can't test changes to it?