If I try to run Instrument's logger for an app downloaded from TestFlight it says "Permission to debug app name was denied". "Recover Suggestion: The app must be debuggable and signed with 'get-task-allow'. How do you make the app debuggable? (I tried creating an archive with the scheme set to Debug, but after uploading that to TestFlight, it doesn't appear. So presumably its not possible to upload an app built with debug scheme builds to TF?). Therefore how can I make a TF build debuggable?, and how to sign it with get-task-allow? Does it have to be a developer distribution .ipa rather than a TestFlight build to enable Instruments/Logger to run it?

Hello, this morning logged in to my app store connect developer account and its all blank, no apps is present. THanks!

I have two release trains going in TestFlight: The App Store version v1.0(0) with bug fixes v1.0(1), v1.0(2), etc. The next feature version with additional functionalities of the app v1.1(0), v1.1(1), v1.1(2), etc. Is there any way to have v1.0(x) be for internal testing, and have v1.1(x) be for external testing? I really need to start external testing the next release of the app in TestFlight, while also bug fixing the current version of the app in TestFlight. Thanks!

Hi, I build my application bundle by makefile and later using productbuild to create an application installer. This works fine. But as uploading it to apple using Transporter I get these 2 error messages. #01 error message: Asset validation failed (90242) The product archive is invalid. The Info.plist must contain a LSApplicationCategoryType key, whose value is the UTI for a valid category. For more details, see "Submitting your Mac apps to the App Store". (ID: f25a48a4-8e89-4824-9f22-a6bc2fb90193) #02 error message: Asset validation failed (90259) Bad Bundle Executable. You must include a valid CFBundleExecutable key in your bundle's information property list file. (ID: c3d9f35a-5a27-4cc6-bba8-56cf514c3ad9) Here is my Info.plist <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>CFBundleDevelopmentRegion</key> <string>English</string> <key>CFBundleExecutable</key> <string>GSequencer</string> <key>CFBundleGetInfoString</key> <string>6.4.3, Copyright 2005-2024 Joel Kraehemann</string> <key>CFBundleIconFile</key> <string>GSequencer.icns</string> <key>CFBundleIdentifier</key> <string>com.gsequencer.GSequencer</string> <key>CFBundleInfoDictionaryVersion</key> <string>6.0</string> <key>CFBundlePackageType</key> <string>APPL</string> <key>CFBundleShortVersionString</key> <string>6.4.3</string> <key>CFBundleSignature</key> <string>????</string> <key>CFBundleVersion</key> <string>6.4.3</string> <key>NSHumanReadableCopyright</key> <string>Copyright 2005-2024 Joel Kraehemann, GNU General Public License.</string> <key>LSMinimumSystemVersion</key> <string>11.0</string> </dict> </plist> Here are the 2 binaries in MacOS directory: ls -1 gsequencer-macos/build/universal/GSequencer.app/Contents/MacOS/ GSequencer gsequencer_macos_install Please help me to fix. regards, Joël

Hi, All of my TestFlight builds expired themselves and I can't submit any new builds for external testing. The general error message I see is "There was an error processing your request. Please try again later." and looking at the console I see a more specific error "API Response Error: TF_BETA_APP_REVIEW_RESPONSE". I've sent a couple of emails to support but I haven't heard anything back yet. What's going on with App Store Connect these days? It's so unreliable.

