TestFlight

RSS for tag

Use TestFlight in App Store Connect to invite and manage beta testers for iOS, iPadOS, tvOS, and watchOS apps. Discuss questions here and share app builds publicly via TestFlight under the Community topic.

TestFlight Documentation

Post

Replies

Boosts

Views

Activity

Adalo App Submission Issue on IOS
Greetings to all! I recently developed an called DANZUB, the hub for dancers using the Adalo no-code tool. The App from adalo was directly imported into TestFlight on App Store Connect. When I released it for review, I got a rejection that app was not supported (display scale issue) on Ipad. I have primarily designed for IPhones and I do not know how I can adjust to IPads as well. I don't have this option on Adalo. Some said I could change the settings in XCode. But I don;t have the file, because the file was directly exported from Adalo to App Store Connect. I am unable to download the file. Please help, I am new to developing. So close yet so far. Thanks all!!
0
0
28
4h
App Crash on Testflight
Good day. My app crashed as i launched to testflight. when it is launched on a real devices it crashes here is my crash report. Incident Identifier: 6B2FE0C7-91F8-46D3-90B5-EB96A6809C5C Hardware Model: iPhone12,5 Process: Runner [39554] Path: /private/var/containers/Bundle/Application/D413442F-1978-4F6F-909C-A09EAE720D44/Runner.app/Runner Identifier: com.gtirides.appRide Version: 1.0.0 (1) AppStoreTools: 15F31e AppVariant: 1:iPhone12,5:16 Beta: YES Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: com.gtirides.appRide [4745] Date/Time: 2024-06-20 13:07:17.1843 +0100 Launch Time: 2024-06-20 13:07:16.9994 +0100 OS Version: iPhone OS 16.5.1 (20F770750d) Release Type: User Baseband Version: 4.02.01 Report Version: 104 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Codes: 0x0000000000000001, 0x0000000000000000 VM Region Info: 0 is not in any region. Bytes before following region: 4301684736 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 100668000-100670000 [ 32K] r-x/r-x SM=COW ...er.app/Runner Termination Reason: SIGNAL 11 Segmentation fault: 11 Terminating Process: exc handler [39554] Triggered by Thread: 0 Thread 0 Crashed: 0 Intercom 0x0000000100e94610 +[ICMIdentityStore hexTokenFromDeviceToken:] + 32 1 Intercom 0x0000000100e946bc -[ICMIdentityStore setDeviceTokenData:environment:failure:] + 80 2 Intercom 0x0000000100ebb320 +[ICMHTTPBridge registerDeviceToken:failure:] + 116 3 Intercom 0x0000000100ea7bdc +[ICMBridge registerDeviceToken:failure:] + 112
1
0
65
1d
Can't install from TestFlight
I'm trying to test an app on Testflight and having problems. I've uploaded my app to App store connect successfully and I've added my external testers to the new build. It's in the "waiting for review" stage. When I go to TestFlight, I see the new build, as expected (I'm an internal tester). When I tap "install" I get the following error: Could not install ______. The profile can't be installed. Try again. Is this a problem on my end or apple's? The same build of the app works fine when I hit the "run" button in XCode.
13
16
768
2d
Testflight Build Erro - DVTAppStoreConnect.ServiceBackendError error 1.
Hi guys, I'm trying to make a test flight build (first time in a while) in Xcode 16.0 Beta for a visionOS 2.0 beta test. When I click Distribute App, It preps and creates the app but fails on the next step "creating app record..." with this code The operation couldn’t be completed. (DVTAppStoreConnect.ServiceBackendError error 1.) My account is old with a ton of certs, identifers, profiles etc. I've tied setting up a new one but that doesn't seem to fix the issue ( though I might have easily missed a step? ) Any help on how to solve this?
0
0
107
5d
App crashes when downloaded from TestFlight, not when built locally with Xcode
Development Environment: Xcode Version: 15.4 (15F31d) macOS: 14.5 (23F79) Hardware: MacBook Pro with Apple M1 Max Chip Dear Apple Developer Community and Support, I am currently developing an application for both iOS and macOS. In the macOS environment, I encounter an issue where the app crashes immediately upon launch when deployed via Xcode Cloud to TestFlight. This issue does not occur when building the app directly in Xcode with the Scheme Build Configuration set to Release. My colleague, who is also working on this project, does not experience any issues when running the app from TestFlight on her Mac. Below is the crash log for reference: Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x0000000196b94c88 Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5 Terminating Process: exc handler [26662] Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 AppKit 0x196b94c88 ___NSAssertMainEventQueueIsCurrentEventQueue_block_invoke + 216 1 libdispatch.dylib 0x1930a63e8 _dispatch_client_callout + 20 2 libdispatch.dylib 0x1930a7c68 _dispatch_once_callout + 32 3 AppKit 0x196b93bbc _DPSNextEvent + 232 4 AppKit 0x197389808 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 700 5 AppKit 0x196b8709c -[NSApplication run] + 476 6 AppKit 0x196b5e2e0 NSApplicationMain + 880 7 SwiftUI 0x1becd2474 0x1bebc8000 + 1090676 8 SwiftUI 0x1bf43be88 0x1bebc8000 + 8863368 9 SwiftUI 0x1bf836eb8 0x1bebc8000 + 13037240 10 Paperbot 0x104f247b4 0x104f1c000 + 34740 11 dyld 0x192ece0e0 start + 2360 We would greatly appreciate any insights or suggestions to resolve this issue. Thank you for your support. Best regards, Julien
0
0
66
1w
How can I revoke one time purchases made via TestFlight?
Before I launched my app, I ran a TestFlight beta program and also included a one time purchase in the TestFlight build to test the functionality. Now that the app is available in the App Store, I had closed the TestFlight program, but am looking to reopen it again to test iOS 18 specific features. The issue is, the beta testers that previously purchased the IAP on TestFlight but didn't actually purchase the IAP on the App Store version would be able to use the paid features of the app for free as long as they have the TestFlight build. Therefore I would like to revoke all the purchases made via the TestFlight build. Is there any way to do that?
0
0
124
1w
TestFlight not working with In-app purchases
Environment react-native-iap: 12.12.2. react-native: 0.72.12. Platforms (physical & simulator): iPhone 11 - OS version 17.4 /// iOS Simulator iPhone 15 Pro Max - OS version 17.4 Description Hello, I am trying to test the purchase of a subscription and an in-app product within my react native app. I have setup the necessary Sandbox account in App Store Connect, created a Store kit file in Xcode that I also synced with the products I created in the App Store Connect dashboard. If I use Xcode to run the app on a physical device (after logging into the sandbox account), I am able to purchase a subscription/in-app product without any issues. If I purchased a subscription on the physical phone I can go into Settings > App Store > Sandbox Account Management and see the purchased subscription, change renewal rate, clear purchase history etc.. If I use the TestFlight build with a physical phone (logging in with the sandbox account) the in app purchases stop working correctly. After purchasing a subscription it is not shown in the Sandbox Account Management, so I am unable to cancel it. Upon trying to purchase another subscription the apple service keeps returning the same exact subscription that I "originally" purchased. How am I supposed to cancel that subscription if it not shown in the sandbox account subscription list? Adding a different sandbox account does not help either, trying to purchase another subscription returns the same subscription that I am unable to cancel. Is there a step in the TestFlight environment that I am missing on setup? Expected Behavior Upon purchasing a subscription in the TestFlight environment on a physical device I should be able to cancel that subscription. Here's an example of what function I am calling on purchasing a subscription: const product = { productId: 'example_monthly_subscription' }; subscribe(product.productId); Any help would be appreciated.
0
0
119
1w
how to include secrets file
Hi. My app hits an API. I have the API key stored in a config.plist file. Of course, I don't want to include this file in version control. So I omitted it. I have a workflow that when I push to my main branch, it pushes the newest version to internal testers on test flight. The problem is, the deployed code cannot find the config file, which makes sense. My approach to this problem has been to use resource tags Targets > Resource Tags And I declared that this app should download this resource. I can't figure out how to categorize it as other than download on demand . I would like it to be downloaded immediately with the app. Am I even on the right track here?
1
0
134
1w
macOS app crashes on first launch from TestFlight
2024_06_09_testflight_launch_crash_log.txt Running my macOS app the first time after installing via TestFlight crashes on launch. Every subsequent run works fine (including completely quitting the app and re-running it). Also, building and running directly in XCode both in Debug and Release mode works fine. I'm on a Mac M2 and the app excludes x86_64 arch. Here is the trimmed crash log (sanitised full log is attached) Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: CamHero-macOS-v2-Release [12876] Application Specific Information: abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x18c81d11c __pthread_kill + 8 1 libsystem_pthread.dylib 0x18c854cc0 pthread_kill + 288 2 libsystem_c.dylib 0x18c764a40 abort + 180 3 libglib-2.0.0.dylib 0x1061e5bd0 g_assertion_message + 464 4 libglib-2.0.0.dylib 0x1061e5c44 g_assertion_message_expr + 116 5 libgstlibav.dylib 0x10549ede0 gst_ffmpeg_cfg_init + 776 6 libgstlibav.dylib 0x10548a4f4 plugin_init + 140 7 libgstreamer-1.0.0.dylib 0x10646a458 gst_plugin_register_func + 636 8 libgstreamer-1.0.0.dylib 0x106469fe4 gst_plugin_register_static + 212 9 libgstlibav.dylib 0x10548a45c gst_plugin_libav_register + 92 10 CamHero-macOS-v2-Release 0x104a01624 gst_ios_init + 900 (gst_ios_init.m:1072) 11 CamHero-macOS-v2-Release 0x104a80590 specialized CamHeroMacOSApp.init() + 68 (CamHeroMacOSApp.swift:19) 12 CamHero-macOS-v2-Release 0x104a804a4 CamHeroMacOSApp.init() + 4 [inlined] 13 CamHero-macOS-v2-Release 0x104a804a4 protocol witness for App.init() in conformance CamHeroMacOSApp + 20 (<compiler-generated>:16) 14 SwiftUI 0x1b7f134e0 0x1b7163000 + 14353632 15 CamHero-macOS-v2-Release 0x104a804d8 static CamHeroMacOSApp.$main() + 24 [inlined] 16 CamHero-macOS-v2-Release 0x104a804d8 main + 36 17 dyld 0x18c4d90e0 start + 2360 Thread 1: 0 libsystem_pthread.dylib 0x18c84fe28 start_wqthread + 0 Thread 2: 0 libsystem_pthread.dylib 0x18c84fe28 start_wqthread + 0 Thread 0 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0x0000600000755680 x5: 0x0000000000000020 x6: 0x0000600000755680 x7: 0xffffffff00008600 x8: 0x8ddd1ea266cd729b x9: 0x8ddd1ea3846d2c5b x10: 0x0000000000001620 x11: 0x00000000dbe367fb x12: 0x00000000000007fb x13: 0x00000000000007fd x14: 0x00000000dc03683c x15: 0x000000000000003c x16: 0x0000000000000148 x17: 0x00000001eb9f3da0 x18: 0x0000000000000000 x19: 0x0000000000000006 x20: 0x00000001e2a05ec0 x21: 0x0000000000000103 x22: 0x00000001e2a05fa0 x23: 0x000000016b407508 x24: 0x0000000000000000 x25: 0x00000001064f8450 x26: 0x000060000080d511 x27: 0x0000000000000000 x28: 0x0000000000000000 fp: 0x000000016b407460 lr: 0x000000018c854cc0 sp: 0x000000016b407440 pc: 0x000000018c81d11c cpsr: 0x40001000 far: 0x0000000000000000 esr: 0x56000080 Address size fault It seems that the initialisation of one of the gstreamer plug-ins doesn't go well. But, I wonder what might lead to that happening only the first time after launch? Will appreciate any clues! EDIT / UPDATE: If i remove the app completely and install the same version again from TestFlight, app doesn't crash. So it seems the crashing is limited to the very first launch of a new /updated version.
3
0
211
1w
Unable to install TestFlight build after app was removed from sale
I'm frantically trying to update five mobile applications that have been neglected for way too long, managed to get an update published for the first one just last month, but now I'm stuck trying to release an update for the second one. The only real difference in the overall process between these two is that the first was not "removed from sale" by Apple's automated systems, where the second one has been. My app update is built and uploaded to App Store Connect, it shows up under the "TestFlight" tab, and it shows in the TestFlight app on my iPad, but when I tap "Install" I get a message that reads "Could not install [app]. The requested app is not available or doesn't exist." The app in question works with proprietary hardware that I cannot send to Apple for the sake of their internal review process, but I cannot make a "tech demo" video showing the app working on my iPad because TestFlight refuses to install it... Please can somebody help me work out what I'm missing here?
1
0
220
2w
My macOS TestFlight app keep deactivating its windows as if there's another invisible window in front
Has anyone else seen this happen with their macOS apps in TestFlight? The situation: When I launch my app that's been downloading via TestFlight.app, it often comes up with its main window deactivated. Also, when I have open more than one window and close one, the other window doesn't come to front either. In either case, activating the app or clicking into a window will activate it properly. It feels as if there's another window that's not visible but somehow keeps getting activated. I have this happen on two Macs running both Sonoma and Monterey. Also, if I take the very same build that I had uploaded to TestFlight and run it directly, it works correctly. So I suspect that TestFlight somehow messes with my app's windows. If you want to test this yourself: Get the app thru this link: https://findanyfile.app/TestFlight/ Then launch it. Often, the Find window will already come up without being active. Activate it, then open the Preferences window by typing cmd-comma. Then close the Prefs window with cmd-W. This should re-activate the Find window but will instead leave it deactivated, and none of the menu shortcuts (such as cmd-comma, cmd-N or cmd-Q) work. That's the bug. I wonder how I can debug this to find a work-around for this odd behavior. E.g, I'd like to see if there is indeed a semi-hidden window causing this. How would I do this? I could probably make a new TestFlight build that queries the app's windows array and logs it. But are there other ways to query an app's windows? I tried AppleScript, but since my app isn't scriptable, I only get an error -1728 for tell app "Find Any File" to get windows.
2
0
284
3w
visionOS and iOS archive builds
When I do an archive build of my app against visionOS, the archive listing in the Organizer show the archive entry as iOS. So I have one archive build for iOS with a certain build number and another archive build for visionOS with another build number (incremented by 1) They are both listed in The Organizer but they both have iOS info. I’ve submitted them both separately to TestFlight and I’m about to try to test it on visionOS. Shouldn’t the visionOS archive build that I submit to TestFlight indicate something about visionOS instead of iOS?
1
0
292
3w