Since updating to 14.2 beta 2 I see the following error when trying to sign in to the TestFlight App on macOS. "Password reuse not available for account" It seems like it possibly affecting the AppStore too, from the device logs I see: Error Domain=AMSErrorDomain Code=2 \"Password reuse not available for account\" UserInfo={NSLocalizedDescription=Password reuse not available for account, NSLocalizedFailureReason=The account state does not support password reuse.}" I've tried signing out of the App Store to fix it but now I can't sign into either the store of TestFlight. I've also tried, multiple restarts and safe mode. Things seem fine on other platforms. Is this a known issue? Are others seeing it? Any ideas for how to reset things or what the error might be referring to?

Does anyone know how TestFlight counts the number of installs, sessions and crashes? I'm seeing totally insane numbers. I don't understand. Right now for the latest beta it shows me: number of installs "-", number of sessions 19 and number of crashes 36. What's that supposed to mean? When I look at the individual testers, sometimes there's already complete crap there. For example, there is a user who has reached 1180 crashes in 13 runs. What? Can you imagine a person who runs an application 1180 times and it crashes? I don't. What's really best, TestFlight gives me almost no crash logs. There were a few from the early betas, but none the last few days. Do you know of any other tool from which I get consistent information on absolutely all crashes?

I've already done my test on development signed app locally, all in-app purchase runs well with sandbox tester Apple ID. Errors happens when make a purchase in distribution app from TestFlight. Detail Info: in Apple Store connect , make app available to China Electron project, packaging by electron builder using distribution sign upload to TestFlight, invite myself to test using my Apple ID(not the sandbox tester) to login and purchase dialog appears and said "Account not in this store" VPN is off Apple Store shows Chinese language and Chinese apps, not llikely to be u.s. store I'm suspecting that: Maybe shouldn't use my developer Apple ID to run TestFlight test? TestFlight locked app to be in u.s. store ?

We encountered a weird situation recently. Our daily build process upload an app with a daily incremental 4-digit build number, e.g. 4000, 4001, 4002, etc. Our release build number has a specific requirement to use the date, such as 20240719. In the past I have learned that in order to upload a new build for the same version number, the new build number needs to be greater than the old one. Thus, if I have uploaded 200.1.0 (20240719), I cannot upload 200.1.0 (4001) anymore, because the daily build's build number is smaller than the release build. I have to expire the 20240719 build in order for the daily build to continue, which is fine. The problem is, yesterday I submitted 200.1.0 (20240719) for App Store review then got approved. While today's daily build is 200.2.0 (4001) and when it is uploaded, it got rejected for the following error message: This bundle is invalid. The value for key CFBundleVersion [4001] in the Info.plist file must contain a higher version than that of the previously uploaded version [20240719]. Please find more information about CFBundleVersion at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion With error code STATE_ERROR.VALIDATION_ERROR.90061 for id [redacted] Asset validation failed (-19208) This befuddles me, because the 20240719 build submitted for review is in an older release version, while the daily build 4001 is using the newer release version number. It seems that TestFlight decided to compare build numbers while ignoring the version numbers?! Furthermore, after I canceled my approved submission for 200.1.0 (20240719), surprisingly the 200.2.0 (4001) can be uploaded without an error! 😲 It seems that the only factor is whether the build is submitted or not. If an older version number higher build (200.1.0 (20240719)) is not submitted, then TestFlight happily allows newer version number lower build (200.2.0 (4001)) to be uploaded. In contrast, if submitted, then 4001 is not allowed to be uploaded! Is it an expected behavior? Thank you for the patience.

Beta testers outside the US, for our MacOS App, are being told their ID is not valid in the US Store and that they must switch to a store in their country. Yet the store switch fails Essentially beta testers outside the US cannot do testflight sandbox eCommerce for the Mac version of our app. Note that eCommerce on the Mac works for US based testers and eCommerce for the iOS/iPadOS works for testers in all territories. Many of these testers are in India, the UK and Canada. We believe that this is incorrect, that storeKit is not correctly detecting the AppStore Region for mac based testflight eCommerce. At this point we have 382 testers, most outside the US and we can only Beta Test our app with US users. Attached are images of the messages that are coming from storeKit: Here is a link to a video from a user in Canada who is demonstrating the problem (cut and paste into browser) https://youtu.be/kB818wfVld4 Here is another link to a video from a user in Canada who is demonstrating the problem (cut and paste into browser). https://youtu.be/7uAZKo8wpfU We see that there is another post with a similar problem. Similar eCommerce Problem Because eCommerce works in all territories on iOS/iPadOS but ONLY in the US for Mac we suspect that this is an error that either a DBA or a coder will need to fix. Any insights from anyone would be appreciated.