I'm really new into Development I have macos App I upload 2 builds to TestFlight were working Fine But the Third Build Crashed on TestFlight user Machine but on my machine working just fine from Xcode or TestFlight on my machine. Appreciate if someone helped here is crashlog: Process: Shaheed [814] Path: /Applications/Shaheed.app/Contents/MacOS/Shaheed Identifier: com.inno.Shaheed Version: 0.1 (4) App Item ID: 6474969425 Code Type: ARM-64 Parent Process: launchd [1] User ID: 501 Date/Time: 2024-02-05 20:19:32.6035 +0300 OS Version: macOS 14.2.1 (23C71) Report Version: 12 Anonymous UUID: Time Awake Since Boot: 270 seconds System Integrity Protection: enabled Crashed Thread: 0 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x000000019d3c51e8 Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5 Terminating Process: exc handler [814] Thread 0 Crashed: 0 libswiftCore.dylib 0x000000019d3c51e8 _assertionFailure(_:_:file:line:flags:) + 268 (AssertCommon.swift:144) 1 SwiftData 0x00000001fed53e08 specialized static ModelContainer.currentContainer(_:) + 920 (ModelContainer.swift:144) 2 SwiftData 0x00000001fedd02d4 _DefaultBackingData.init(for:) + 364 (BackingData.swift:106) 3 SwiftData 0x00000001fedd50f0 _DefaultBackingData.__allocating_init(for:) + 60 4 SwiftData 0x00000001fed8aec0 static PersistentModel.createBackingData<A>() + 76 (PersistentModel.swift:42) 5 Shaheed 0x00000001026d9670 specialized ItemSD.init(id:supplierName:purchaseDate:unit:currency:name:quantity:price:salePrice:itemID:floor:container:cell:) + 576 (@__swiftmacro_7Shaheed6ItemSD5ModelfMm_.swift:2) 6 Shaheed 0x0000000102707798 ItemSD.init(id:supplierName:purchaseDate:unit:currency:name:quantity:price:salePrice:itemID:floor:container:cell:) + 100 (ItemModel.swift:0) 7 Shaheed 0x0000000102707798 ItemSD.__allocating_init(id:supplierName:purchaseDate:unit:currency:name:quantity:price:salePrice:itemID:floor:container:cell:) + 124 (ItemListView.swift:39) 8 Shaheed 0x0000000102707798 closure #1 in closure #2 in closure #1 in ItemListView.body.getter + 532 9 SwiftUI 0x00000001b9a7ac30 NavigationStack.init<>(root:) + 128 (NavigationStack.swift:126) 10 Shaheed 0x0000000102707574 closure #2 in closure #1 in ItemListView.body.getter + 92 (ItemListView.swift:38) 11 SwiftUI 0x00000001b9483a2c closure #1 in SheetPresentationModifier.body(content:) + 188 (SheetPresentation.swift:277) 12 SwiftUI 0x00000001b94835e4 SheetPresentationModifier.body(content:) + 960 (SheetPresentation.swift:276) 13 SwiftUI 0x00000001b881776c ModifierBodyAccessor.updateBody(of:changed:) + 1560 (CustomViewModifier.swift:293) 14 SwiftUI 0x00000001b9fca69c closure #1 in DynamicBody.updateValue() + 564 (DynamicProperty.swift:453) 15 SwiftUI 0x00000001b9fca214 DynamicBody.updateValue() + 664 (DynamicProperty.swift:445) 16 SwiftUI 0x00000001b9a4cb6c partial apply for implicit closure #1 in closure #1 in closure #1 in Attribute.init<A>(_:) + 32 (<compiler-generated>:0) 17 AttributeGraph 0x00000001ba5837a4 AG::Graph::UpdateStack::update() + 512 (ag-graph-update.cc:578) 18 AttributeGraph 0x00000001ba583fe0 AG::Graph::update_attribute(AG::data::ptr<AG::Node>, unsigned int) + 424 (ag-graph-update.cc:719) 19 AttributeGraph 0x00000001ba592828 AG::Subgraph::update(unsigned int) + 848 (ag-subgraph.cc:752) 20 SwiftUI 0x00000001b9e8a2dc GraphHost.flushTransactions() + 384 (GraphHost.swift:617) 21 SwiftUI 0x00000001b9e8b7c0 closure #1 in closure #1 in closure #1 in closure #1 in GraphHost.asyncTransaction<A>(_:id:mutation:style:mayDeferUpdate:) + 24 (GraphHost.swift:540) 22 SwiftUI 0x00000001b95345ec partial apply for closure #1 in ViewGraphDelegate.updateGraph<A>(body:) + 28 (<compiler-generated>:0) 23 SwiftUI 0x00000001b9f60e84 closure #1 in ViewRendererHost.updateViewGraph<A>(body:) + 108 (ViewRendererHost.swift:139) 24 SwiftUI 0x00000001b9f5f6e0 ViewRendererHost.updateViewGraph<A>(body:) + 96 (ViewRendererHost.swift:136) 25 SwiftUI 0x00000001b952cdb4 ViewGraphDelegate.updateGraph<A>(body:) + 84 (ViewGraph.swift:34) 26 SwiftUI 0x00000001b9e8b788 closure #1 in closure #1 in closure #1 in GraphHost.asyncTransaction<A>(_:id:mutation:style:mayDeferUpdate:) + 200 (GraphHost.swift:539) 27 SwiftUI 0x00000001b9e8b674 closure #1 in closure #1 in GraphHost.asyncTransaction<A>(_:id:mutation:style:mayDeferUpdate:) + 72 (GraphHost.swift:538) 28 SwiftUI 0x00000001b97dc464 thunk for @escaping @callee_guaranteed () -> () + 28 (<compiler-generated>:0) 29 SwiftUI 0x00000001b8db3778 static NSRunLoop.flushObservers() + 116 (StandardLibraryAdditions.swift:903) 30 SwiftUI 0x00000001b8db36e4 closure #1 in static NSRunLoop.addObserver(_:) + 36 (StandardLibraryAdditions.swift:878) 31 SwiftUI 0x00000001b8db380c @objc closure #1 in static NSRunLoop.addObserver(_:) + 56 (<compiler-generated>:0) 32 CoreFoundation 0x000000018dbbadf0 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36 (CFRunLoop.c:1789) 33 CoreFoundation 0x000000018dbbacdc __CFRunLoopDoObservers + 532 (CFRunLoop.c:1902) 34 CoreFoundation 0x000000018dbb99f8 CFRunLoopRunSpecific + 684 (CFRunLoop.c:3423) 35 HIToolbox 0x0000000198168448 RunCurrentEventLoopInMode + 292 (EventLoop.c:455) 36 HIToolbox 0x00000001981680d8 ReceiveNextEventCommon + 220 (EventBlocking.c:311) 37 HIToolbox 0x0000000198167fdc _BlockUntilNextEventMatchingListInModeWithFilter + 76 Sorry for this long crashlog

