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

Posts under TestFlight subtopic

Post

Replies

Boosts

Views

Activity

Could not install myapp on Testflight. Happend to all my builds and apps.
Hello, I uploaded my application to TestFlight via Xcode (React Native), but I cannot install it on my device or other testers' devices(Internal). This happened to all builds, all my apps and all tester's I have faced this error before, but after sending a support ticket, it was resolved. But this time, it's come back. I don't know why.
0
0
77
11h
How can I cancel my TestFlight build subscription purchase?
I built a TestFlight version of my unpublished app. While using it, I wanted to test out the subscription purchase and when I did, I used my real production Apple ID and not a Sandbox test account to purchase the subscription. I was surprised to see that it worked and I was able to use the test subscription in the app. However, I now have no way of canceling it. It has renewed every day at the same time due to the accelerated TestFlight subscription rate (it's a monthly sub). I read that it should stop auto-renewing after the 6th time, but I believe it's been over a week now and it still hasn't cancelled. I understand that it's not a real purchase, but I would still like to cancel it so I can try it without the purchase again using this account and also use it with a different Sandbox account. Can someone help me with canceling it? Since the account I used was not a Sandbox account, I can't just clear the purchase history in App Store Connect. Also, I can't go into my personal account settings to remove the subscription since it's not a production one.
2
0
149
2d
Could not download app from App Store or TestFlight after macOS 26 upgrade
After upgrading to macOS 26, I cannot install or update my app from either the App Store or TestFlight. Other apps update and install normally. Steps: Before upgrading, the app was installed via TestFlight and worked fine. After upgrading, I tried to update the app from the App Store: The update stalls at ~90% and never completes. Other apps update successfully. I launched the already-installed TestFlight version — it worked. After deleting the app, I tried reinstalling from TestFlight and got the error: “The app couldn’t be downloaded. Try again.” I tried rebooting, logging out/in of my Apple ID, and submitting a new TestFlight build — same issue. Environment: Originally built with Xcode 14 Also tried a new build with Xcode 16 App is compatible with macOS 26. Distribution outside the App Store (Developer ID signed and notarized build) runs fine
3
1
214
3d
Issue in distributint my app on TestFlight.
Hi, yesterday when I was trying to release the TestFlight build of my app the xcode said that it could not authenticate my apple ID. I then came to know that it actually wanted me to complete and aggrement which was "Paid Apps Agreement". This agreeemnet is to be made if one has to sell their app on AppStore or make in-app-purchases. I want to ask if it was mandatory for me to sign that agreement? As the solution which I could come across suggested that xcode blocks the distribution if there is a pending agreement.
1
0
65
3d
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.
16
6
790
5d
I cant install the app from app store or test flight.
Hello, I'm experiencing difficulties installing the app created by my team, both from the App Store and TestFlight. I'm currently using Tahoe 26.0 Beta (25A5346a), and even though the app isn't previously installed, I'm still unable to proceed with the installation. I was able to obtain these logs, but I'm uncertain about how to rectify this issue. Logs from AppStore: error 10:52:33.103471+0200 appstoreagent [PurchaseService]: [6E4C7375] Purchase completed with error: Error Domain=ASDErrorDomain Code=506 "Duplicate request" UserInfo={NSLocalizedDescription=Duplicate request, NSLocalizedFailureReason=Request is a duplicate of UPD9C204399/com.imperum.app:6743783187} default 10:52:34.164171+0200 appstoreagent [PurchaseService]: [C78059BF] Starting purchase of 6743783187:com.imperum.app by com.apple.AppStore default 10:52:34.164661+0200 appstoreagent [BUYC78059BF/com.imperum.app:6743783187] Starting purchase for client: com.apple.AppStore default 10:52:34.164995+0200 appstoreagent [BUYC78059BF/com.imperum.app:6743783187] Failing this request as a duplicate of UPD9C204399/com.imperum.app:6743783187 error 10:52:34.165014+0200 appstoreagent DetectDuplicateRequestTask completing with error: Error Domain=ASDErrorDomain Code=506 "Duplicate request" UserInfo={NSLocalizedDescription=Duplicate request, NSLocalizedFailureReason=Request is a duplicate of UPD9C204399/com.imperum.app:6743783187} error 10:52:34.165086+0200 appstoreagent [PurchaseService]: [C78059BF] Purchase completed with error: Error Domain=ASDErrorDomain Code=506 "Duplicate request" UserInfo={NSLocalizedDescription=Duplicate request, NSLocalizedFailureReason=Request is a duplicate of UPD9C204399/com.imperum.app:6743783187} Logs from TestFlight: error 10:54:35.751574+0200 appstoreagent [TFU3C168938/com.imperum.app:6743783187]: Failed to set IXProgressHint on the coordinator: Error Domain=IXErrorDomain Code=5 "A coordinated app install already exists for [com.imperum.app/Invalid/[system-defined]] with intent IXCoordinatorIntentUpdating (creator App Store) but request by appstoreagent (pid 5805) was for intent IXCoordinatorIntentInitiating" UserInfo={NSLocalizedFailureReason=Coordinated install exists with different intent., FunctionName=-[IXSClientConnection _remote_createAppInstallCoordinatorWithSeed:createIfNotExisting:requireMatchingIntent:scopeRequirement:completion:], SourceFileLine=641, NSLocalizedDescription=A coordinated app install already exists for [com.imperum.app/Invalid/[system-defined]] with intent IXCoordinatorIntentUpdating (creator App Store) but request by appstoreagent (pid 5805) was for intent IXCoordinatorIntentInitiating} error 10:54:35.751597+0200 appstoreagent AppInstallImportAndPolicyTask completing with error: Error Domain=IXErrorDomain Code=5 "A coordinated app install already exists for [com.imperum.app/Invalid/[system-defined]] with intent IXCoordinatorIntentUpdating (creator App Store) but request by appstoreagent (pid 5805) was for intent IXCoordinatorIntentInitiating" UserInfo={NSLocalizedFailureReason=Coordinated install exists with different intent., FunctionName=-[IXSClientConnection _remote_createAppInstallCoordinatorWithSeed:createIfNotExisting:requireMatchingIntent:scopeRequirement:completion:], SourceFileLine=641, NSLocalizedDescription=A coordinated app install already exists for [com.imperum.app/Invalid/[system-defined]] with intent IXCoordinatorIntentUpdating (creator App Store) but request by appstoreagent (pid 5805) was for intent IXCoordinatorIntentInitiating} error 10:54:35.751641+0200 appstoreagent [TFU3C168938/com.imperum.app:6743783187] TestFlight import failed: Error Domain=IXErrorDomain Code=5 "A coordinated app install already exists for [com.imperum.app/Invalid/[system-defined]] with intent IXCoordinatorIntentUpdating (creator App Store) but request by appstoreagent (pid 5805) was for intent IXCoordinatorIntentInitiating" UserInfo={NSLocalizedFailureReason=Coordinated install exists with different intent., FunctionName=-[IXSClientConnection _remote_createAppInstallCoordinatorWithSeed:createIfNotExisting:requireMatchingIntent:scopeRequirement:completion:], SourceFileLine=641, NSLocalizedDescription=A coordinated app install already exists for [com.imperum.app/Invalid/[system-defined]] with intent IXCoordinatorIntentUpdating (creator App Store) but request by appstoreagent (pid 5805) was for intent IXCoordinatorIntentInitiating} error 10:54:35.751807+0200 appstoreagent InstallTestFlightAppsTask completing with error: Error Domain=IXErrorDomain Code=5 "A coordinated app install already exists for [com.imperum.app/Invalid/[system-defined]] with intent IXCoordinatorIntentUpdating (creator App Store) but request by appstoreagent (pid 5805) was for intent IXCoordinatorIntentInitiating" UserInfo={NSLocalizedFailureReason=Coordinated install exists with different intent., FunctionName=-[IXSClientConnection _remote_createAppInstallCoordinatorWithSeed:createIfNotExisting:requireMatchingIntent:scopeRequirement:completion:], SourceFileLine=641, NSLocalizedDescription=A coordinated app install already exists for [com.imperum.app/Invalid/[system-defined]] with intent IXCoordinatorIntentUpdating (creator App Store) but request by appstoreagent (pid 5805) was for intent IXCoordinatorIntentInitiating} error 10:54:35.751919+0200 TestFlight Installation request for 1 app(s) failed with error: Error Domain=IXErrorDomain Code=5 "A coordinated app install already exists for [com.imperum.app/Invalid/[system-defined]] with intent IXCoordinatorIntentUpdating (creator App Store) but request by appstoreagent (pid 5805) was for intent IXCoordinatorIntentInitiating" UserInfo={NSLocalizedDescription=A coordinated app install already exists for [com.imperum.app/Invalid/[system-defined]] with intent IXCoordinatorIntentUpdating (creator App Store) but request by appstoreagent (pid 5805) was for intent IXCoordinatorIntentInitiating, FunctionName=-[IXSClientConnection _remote_createAppInstallCoordinatorWithSeed:createIfNotExisting:requireMatchingIntent:scopeRequirement:completion:], SourceFileLine=641, NSLocalizedFailureReason=Coordinated install exists with different intent.} Any help please..
9
6
667
6d
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
1w
StoreKit error while testing
Hello, I'm receiving error StoreKit: Failed to get response from platform. I have user in SandBox, that user is logged on physical device, I have correct bundleID. Product is Approved I tested via StoreKit configuration file and that worked just fine. also tried to build app and push to test flight, this way same error. Any recommendations what I can check ? Thanks
2
3
237
1w
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
12
1w
TestFlight builds are not being pushed to App Connect Users
I recently started having an issue with my TestFlight builds. In the past, if I built/distributed an app for TestFlight, the AppConnect group automatically received the builds and were able to install the on their devices. When I look in AppConnect, I can see the AC (AppConnect) group shown as a tester and that group shows the users I am expecting in them. The users are receiving an email from TestFlight saying the build is ready. However, when we go into TestFlight, it doesn't show the update being available for that new build. What I have done as a work-around is added my AppConnect users to separate group and add them as testers each time I release a build to TestFlight. Has anyone seen this or can they point out why this may be happening?
0
1
162
1w
Testflight instructions? "Enter your TestFlight invitation code"
I've developed an app that is available for testing on Testflight now. I've created a link for external testers with no criteria. Over the last week I've had several people contact me and tell me that they are not able to install because they are being asked for a 'redeem code': "Enter your TestFlight invitation code." The problem is, the user shouldn't be seeing this. They should tap the invitation, download/register for Testflight, then tap the link for my app to download install the app. However, that only happens sporadically and other times users are prompted for this redeem code. And I have been looking for solutions to this for hours and all I see are hundreds of posts dating back 5 years or more, but cannot find any solution anywhere. Cannot find any simple instructions to send to users or a link, and I cannot find any indication that Apple is even addressing this problem. Please give this post a boost so that someone at apple finally will address the problem.
0
0
46
1w
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
883
1w
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
188
1w
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
58
2w
Beta-App review approval
Hello everyone, I’ve uploaded my first app to the App Store for TestFlight. Since I’ve read that TestFlight reviews are usually completed within a few hours, I’m a bit unsure if I might have done something wrong during the review process. I submitted a build on September 10th, and after some back-and-forth I received a message on September 13th 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 16th, I sent an email to Support asking if I had done something wrong and mentioning that I had uploaded a new build. Apple then put the new build into review, and on the same day I got another message saying the review would take some more time. Since then, I haven’t heard anything further. The older build has also been stuck in “In Review” since September 12th. Is there anything I can do at this point?
0
0
47
2w
Agora streaming works in USB release builds but not in TestFlight/App Store
We are experiencing an issue with the Agora integration in our app. The video/audio streaming works correctly when the app is run on a device connected via USB in release mode or installed via the Play Store (Android). However, when running through TestFlight or on the App Store version, the streaming does not function as expected. We would greatly appreciate any guidance on whether this is related to App Store restrictions, permissions, or any specific configuration required for Agora to work in TestFlight and App Store builds. Thank you for your time and support.
0
0
16
2w
ITMS-90429: Invalid Swift Support – Swift libraries not at expected location in iOS app submission
Hello Apple Developer Community, I’m facing an issue when submitting my iOS app to App Store Connect. ITMS-90429: Invalid Swift Support libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreGraphics.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftCoreImage.dylib aren’t at the expected location: /Payload/Runner.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it. My setup: Using Flutter for iOS development Flutter version: 3.32.8 Xcode version: Version 16.3 What I have tried so far: Cleaned build folder: flutter clean Upgraded Flutter and CocoaPods to the latest version. Rebuilt the project using latest Xcode GM version. Verified that Always Embed Swift Standard Libraries is set to YES in Xcode. Reinstalled pods and ensured use_frameworks! is correctly set in Podfile. Despite this, I still get the same error. My questions: What is the correct way to ensure the Swift libraries are embedded in the correct location for Flutter apps? Is there any known issue when building with Flutter and integrating static .a libraries that could cause this problem? Has anyone successfully submitted a Flutter iOS app with external static libraries linked and avoided this error? Are there any manual steps required to fix the location of Swift dylibs during the build process? Thank you in advance for your help!
8
0
304
2w