Hi there, I am trying to publish my first app (VisionOS 2.0) via TestFlight for internal testing via XCode 16.0 beta 2. I have tried clicking both 'Distribute App' and 'Validate App', but either way receive the following error: "DVTAppStoreConnect.ServiceBackendError error 1" I am a bit stuck for now, any feedback would be gratefully received! Many thanks

But this one doesn't specify where the problem is, such as the use of a private api or if it's using a key that shouldn't be used, or anything else. Now we need to find out what's causing this problem, can you give us some direction or ideas?

We are preparing a launch for iOS 18, and we experienced crashes from iOS 17 devices. If I load the app right from Xcode 16 RC to the iOS 17 device, then it works fine, but if I download it from TestFlight, the nit crashes. The app crashes immediately upon launch due to a missing symbol in the Foundation framework. I'm hoping someone can provide insights or suggestions on how to resolve this. Error Message CopySymbol not found: _$s10Foundation14NSDecimalRoundyySpySo0B0aG_SPyADGSiSo14NSRoundingModeVtF Referenced from: <C1ABDA48-29EE-3674-8554-669220A76F81> /Volumes/VOLUME/*/CamPlan.app/CamPlan Expected in: <D92E19C1-6299-3E94-8614-C505D5ABCCDB> /System/Library/Frameworks/Foundation.framework/Foundation What I've Tried Verified that the app is compiled with the latest Xcode version Checked for any usage of private APIs (none found) Reviewed usage of Foundation framework methods, especially those related to NSDecimalRound Questions What could be causing this symbol to be missing? Are there any known issues with NSDecimalRound or related functions in recent iOS versions? How can I identify which part of my code is trying to use this missing symbol?

The problem I'm having is that apps on my Apple Developer ID suddenly expire when I just upload them. When I downloaded the new version and sent it to the review team, I got the error "An error occurred while processing your request. Please try again later." I also encountered this situation before and it was resolved by the technical team. However, today, this issue continued to appear on my account. Previously supported field codes were 102388785740. I have attached a video of the incident below. Apple developer ID: Sang Nguyen | 12000621824 Profile ID: 6654899107 Application name: Swordsman JSQY Package ID: com.psm.kiemsijsqyios

I'm just setting up a new app for test flight, and have submitted a few different builds. I added an internal test group and added myself to it. It shows the status as "invited", but I never receive any invite code. How can I make this happen?

We have a game which is original a C++ project, use premake5 generated the XCode project try to ship on App Store. XCode: 15.4 Destination: Mac macOS The steps from this page, all checked. skip_install is set to NO, no dependencies. My linked libraries don't use a headers build phase Installation Directory is set to $(LOCAL_APPS_DIR). https://developer.apple.com/documentation/technotes/tn3110-resolving-generic-xcode-archive-issue Use Show Package Contents, the screenshot is how it looks, it looks good to me. Checked the config in Target-> General Destination(Mac), Bundle Identifier is set Version( 1.0 ), Build( 1 ), App Icon( AppIcon ) In Signing & Capabilities, have the Sandbox added. Use Produce-> Archive to build, but it looks it will try to compile each project for all architectures instead of just arm for me, so I'm using the command line: "xcodebuild -project /.xcodeproj -scheme -archivePath /Users/name/Documents/test.xcarchive archive" to build it. and it results successfully build, checked the log, there aren't any wired error or warning. Checked the Info.plist in the content, compare to a game project generated from Xcode, it looks like the "ApplicationProperties" property is missing, tried to menually modify the Info.plist in the content, add the "ApplicationProperties" property and the infors, then issue doesn't show anymore, but I don't think this can be the solution. Anything that missing? Thanks.

