TestFlight

RSS for tag

TestFlight within App Store Connect allows you to invite and manage testers who can install and beta test your iOS, iPadOS, tvOS, and watchOS apps using the TestFlight app on the App Store.

Posts under TestFlight tag

201 Posts

Post

Replies

Boosts

Views

Activity

TestFlight Public Links on the forums
TestFlight Public Links are a great way to share beta versions of your apps with other members of the Apple Developer Program. With this new channel, you can share your TestFlight Public Links with the developer community, to gather valuable feedback on crucial elements, like technical implementation, user experience, design, and more. To maximize the benefits of posting TestFlight Public Links in the Developer Forums, here are some best practices to keep in mind: Provide details: Give comprehensive information about your app, like new features and test cases, and note specific areas where you seek feedback. The more detailed your post is, the better equipped the community will be to provide insight. Select platforms: Select the platforms that your beta app supports. Enter categories: Enter the App category you’ve selected or plan to select for your app on the App Store. Categories are critical to ensuring your post can be easily found by interested users. Stay connected with notifications: Enable web and push notifications so you’ll know when you receive feedback on your post. Note: The TestFlight app is still the most comprehensive way to gather feedback. This space is meant as a helpful secondary channel.
0
0
4.1k
Aug ’23
Testflight Beta Information Validation Wrong
Hello, I want to add an external test, but I encountered an error when creating the test information. The error message shows that the phone field needs to be filled with only numbers. The following is the error screen This page has one or more errors. Please make sure the contact phone number contains only numbers and try again. Cannot save name because there are other invalid fields. Cannot save last name because there are other invalid fields. Could not save email because there are other invalid fields. Has anyone else encountered the same situation? Thanks.
5
7
8.3k
26m
There was an error processing your request. Please try again later
Hello everyone, on August 31st, all the apps in my personal developer account were suddenly expired and deleted, I have not received any response from Apple. My apps are in compliance with Apple's policies. I then uploaded a new version and sent it to the review team, but I received the following error "There was an error processing your request. Please try again later." I have contacted Apple via Email and Phone but no one cares about my problem. Has anyone had the same situation as me, I am really worried.
6
2
865
3h
Validation error, when I try to upload a game to Testflight
Hello everyone and thank you for you're time! I got an issue with uploading several icons to testflight. I'm using Game Maker Studio as my engine for the game. This is the error that I'm getting, even when I try to use the old icons for the game, that worked in the past. I tried to transform the icons, using this site "https://makeappicon.com/", but I still got the same validation error. Can you help me fixing the issue - thank you so much!
0
0
74
13h
App getting Crashed in Test Flight
The issue arises only when the .ipa is uploaded to App Store Connect via Xcode. When attempting to download the app through TestFlight, it crashes. This behaviour is isolated to TestFlight and does not occur in any other environment. To clarify the issue: the build is successfully running in Xcode across all iOS devices and versions without any problems. Additionally, the same production .ipa file downloaded from Firebase is functioning as expected.
0
0
4
17h
App icon not showing in TestFlight and App Store Connect, but visible on device
Hi everyone, we are currently facing an issue with one of our apps regarding the new icon requirements in iOS 26. • We created the app icon using Apple’s Icon Composer. • On the device, everything works perfectly: the app icon is shown on the home screen, and it can also be customized with the new iOS 26 features (colors, transparency, etc.). • However, in TestFlight the app icon is not displayed at all (in the TestFlight app on the device). • In App Store Connect, the icon is also not shown in the overview for the app. Interestingly, within the list of TestFlight builds in App Store Connect the icon is visible. What we have tried so far: • Created an archive and manually uploaded it to App Store Connect → no icon in TestFlight. • Took the working Icon Composer asset from another app target where everything works correctly, deleted the old one in this project, and copied the working asset into the problematic target. → Same behavior: visible on the device, but still missing in TestFlight and App Store Connect overview. In contrast, in another app (using the same workflow and also Icon Composer), everything works perfectly: the icon shows up on the device, in TestFlight, and in App Store Connect. Has anyone experienced a similar situation? Is there something specific that needs to be set in App Store Connect (e.g. Marketing Icon / Branding section), or could this be related to the new iOS 26 icon handling? Any help or hints would be greatly appreciated. Thanks in advance!
6
3
182
21h
Couldn't redeem TestFlight invitation code
I cannot add myself as a TestFlight user to my own app. When I open the invite link on my device, or manually enter the redeem code on device (obtained from opening the invite link on macOS), I get "This invitation has been revoked or is invalid". I've tried going to App Store Connect and removing myself from both the testing group and the list of 'All testers', both to no avail. Apple folks: this is not user error and you must have thousands of bug reports on this by now. Why don't you prioritize a fix for this incredibly annoying issue?
1
3
865
1d
TestFlight unable to install own application
Hi, I am facing a very weird issue where I am unable to download our own application from TestFlight for testing. This issue only happens for one of our applications; we are able to download our other applications without any issues. Furthermore, this only happens on one of our MacBooks; the game downloads fine on our other MacBook (macOS 15) and can run our application. When running the console, I noticed this error being thrown when the TestFlight fails the download: I have tried reinstalling TestFlight, clearing all instances of our application as what Finder can find, restarting the MacBook but nothing worked. Is there anyone that faced this similar issue, or any Apple staff that could help with this? OS version: macOS Tahoe (26 Beta) latest TestFlight was able to download on this version previously, until one day it couldn't (and not sure why), tried downloading latest version but did not solve the issue. Note: We noticed that we are unable to install our own application from the Appstore as well, on this MacBook that has the TestFlight issue.
13
6
528
1d
Step-by-step instructions on how to send an app to external testers with TestFlight in 2024?
New Apple Developer here, I've built my first iOS app in Xcode and wants to get it onto some friends' iPhones to do some external testing and give me some feedback. I've read the Apple Developer documentation on how to use TestFlight, but it's not understandable since step 1 is entering information about the app in App Store Connect and step 2 is uploading the app to App Store Connect? Can someone please write some easy step-by-step directions on how to get an iOS app from Xcode onto external testers' iPhones for a first-timer in 2024? Thank you so much!
1
1
726
1d
TestFlight app crashes since iOS 26 released
App builds fine locally on iPad. Once released to TestFlight, the app crashes on startup. Can't even release previous builds to TestFlight that worked fine before iOS 26. Using .net Maui 8.0.413 and Xcode 16.4. IpadOS 18.6 Crash log: Incident Identifier: 2183463F-CAFD-4E0C-95FB-8E56876118E9 Distributor ID: com.apple.TestFlight Hardware Model: iPad15,7 Process: VS_NASCO_Auscultation [3576] Path: /private/var/containers/Bundle/Application/062FE418-9CD6-4509-B368-5FD6465FF1F9/VS_NASCO_Auscultation.app/VS_NASCO_Auscultation Identifier: com.NASCO.Auscultation Version: 2.8.04 (20) AppStoreTools: 17A323 AppVariant: 1:iPad15,7:18 Beta: YES Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: com.NASCO.Auscultation [2590] Date/Time: 2025-09-22 14:31:29.9710 -0500 Launch Time: 2025-09-22 14:31:27.7714 -0500 OS Version: iPhone OS 18.6 (22G86) Release Type: User Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Terminating Process: VS_NASCO_Auscultation [3576] Triggered by Thread: 0 Thread 0 Crashed: 0 libsystem_kernel.dylib 0x00000001df60f1dc __pthread_kill + 8 1 libsystem_pthread.dylib 0x0000000218bf0c60 pthread_kill + 268 (pthread.c:1721) 2 libsystem_c.dylib 0x0000000196e9a0ac abort + 124 (abort.c:122) 3 VS_NASCO_Auscultation 0x0000000105157294 0x102e5c000 + 36680340 4 VS_NASCO_Auscultation 0x00000001050cb930 mono_runtime_setup_stat_profiler + 0 (mini-posix.c:690) 5 libsystem_platform.dylib 0x0000000218b40a68 _sigtramp + 56 (sigtramp.c:116) 6 libsystem_pthread.dylib 0x0000000218bf0c60 pthread_kill + 268 (pthread.c:1721) 7 libsystem_c.dylib 0x0000000196e9a0ac abort + 124 (abort.c:122) 8 VS_NASCO_Auscultation 0x0000000104f91170 mono_log_write_os_log + 408 (mono-log-darwin.c:0) 9 VS_NASCO_Auscultation 0x0000000104f8644c monoeg_g_logv + 172 (goutput.c:173) 10 VS_NASCO_Auscultation 0x0000000104f86594 monoeg_g_log + 28 (goutput.c:184) 11 VS_NASCO_Auscultation 0x00000001050a5f84 load_aot_module + 3172 (aot-runtime.c:2365) 12 VS_NASCO_Auscultation 0x0000000104fe4f48 mono_assembly_request_load_from + 1104 (assembly.c:2020) 13 VS_NASCO_Auscultation 0x0000000104fe4a68 mono_assembly_request_open + 472 (assembly.c:1625) 14 VS_NASCO_Auscultation 0x0000000104fe5cec mono_assembly_open + 80 (assembly.c:1828) 15 VS_NASCO_Auscultation 0x0000000104e1a0ac xamarin_assembly_preload_hook + 884 (monotouch-main.m:157) 16 VS_NASCO_Auscultation 0x0000000104fe6800 invoke_assembly_preload_hook + 64 (assembly.c:1283) 17 VS_NASCO_Auscultation 0x0000000104fe41e4 mono_assembly_request_byname + 1060 (assembly.c:2786) 18 VS_NASCO_Auscultation 0x00000001050af2e0 load_image + 280 (aot-runtime.c:325) 19 VS_NASCO_Auscultation 0x00000001050a5f1c load_aot_module + 3068 (aot-runtime.c:2358) 20 VS_NASCO_Auscultation 0x00000001050aa71c mono_aot_get_method + 292 (aot-runtime.c:4920) 21 VS_NASCO_Auscultation 0x000000010509e924 mono_jit_compile_method_with_opt + 472 (mini-runtime.c:2759) 22 VS_NASCO_Auscultation 0x000000010509cd10 mono_jit_runtime_invoke + 572 (mini-runtime.c:3525) 23 VS_NASCO_Auscultation 0x0000000105044b74 mono_runtime_invoke_checked + 148 (object.c:2792) 24 VS_NASCO_Auscultation 0x0000000105001720 create_exception_two_strings + 592 (exception.c:177) 25 VS_NASCO_Auscultation 0x00000001050014a4 mono_exception_from_name_two_strings_checked + 148 (exception.c:236) 26 VS_NASCO_Auscultation 0x0000000104fe0ab0 mono_runtime_init_checked + 708 (appdomain.c:288) 27 VS_NASCO_Auscultation 0x000000010509c64c mini_init + 6648 (mini-runtime.c:4889) 28 VS_NASCO_Auscultation 0x00000001050a3ad8 mono_jit_init_version + 20 (driver.c:2823) 29 VS_NASCO_Auscultation 0x0000000104e157ac xamarin_bridge_initialize + 216 (monovm-bridge.m:88) 30 VS_NASCO_Auscultation 0x0000000104e1a968 xamarin_main + 1784 (monotouch-main.m:438) 31 VS_NASCO_Auscultation 0x00000001051033ec main + 72 (main.arm64.mm:236) 32 dyld 0x00000001b58e5f08 start + 6040 (dyldMain.cpp:1450) Thread 1: 0 libsystem_pthread.dylib 0x0000000218be9aa4 start_wqthread + 0 Thread 2: 0 libsystem_kernel.dylib 0x00000001df60a438 __psynch_cvwait + 8 1 libsystem_pthread.dylib 0x0000000218beae50 _pthread_cond_wait + 984 (pthread_cond.c:862) 2 VS_NASCO_Auscultation 0x0000000104fdde4c thread_func + 412 (sgen-thread-pool.c:195) 3 libsystem_pthread.dylib 0x0000000218bec344 _pthread_start + 136 (pthread.c:931) 4 libsystem_pthread.dylib 0x0000000218be9ab8 thread_start + 8 Thread 0 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0xffffffff9838bfdf x5: 0x0000000000000018 x6: 0x000000016cfa0730 x7: 0x000000016cf9fe20 x8: 0x9b8f66cd52cb42ec x9: 0x9b8f66ccab4b5cec x10: 0x00000000000003ff x11: 0x000000016cf9fe98 x12: 0x0000000000000000 x13: 0x00000001031e01a0 x14: 0x00000001a960913c x15: 0x00000001a960be20 x16: 0x0000000000000148 x17: 0x00000001f9801e00 x18: 0x0000000000000000 x19: 0x0000000000000006 x20: 0x0000000000000103 x21: 0x00000001f9801ee0 x22: 0x0000000000000010 x23: 0x000000000000000b x24: 0x0000000000002788 x25: 0x0000000105687624 x26: 0x000000010553ea10 x27: 0x000000010a6a0880 x28: 0x00000000000003c8 fp: 0x000000016cfa0740 lr: 0x0000000218bf0c60 sp: 0x000000016cfa0720 pc: 0x00000001df60f1dc cpsr: 0x40001000 esr: 0x56000080 Address size fault Binary Images: 0x102e5c000 - 0x10535bfff VS_NASCO_Auscultation arm64 <9b9a7de8b40b303bbc3d1a11686bb1dc> /var/containers/Bundle/Application/062FE418-9CD6-4509-B368-5FD6465FF1F9/VS_NASCO_Auscultation.app/VS_NASCO_Auscultation 0x109498000 - 0x1099fbfff libSkiaSharp arm64 /private/var/containers/Bundle/Application/062FE418-9CD6-4509-B368-5FD6465FF1F9/VS_NASCO_Auscultation.app/Frameworks/libSkiaSharp.framework/libSkiaSharp 0x196e23000 - 0x196ea26c3 libsystem_c.dylib arm64e <335cd87d234b3fc182db943350d31a88> /usr/lib/system/libsystem_c.dylib 0x1b58a7000 - 0x1b594187b dyld arm64e /usr/lib/dyld 0x1df604000 - 0x1df63debf libsystem_kernel.dylib arm64e /usr/lib/system/libsystem_kernel.dylib 0x218b3e000 - 0x218b458cf libsystem_platform.dylib arm64e /usr/lib/system/libsystem_platform.dylib 0x218be9000 - 0x218bf53f3 libsystem_pthread.dylib arm64e <1ee1922008593cbcbdebdf37ca2e8e4f> /usr/lib/system/libsystem_pthread.dylib EOF
0
0
105
2d
iOS build not appearing in App Store Connect after upload via Xcode and Transporter (React Native)
iOS build not appearing in App Store Connect after upload via Xcode and Transporter (React Native), Uploaded IPA “successfully” but build never shows in App Store Connect — React Native iOS. App type: React Native mobile app Android: Already published on Google Play (works fine) iOS goal: Upload the iOS build so it appears in App Store Connect (for TestFlight/release) No matter how I upload (Xcode Organizer Archive or the Transporter app), the build never appears in App Store Connect. It does not show under My Apps > [My iOS App] > TestFlight, nor under App Store Connect > Activity > All Builds. I’ve tried multiple times over several days. Xcode Organizer: “Upload to apple" there is no error, Transporter: delivered but app is processing , Email : there is no feedback with my problem please contact me
0
1
66
4d
CloudKit Sync with TestFlight
I'm working on a new app with SwiftData and now adding CloudKit Sync. Everything is working fine in the simulator against the development CloudKit Schema. I successfully deployed the schema to production. However, the TestFlight builds fail against production. This is what I see in the logs, but I haven't been able to find info on how to fix it. Help appreciated. CoreData+CloudKit: -[NSCloudKitMirroringDelegate _requestAbortedNotInitialized:](2205): <private> - Never successfully initialized and cannot execute request '<private>' due to error: Error Domain=CKErrorDomain Code=2 "CKInternalErrorDomain: 1011" UserInfo={ContainerID=<private>, NSDebugDescription=CKInternalErrorDomain: 1011, CKPartialErrors=<private>, RequestUUID=<private>, NSLocalizedDescription=<private>, CKErrorDescription=<private>, NSUnderlyingError=0x1078e9fe0 {Error Domain=CKInternalErrorDomain Code=1011 UserInfo={CKErrorDescription=<private>, NSLocalizedDescription=<private>, CKPartialErrors=<private>}}} CoreData+CloudKit: -[NSCloudKitMirroringDelegate _performSetupRequest:]_block_invoke(1153): <private>: Successfully set up CloudKit integration for store (<private>): <private> CoreData+CloudKit: -[NSCloudKitMirroringDelegate _enqueueRequest:]_block_invoke(1035): Failed to enqueue request: <private> Error Domain=NSCocoaErrorDomain Code=134417 UserInfo={NSLocalizedFailureReason=<private>}
1
0
47
5d
Missing Entitlement. The bundle ... is missing entitlement 'com.apple.developer.networking.networkextension'."
Hello everyone, I'm encountering an issue while trying to publish an app on TestFlight. The app in question is Home Assistant, which I've compiled from the source. I am able to compile and install the app on my device without any problems. My company's developer account is properly configured, and I have set Xcode to automatically manage the provisioning profile. The archive is also created successfully, but when I attempt to upload it to Apple Store Connect for testing via TestFlight, I receive the following error: ERROR: [ContentDelivery.Uploader] Asset validation failed (90525) Missing Entitlement. The bundle 'Home Assistant.app/PlugIns/HomeAssistant-Extensions-PushProvider.appex' is missing entitlement 'com.apple.developer.networking.networkextension'. (ID: ceac6dcc-9c76-412e-8ea7-f2d2845f8013) I've made several attempts to resolve this issue to no avail. For instance, if I add the missing capability manually, then I am informed that the provisioning profile is incorrect. However, checking the network extension settings on my company's dev account, I see nothing related to push notifications, which are located elsewhere. Thus, I am stuck in a loop where either the provisioning file is correct but the entitlement is missing, or if the entitlement is present, then the provisioning profile is deemed incorrect. URL:https://contentdelivery.itunes.apple.com status code: 409 (conflict) httpBody: { "errors" : [ { "id" : "ceac6dcc-9c76-412e-8ea7-f2d2845f8013", "status" : "409", "code" : "STATE_ERROR.VALIDATION_ERROR.90525", "title" : "Asset validation failed", "detail" : "Missing Entitlement. The bundle 'Home Assistant.app/PlugIns/HomeAssistant-Extensions-PushProvider.appex' is missing entitlement 'com.apple.developer.networking.networkextension'." }, { "id" : "9ff2143b-3c00-4912-b59f-8342fa6fe5c0", "status" : "409", "code" : "STATE_ERROR.VALIDATION_ERROR.90525", "title" : "Asset validation failed", "detail" : "Missing Entitlement. The bundle 'Home Assistant.app' is missing entitlement 'com.apple.developer.networking.networkextension'." } ] } ======================================= 2024-01-10 23:19:35.506 ERROR: [ContentDelivery.Uploader] Asset validation failed (90525) Missing Entitlement. The bundle 'Home Assistant.app/PlugIns/HomeAssistant-Extensions-PushProvider.appex' is missing entitlement 'com.apple.developer.networking.networkextension'. (ID: ceac6dcc-9c76-412e-8ea7-f2d2845f8013) 2024-01-10 23:19:35.506 DEBUG: [ContentDelivery.Uploader] Error Domain=ContentDelivery Code=90525 "Asset validation failed" UserInfo={NSLocalizedFailureReason=Missing Entitlement. The bundle 'Home Assistant.app/PlugIns/HomeAssistant-Extensions-PushProvider.appex' is missing entitlement 'com.apple.developer.networking.networkextension'. (ID: ceac6dcc-9c76-412e-8ea7-f2d2845f8013), NSUnderlyingError=0x6000022b6430 {Error Domain=IrisAPI Code=-19241 "Asset validation failed" UserInfo={status=409, detail=Missing Entitlement. The bundle 'Home Assistant.app/PlugIns/HomeAssistant-Extensions-PushProvider.appex' is missing entitlement 'com.apple.developer.networking.networkextension'., id=ceac6dcc-9c76-412e-8ea7-f2d2845f8013, code=STATE_ERROR.VALIDATION_ERROR.90525, title=Asset validation failed, NSLocalizedFailureReason=Missing Entitlement. The bundle 'Home Assistant.app/PlugIns/HomeAssistant-Extensions-PushProvider.appex' is missing entitlement 'com.apple.developer.networking.networkextension'., NSLocalizedDescription=Asset validation failed}}, iris-code=STATE_ERROR.VALIDATION_ERROR.90525, NSLocalizedDescription=Asset validation failed} 2024-01-10 23:19:35.507 ERROR: [ContentDelivery.Uploader] Asset validation failed (90525) Missing Entitlement. The bundle 'Home Assistant.app' is missing entitlement 'com.apple.developer.networking.networkextension'. (ID: 9ff2143b-3c00-4912-b59f-8342fa6fe5c0) 2024-01-10 23:19:35.507 DEBUG: [ContentDelivery.Uploader] Error Domain=ContentDelivery Code=90525 "Asset validation failed" UserInfo={NSLocalizedFailureReason=Missing Entitlement. The bundle 'Home Assistant.app' is missing entitlement 'com.apple.developer.networking.networkextension'. (ID: 9ff2143b-3c00-4912-b59f-8342fa6fe5c0), NSUnderlyingError=0x6000022b6640 {Error Domain=IrisAPI Code=-19241 "Asset validation failed" UserInfo={status=409, detail=Missing Entitlement. The bundle 'Home Assistant.app' is missing entitlement 'com.apple.developer.networking.networkextension'., id=9ff2143b-3c00-4912-b59f-8342fa6fe5c0, code=STATE_ERROR.VALIDATION_ERROR.90525, title=Asset validation failed, NSLocalizedFailureReason=Missing Entitlement. The bundle 'Home Assistant.app' is missing entitlement 'com.apple.developer.networking.networkextension'., NSLocalizedDescription=Asset validation failed}}, iris-code=STATE_ERROR.VALIDATION_ERROR.90525, NSLocalizedDescription=Asset validation failed} 2024-01-10 23:19:35.507 DEBUG: [ContentDelivery.Uploader] swinfo errors: ( "Error Domain=ContentDelivery Code=90525 \"Asset validation failed\" UserInfo={NSLocalizedFailureReason=Missing Entitlement. The bundle 'Home Assistant.app/PlugIns/HomeAssistant-Extensions-PushProvider.appex' is missing entitlement 'com.apple.developer.networking.networkextension'. (ID: ceac6dcc-9c76-412e-8ea7-f2d2845f8013), NSUnderlyingError=0x6000022b6430 {Error Domain=IrisAPI Code=-19241 \"Asset validation failed\" UserInfo={status=409, detail=Missing Entitlement. The bundle 'Home Assistant.app/PlugIns/HomeAssistant-Extensions-PushProvider.appex' is missing entitlement 'com.apple.developer.networking.networkextension'., id=ceac6dcc-9c76-412e-8ea7-f2d2845f8013, code=STATE_ERROR.VALIDATION_ERROR.90525, title=Asset validation failed, NSLocalizedFailureReason=Missing Entitlement. The bundle 'Home Assistant.app/PlugIns/HomeAssistant-Extensions-PushProvider.appex' is missing entitlement 'com.apple.developer.networking.networkextension'., NSLocalizedDescription=Asset validation failed}}, iris-code=STATE_ERROR.VALIDATION_ERROR.90525, NSLocalizedDescription=Asset validation failed}", "Error Domain=ContentDelivery Code=90525 \"Asset validation failed\" UserInfo={NSLocalizedFailureReason=Missing Entitlement. The bundle 'Home Assistant.app' is missing entitlement 'com.apple.developer.networking.networkextension'. (ID: 9ff2143b-3c00-4912-b59f-8342fa6fe5c0), NSUnderlyingError=0x6000022b6640 {Error Domain=IrisAPI Code=-19241 \"Asset validation failed\" UserInfo={status=409, detail=Missing Entitlement. The bundle 'Home Assistant.app' is missing entitlement 'com.apple.developer.networking.networkextension'., id=9ff2143b-3c00-4912-b59f-8342fa6fe5c0, code=STATE_ERROR.VALIDATION_ERROR.90525, title=Asset validation failed, NSLocalizedFailureReason=Missing Entitlement. The bundle 'Home Assistant.app' is missing entitlement 'com.apple.developer.networking.networkextension'., NSLocalizedDescription=Asset validation failed}}, iris-code=STATE_ERROR.VALIDATION_ERROR.90525, NSLocalizedDescription=Asset validation failed}" )
8
0
2.8k
5d
TestFlight Build Stuck in Review
Hello everyone, I uploaded my first app to the App Store for TestFlight. Since I read that TestFlight reviews are usually completed within a few hours, I am a bit unsure whether I might have done something wrong in the review process. I submitted the app to TestFlight on September 10, and after some back and forth, I received a message on September 13 saying: “Your submission is still in review but is requiring additional time. We will provide further status updates as soon as we are able.” On Tuesday, September 16, I sent an email to Support asking if I had done something wrong and mentioning that I uploaded a new build. Apple then put the new build into review, and on the same day I received another message that the review would take some more time. Since then, I haven’t heard anything further. The older build is still shown as “In Review” (since September 12). Is there anything I can do at this point?
0
0
46
5d
Issue after Build
I have a strange problem. My code works perfectly on my iPhone, i.e. on a real iPhone, but when I upload the build version to TestFlight, it no longer works. I use React Native. The issue is as follows: I have created a code for Grid View that runs automatically when another person joins the stream. It works locally without any problems, but unfortunately the public version does not work. What could be the reason for this?
0
0
51
6d
Successfully uploaded iOS app builds don't appear in App Store Connect
Since 1st of September archives uploaded via Xcode 26 beta 7 or builds distributed via CD (fastlane deliver) don't appear in App Store Connect. No errors reported during/after upload process, no e-mails with errors received. Xcode reports successful upload (with a few warnings regarding dSYM) I'm not getting any e-mails with ITMS errors Builds don't appear at in App Store Connect in TestFlight section (not even in "Processing" or "Failed" states). For me it seems like App Store Connect outage but all statuses in https://www.apple.com/support/systemstatus/ are green.
4
4
201
1w
What's the best way to detect if the app was installed from TestFlight (iOS & macOS)?
For ages, we've been using appStoreReceiptUrl to detect if the app was installed from TestFlight or not, but now that's deprecated. Since we have a strict policy of no warnings on the project, we need to find a way to check if the app was installed from TestFlight or from the App Store. Does anyone know what's the new way to do so? I thought about using MarketplaceKit.AppDistributor.testFlight but to use MarketplaceKit you need to jump through hoops that our app really doesn't need to - we don't distribute outside of the App Store. Any ideas are much appreciated! 🙏
0
1
136
1w