+1 to everyone here. While the thread has been viewed thousands of times, there aren't really that many actual posts (and that's across 6+ years) so I wonder if this is a much smaller issue than it seems. Alternatively, I wonder if this isn't the right place to file this issue in the first place. To rule out the latter possibility, I went ahead and opened a ticket to Apple via the Feedback Assistant (case ID FB13585955) where I also referenced this thread. If I hear back from them (not sure how public the feedback tickets are), I'll try to update this thread with the findings. Even if this issue doesn't affect many developers, I hope Apple will at least provide us with some debug steps. Otherwise, it's just educated guesses, which is very time-consuming (and wasteful).

I'm analyzing an app which is doing some processing with contacts, and stress testing it with tens and tens of thousands of contacts which are being processed. The code is being processed within DispatchQueue.global(qos: .background).async {) When the app moves to the foreground the processing starts and continues after the app moves to the background. What I've noticed is that if the app is downloaded from TestFlight, then ~20 seconds after moving to the background, a dialog is displayed saying the App Crashed. Though it hasn't actually "crashed" in the usual sense of crash - there's no crash log present on the device nor in TestFlight if the crash is reported nor is there anything reported to Crashlytics. In addition the is still displayed in the iPhone task manager, also ApplicationWillTerminate() isn't called so it wasn't killed by the OS. This doesn't happen if the app is installed via Xcode and then run (not run via Xcode, installed via Xcode, then run independently from Xcode). When running via TestFlight installation I can see the OS logging" ReportCrash recordCrashEvent; isBeta 1 app stored Received a beta app crash notification. What's going on here, why is TestFlight reporting this? Is it erroneously reporting the background processing after 20 seconds as a crash? Is there anything the app should be doing in this situation that it isn't? Otherwise why is TF popping up that dialog?

I'm trying to add a member of my team to the Testlfight app because they're saying that they were removed. If I go to the Testflight group and try to add them there, they don't show up in the list despite being a tester. If I try to add them as a tester by finding them in "All Testers", selecting them, and doing "Add to group", I get the error: "An error has occurred. Try again later." The API request and response looks like this: Request URL: https://appstoreconnect.apple.com/iris/v1/betaGroups/[redacted uuid]/relationships/betaTesters Request Method: POST Status Code: 409 Conflict Response: { "errors" : [ { "id" : "7d7f28bc-60e5-438e-9a29-f17e14b533bc", "status" : "409", "code" : "STATE_ERROR", "title" : "The request cannot be fulfilled because of the state of another resource.", "detail" : "Tester(s) cannot be assigned" } ] } I don't think this person was ever removed, so it looks like their account is stuck in a state where they're in the group but also not in the group. Any ideas for a fix?