We have transferred our app from App Store Connect account to another. Transfer process was smooth and we we were able to move our app to new App Store account While uploading the new build for our app using the new account we received the below email. Can someone shed some lights on this and how can we make user to not to logout. ITMS-90076: Potential Loss of Keychain Access - The previous version of software has an application-identifier value of ['94B63VZT32.com.prasthana.tenmates'] and the new version of software being submitted has an application-identifier of ['G3M3U47GBZ.com.prasthana.tenmates']. This will result in a loss of keychain access.

Asset validation failed Invalid Executable. The executable 'xyz.app/Frameworks/OpenSSL.framework/OpenSSL' contains bitcode. (ID: 99418466-a170-4c6b-9b45-9286bb26ffe6) Asset validation failed Invalid Executable. The executable 'xyz.app/Frameworks/HPWebKit.framework/HPWebKit' contains bitcode. (ID: a6f5ae91-558a-4c23-9d09-d139132910e7)

As the title says. We can't install any mobileprovion anymore since the OS update. So does any one has a solution for this how to download and install them on your Mac. Because now I cannot continue with creating test build or build for the store.

How can I get an invitation code for TestFlight?

I am currently facing an issue with the TestFlight app on my iPhone, where I am stuck on the redeem code page and unable to access the apps I am testing. Interestingly, I am able to access TestFlight without any issues on my MacBook (MacOS), but the problem persists only on iOS. Here is a detailed breakdown of the issue: Issue Description: Upon opening TestFlight on my iPhone, I am immediately directed to a redeem code page with no option to exit or view the main screen, where I should see the apps and builds I am testing. Steps to Reproduce: 1. Open TestFlight on iPhone. 2. TestFlight opens directly to the redeem code page with no option to access other parts of the app. 3. Enter a valid redeem code (used immediately after receiving it). 4. Receive an error message stating the code is invalid or expired. 5. Attempt to access TestFlight via an email invitation link, but it redirects back to the redeem code page. Expected Result: I expect to see TestFlight’s homepage with all the apps and builds I am currently testing. Actual Result: I am stuck on the redeem code page with no option to exit, and valid redeem codes are not being accepted. I have tried using new codes, accessing the app via email invitations, and reinstalling the app, but the issue continues. Any help or guidance on how to fix this would be greatly appreciated.

Hello, we have distributed the build for "Breathegolf" app successfully from XCocde, but it did not appear in the Test Flight section of the "Breathegolf" app. We have also created an internal testing group for the app and added a tester in the group. In the Test flight section, the version 1.0.0 appeared for some times but after after refreshing, it showed "No Builds". Why this is happening? Please suggest a solution. Breathegolf, App ID - 6720740834

Please can I put my app on TestFlight after I renew my developer fee? Does it have to go through the App Store review and approval ?