We submitted our app last night for review with version number 7.22.1 (binary has MARKETING_VERSION = 7.22.1). While in the review queue, we continued development on a feature for the next release (7.22.2). We then finished development of the feature, and uploaded the build to App Store Connect so we could send it via test flight to our QA team. (using fastlane deliver code snippet below) This appears to have automatically updated the version number of the app in status "Waiting for Review" to 7.22.2, although the build associated appears to still be the binary with MARKETING_VERSION = 7.22.1. As of this morning the app was reviewed and approved with binary of 7.22.1 but the app store connect version number says 7.22.2. Apple Support wasn't that helpful, they didn't seem to grasp the exact sequence of events. They also told me I had no choice but to release 7.22.2 as the version code. Thankfully they were incorrect, we were able to cancel the release, decrement the version down to 7.22.1 again, and resubmit for review. Has anyone else experienced this? Is it to be expected that an app version currently in review would automatically have its version number changed if a separate build is uploaded to App Store Connect? Below are the automated emails from App Store Connect which highlight the issue we observed: 8:06 PM The status of your app has changed to Waiting for Review. App Version Number: 7.22.1 1:54 AM The following build has completed processing: Platform: iOS Build Number: 4 Version Number: 7.22.2 3:39 AM The status of your app has changed to In Review. App Version Number: 7.22.2 6:23 AM The status of your app has changed to Pending Developer Release. App Version Number: 7.22.2 Fastlane Deliver code snippet: deliver( api_key: api_key, skip_screenshots: true, skip_metadata: true, ignore_language_directory_validation: true, precheck_include_in_app_purchases: false, submit_for_review: false, force: true )

I have a app that uses my old backend. I want to switch to new backend. App is currently live on app store. I want to make a copy of this and replace it with new backend and push to testflight. I want to keep making changes to old app with old backend as well. I want to do this parallel. How do I do this?

Enviloment : TestFlight AppleAccount : sandbox The problem that is happening : Unable to get receipt with storeKit.requestReceipt Prerequisite : The form to input ID and password is displayed even if the user is already logged in to AppleAccount (not displayed when normal). The same operation is not reproduced by using the sandbox during debug builds. - (void)requestReceiptWithBlocks:(ReceiptCallback)callback { self.receiptCallback = callback; SKReceiptRefreshRequest *receiptRequest = [[SKReceiptRefreshRequest alloc] init]; receiptRequest.delegate = self; /** When start() is executed, iOS displays the "Sign in to iTunes Store" dialog if you are not yet logged in to the iTunes Store */ [receiptRequest start]; } storeKit.requestReceipt { success, receipt in guard success, receipt != nil else { if success { // receipt nil } else { // requestReceipt failed } } } Does anyone know why the receipt would be in a state where it cannot be retrieved? Thank you.

Developer succesfully pushed a new app build to TestFlight. Testers are notified but unable to perform an update. Error Message is "Could not install "app name". The requested app is not available or doesn't exist"

When trying to download TestFlight on iOS 17.2.1 the "Get" button first turns into a loading symbol, but turns back to its original form after some while. There is no error message whatsoever unfortunately. This has happend many times now, and Im not sure how to proceed here, any help is greatly appreciated!

I have a application and its been showing Waiting for Review from last 2 month. They can't share anything can't talk about review. If we send message to support they told us due to high volume we can't do. Now I am stuck what I do ? My customer is waiting from last 2 month and apple even didn't reply. Any idea what I can do now?

The app is a React Native Expo App made using React Native Libraries.A build was generated using Xcode and was shared for internal testing in testflight.Whenever a tester is trying to open the app on his/her Ios device the app is crashing after loading the splash sceen

For external testing through testflight, there is app review process. Link: https://developer.apple.com/testflight/ Planning to submit an app for external testing. However, the backend of the App is an test environment. Is that ok for the **external testing app review process **. The test environment is behind IP restriction. a. Can we provide VPN credentials to apple team for app access and complete the **external testing app review process ** OR b. Does apple team have any IP addresses, that can be add it to our testing environment.

Am I missing something or is there no feedback during the review process of an App. We had one rejected which previously had gone through, OK my error on the app side, but it would be great to recieve an email from Apple say as much. It wasn't until the App had expired and users could not login that I was aware of the issue.

i have ios application from app store, now after i updated my xcode version to 15.2 and i want to send new update but i faced this (Unexpected CFBundleExecutable Key. The bundle at 'Payload/clashofclansplanet.app/AccessibilityResources.bundle' does not contain a bundle executable.), i do some search before and find some solutions like remove CFBundleExecutable from Info.plist or delete Info.plist from build phases-> copy bundle resources, but dosn't work. this is error and it's info.plist

I read about the App Store changes for EU27 Digital Markets Act compliance. I am a UK-based developer. The UK is not a member of the EU27. However, I want to consider developing an app targeting EU27 countries. How can I setup my system so that I experience the installation experience and options offered to those of EU27 country users? Do I have to be resident in the EU27 to develop for it? Would I have to use one of those iPhone in the cloud services (to get the geolocation experience of a handset in the EU)? I would prefer some option I could select in the Developer settings app on the iPhone to toggle the EU27 experience.