Translated Report (Full Report Below) Process: Xcode [32132] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 16.0 (23051) Build Info: IDEApplication-23051000000000000~2 (16A242d) App Item ID: 497799835 App External ID: 869020508 Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2024-10-02 10:43:40.6653 -0500 OS Version: macOS 14.6.1 (23G93) Report Version: 12 Anonymous UUID: 0E2EB149-11CD-556E-AD70-0143A1FB92FE Time Awake Since Boot: 5100 seconds System Integrity Protection: enabled Crashed Thread: 9 Dispatch queue: com.apple.root.default-qos Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Xcode [32132] Application Specific Information: abort() called Application Specific Signatures: NSInvalidArgumentException Application Specific Backtrace 0: 0 CoreFoundation 0x000000019fa0a2ec __exceptionPreprocess + 176 1 DVTFoundation 0x0000000102e545cc DVTFailureHintExceptionPreprocessor + 388 2 libobjc.A.dylib 0x000000019f4ee158 objc_exception_throw + 60 3 CoreFoundation 0x000000019fabc56c -[NSObject(NSObject) __retain_OA] + 0 4 CoreFoundation 0x000000019f973f3c forwarding + 1580 5 CoreFoundation 0x000000019f973850 _CF_forwarding_prep_0 + 96 6 IDEDistribution 0x000000010ce4c810 -[IDEDistributionProcessingPipelineContext packagePathForVariant:] + 648 7 IDEDistribution 0x000000010ce40fec -[IDEDistributionCreateIPAStep name] + 88 8 IDEDistribution 0x000000010ce4a760 __98-[IDEDistributionProcessingPipeline observationForPhaseStateChanges:stepIndex:pipelineStepsCount:]_block_invoke + 96 9 DVTFoundation 0x0000000102f337d4 -[NSObject(DVTObservingConvenience) dvt_newObserverForKeyPath:options:owner:creationBacktrace:withHandlerBlock:] + 380 10 DVTFoundation 0x0000000102f345a4 -[NSObject(DVTObservingConvenience) dvt_newObserverForKeyPath:options:withHandlerBlock:] + 124 11 IDEDistribution 0x000000010ce4a624 -[IDEDistributionProcessingPipeline observationForPhaseStateChanges:stepIndex:pipelineStepsCount:] + 152 12 IDEDistribution 0x000000010ce4a998 -[IDEDistributionProcessingPipeline processForThinningVariant:distributionItem:stepClass:stepIndex:pipelineStepsCount:error:] + 420 13 IDEDistribution 0x000000010ce4a150 -[IDEDistributionProcessingPipeline process:] + 1112 14 IDEDistribution 0x000000010ce567e8 -[IDEDistributionPackagingStep loadDrivableFromExportOptions:error:] + 204 15 IDEDistribution 0x000000010ce1de20 -[IDEDistributionDriver runWithDestinationPath:wantsExportStep:] + 2000 16 IDEDistribution 0x000000010ce75eb0 $s15IDEDistribution29RecoverableDistributionDriverC3runyyFyyYbcfU + 160 17 IDEDistribution 0x000000010ce7626c $sIeg_IeyB_TR + 28 18 libdispatch.dylib 0x000000019f703750 _dispatch_call_block_and_release + 32 19 libdispatch.dylib 0x000000019f7053e8 _dispatch_client_callout + 20 20 libdispatch.dylib 0x000000019f708580 _dispatch_queue_override_invoke + 928 21 libdispatch.dylib 0x000000019f716ea8 _dispatch_root_queue_drain + 392 22 libdispatch.dylib 0x000000019f7176b8 _dispatch_worker_thread2 + 156 23 libsystem_pthread.dylib 0x000000019f8b1fd0 _pthread_wqthread + 228 24 libsystem_pthread.dylib 0x000000019f8b0d28 start_wqthread + 8 Thread 0:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x19f874df4 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x19f8875e4 mach_msg2_internal + 80 2 libsystem_kernel.dylib 0x19f87d9c4 mach_msg_overwrite + 476 3 libsystem_kernel.dylib 0x19f875178 mach_msg + 24 4 CoreFoundation 0x19f995680 __CFRunLoopServiceMachPort + 160 5 CoreFoundation 0x19f993f44 __CFRunLoopRun + 1208 6 CoreFoundation 0x19f993434 CFRunLoopRunSpecific + 608 7 HIToolbox 0x1aa13d19c RunCurrentEventLoopInMode + 292 8 HIToolbox 0x1aa13cfd8 ReceiveNextEventCommon + 648 9 HIToolbox 0x1aa13cd30 _BlockUntilNextEventMatchingListInModeWithFilter + 76 10 AppKit 0x1a31f2cc8 _DPSNextEvent + 660 11 AppKit 0x1a39e94d0 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 700 12 AppKit 0x1a31e5ffc -[NSApplication run] + 476 13 IDEKit 0x106c4f524 -[IDEApplication run] + 60 14 AppKit 0x1a31bd240 NSApplicationMain + 880 15 dyld 0x19f52b154 start + 2476

I’m facing a challenge with the App Store review process for my app to launch on Testflight, and I’m hoping for some advice or insight from the community. Our app exclusively uses passkey authentication—no passwords are involved. Passkeys are stored on the user's device and in their cloud account, making it impossible for us to provide the traditional username/password combo that the App Store review team requested and we are getting our review requests rejected because of this. There’s no way to grant access to an already created passkey or use any other form of authentication. The only viable option is for the review team to create an account themselves using passkeys, which works seamlessly in our app. Has anyone else dealt with a similar situation? how can we approach it? Any advice or suggestions would be greatly appreciated!