I have an app in the App Store that doesn't need to be sandboxed (it's been in the MAS since 2010, before sandboxing became mandatory for new apps). I have run into an obscure bug that ONLY appears when the app was installed by TestFlight, but not when I run the same executable from before the upload (taken from the very same archive). I suspect it's a bug around the installed receipt or is codesign related, because that's the only things I am aware of that would be changed between my upload and the re-download via TestFlight. To debug this, I have built a small test project that I want to submit to DTS, demonstrating the bug in a clear and direct manner. But when I try to upload it, even for "internal testing" only, the upload gets rejected automatically because it's missing the App Sandbox entitlement. However, if I add the entitlement, then my app won't work, so I cannot enable it. Hence I need to get an exception from App Review so that they allow me test app being uploaded without the sandbox entitlement. I know that's possible because otherwise I'd not be able to upload my regular application, which I did just the other day. How do I get this resolved? Would a member of the App Store team please contact me? The Apple ID for the test project is: 410006334. Or, alternatively, you can also use the newer 6503298614 (I tried the other in hopes it would be allowed not to be sandboxed because I had created it long ago, but that didn't work out).

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.

Imagine you accidentally made a build of your app with version 2 and uploaded that to App Store Connect for TestFlight even though you're still working on version 1.x and continue to do so with your public releases. Here's an example: The build 55 is the accidental 2.0 version, but the current releases are 209 and 210 with a lower string version. So, that one build of version 2 was a mistake. Sadly, you cannot remove it, even it has expired, even if it has never seen the outside of TestFlight. And it's a bit annoying too, because it stays up there at the top of your builds, and always presents the outdated version when you visit that page on App Store Connect. But worse is the fact that because of this, any version 1.x you release since then will not get you any crash reports or feedback that the user may have submitted to you. This is clearly a bug, and I was able to verify this just recently. I suspect this happens because Apple wants to avoid storing and forwarding reports for outdated versions, maybe to save space on their servers. That makes somewhat sense, though I've also had people finding crashes in older versions that were not fixed in the latest version, so I'd still like to get those reports from older versions. However, if Apple really only wants to keep crash reports and feedback msgs from the latest release, then Apple's mistake is that they use the unreliable string version to check which is the latest version instead of using the build number, which is ENFORCED by Apple to always be incrementing for each upload. If you are in the same boat, please comment so that we can make it clear to Apple that this is not an isolated issue.

Update: Turns out it works for others, apparently, and I also found one of my Macs where it does work, too. So it must be something pertinent to my systems. Oddly, though, the same ones where it now fails used to work because I had TestFlight enabled there before. I have TestFlight set up on App Store Connect, and I have already about 50 testers subscribed. Today, I found that the Public Link does not work any more: Once TestFlight.app is installed, and one clicks the link to add my app to TestFlight, it always shows the error ""Unable to Open Link" in TestFlight.app: I've tried this on several Macs (Ventura and Sonoma), and with different Accounts, both where the app was already added or not. Is something generally broken, i.e. do others see the same issue with their TestFlight links, or is it just me? How do you suggest I get this resolved? Here's an example link I set up for this purpose - it only allows a handful of subscribers, so please do not actually subscribe but just see if you even get allowed to, or if you get the same error if you must try: https://testflight.apple.com/join/oV8NNojg And here's how it's set up:

Hi, I would like to know if ios 17 sdk is compatible with react native version 0.64. I am not able to build my app currently.. Error that i got when build Undefined symbols for architecture x86_64: "_GULLogBasic", referenced from: _MLKLog in MLKitCommon[x86_64]7 "OBJC_CLASS$_AppCenterReactNative", referenced from: in AppDelegate.o "OBJC_CLASS$_AppCenterReactNativeAnalytics", referenced from: in AppDelegate.o "OBJC_CLASS$_AppCenterReactNativeCrashes", referenced from: in AppDelegate.o "OBJC_CLASS$_FKUserDefaultsPlugin", referenced from: in AppDelegate.o "OBJC_CLASS$_FlipperClient", referenced from: in AppDelegate.o "OBJC_CLASS$_FlipperKitLayoutPlugin", referenced from: in AppDelegate.o "OBJC_CLASS$_FlipperKitNetworkPlugin", referenced from: in AppDelegate.o "OBJC_CLASS$_FlipperKitReactPlugin", referenced from: in AppDelegate.o "OBJC_CLASS$_GDTCORTransport", referenced from: in MLKitCommon[x86_64]6 "OBJC_CLASS$_GTMLogMininumLevelFilter", referenced from: in MLKitCommon[x86_64]200 "OBJC_CLASS$_GTMLogger", referenced from: in MLKitCommon[x86_64]26 OBJC_CLASS$_MLKITx_GIPLoggingReroutingGTMLogger in MLKitCommon[x86_64]200 "OBJC_CLASS$_GTMSessionCookieStorage", referenced from: in MLKitCommon[x86_64]26 "OBJC_CLASS$_GTMSessionFetcher", referenced from: in MLKitCommon[x86_64]26 "OBJC_CLASS$_GTMSessionFetcherService", referenced from: in MLKitCommon[x86_64]18 "OBJC_CLASS$_GULCCComponent", referenced from: in MLKitCommon[x86_64]11 "OBJC_CLASS$_GULCCComponentContainer", referenced from: in MLKitCommon[x86_64]3 "OBJC_CLASS$_GULCCComponentType", referenced from: in MLKitCommon[x86_64]3 "OBJC_CLASS$_GULUserDefaults", referenced from: in MLKitCommon[x86_64]2 "OBJC_CLASS$_RCTBundleURLProvider", referenced from: in AppDelegate.o "OBJC_CLASS$_RCTLinkingManager", referenced from: in AppDelegate.o "OBJC_CLASS$_ReactNativeNavigation", referenced from: in AppDelegate.o "OBJC_CLASS$_SKDescriptorMapper", referenced from: in AppDelegate.o "OBJC_CLASS$_SKIOSNetworkAdapter", referenced from: in AppDelegate.o "OBJC_METACLASS$_GTMLogger", referenced from: OBJC_METACLASS$_MLKITx_GIPLoggingReroutingGTMLogger in MLKitCommon[x86_64]200 "_kGTMSessionFetcherStatusDomain", referenced from: ___69-[MLKModelDownloader beginModelDownloadWithURL:modelInfo:conditions:]_block_invoke.285 in MLKitCommon[x86_64]18 ___150-[MLKITx_PHTHeterodyneSyncer batchSyncWithAccounts:syncedScopes:fetchReason:throttlingCache:heterodyneSyncInfo:accountToAuthToken:lastError:callback:]_block_invoke in MLKitCommon[x86_64]48 ___91-[MLKITx_PHTInternalHeterodyneSyncer syncHoldingLockWithSyncedScopes:fetchReason:callback:]_block_invoke in MLKitCommon[x86_64]51 ___63-[MLKITx_GMVCloudVisionClient initWithCloudUri:apiKey:options:]_block_invoke in MLKitVision[x86_64]7 ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) Undefined symbol: _GULLogBasic Undefined symbol: OBJC_CLASS$_AppCenterReactNative Undefined symbol: OBJC_CLASS$_AppCenterReactNativeAnalytics Undefined symbol: OBJC_CLASS$_AppCenterReactNativeCrashes Undefined symbol: OBJC_CLASS$_FKUserDefaultsPlugin Undefined symbol: OBJC_CLASS$_FlipperClient Undefined symbol: OBJC_CLASS$_FlipperKitLayoutPlugin Undefined symbol: OBJC_CLASS$_FlipperKitNetworkPlugin Undefined symbol: OBJC_CLASS$_FlipperKitReactPlugin Undefined symbol: OBJC_CLASS$_GDTCORTransport Undefined symbol: OBJC_CLASS$_GTMLogMininumLevelFilter Undefined symbol: OBJC_CLASS$_GTMLogger Undefined symbol: OBJC_CLASS$_GTMSessionCookieStorage Undefined symbol: OBJC_CLASS$_GTMSessionFetcher Undefined symbol: OBJC_CLASS$_GTMSessionFetcherService Undefined symbol: OBJC_CLASS$_GULCCComponent Undefined symbol: OBJC_CLASS$_GULCCComponentContainer Undefined symbol: OBJC_CLASS$_GULCCComponentType Undefined symbol: OBJC_CLASS$_GULUserDefaults Undefined symbol: OBJC_CLASS$_RCTBundleURLProvider Undefined symbol: OBJC_CLASS$_RCTLinkingManager Undefined symbol: OBJC_CLASS$_ReactNativeNavigation Undefined symbol: OBJC_CLASS$_SKDescriptorMapper Undefined symbol: OBJC_CLASS$_SKIOSNetworkAdapter Undefined symbol: OBJC_METACLASS$_GTMLogger Undefined symbol: _kGTMSessionFetcherStatusDomain Linker command failed with exit code 1 (use -v to see invocation)

We created an app for iphone which includes a Watch app. The app works well during debugging, and also in TestFlight the Watch app installs nicely and does what it is supposed to do. However, when we make the app available through the Apple Business Manager (the app is for internal use by a company) the Iphone app downloads without problems, but the app for the Apple Watch does not work. When I go to the Watch app on my Iphone (where you can manage the apps on your Watch and so on) my app is listed, but when I press install I see a loader for a few seconds, then it stops but nothing else happens. So the code seems to be good, but after I download the app with a code through the Business Manager, then I cannot install the Watch version of the app.

I faced thta issue 2 days ago and today. The distribution certificat is installed in thekeychain and provision profiles gives no error when I'mm builing the arhive. But when I select App Store Connect as distribution. method it gives me an error that "App Store Connect access for ___ is required. What is the reason of that? Did someone face the same issue recently? Restart XCode and laptop did not help. I used to distribute the builds for individual account this way many times, but. now smth seems. to be changed or broken.

Hello, I have encountered this error in all the applications I have listened to so far on my individual developer account and I cannot test it. I heard that different developer friends of mine are experiencing this problem, especially on individual accounts. All test users I added to my account also have this problem. They all have different phones and operating system versions. I tried a lot of solutions on different computers, Xcode versions, etc. But I couldn't find a solution. Could you please help with this?

Hello. I received a rejection on a new application in the first release for some unknown reason: 2.1.0 Performance: App Completeness Bug description: Specifically, no action occurred after completing in-app purchase. and a screenshot of the paywall with products (prices). My products load from RevenueCat, and when tested in TestFlight, there are no issues. Please tell me what could be the problem?

Our release engineer encounters Asset validation failed error with various reasons (90240, 90270, 90242, 90259) on Transporter. If I upload same ipa file by Transporter on my dev machine, I can successfully upload. Both machine installs same version of Xcode and Transporter. My system is M1 macbook and his system is Intel macbook. Other than that, I don't see any differences. I have no idea why his machine does not work. Any thoughts? Thanks

Hi, I am on version 2.2.11 of my app and I need some specific things tested. Honestly, I haven't had much luck with friends downloading and testing my app. I want people who will push the limits of the first flow of my app to hopefully produce edge cases which I can then fix. I don't mind paying. Any there any good services I can use to buy a batch of testers? Is this approach above-board as far as Apple is concerned? Thanks, Ryan

Hi, I'd received an invitation for test flight, but first, i need to join their development team. I'd received the email invitation for joining the team. Click "Accept Invitation", and prompt to log in. Success. But, I'd received "Cannot proceed with the request" message. Although, I'd try 2 different account tester. When, I click, "Contact Us". This page appeared. And I realize that, sometime, I didn't receive the invitation link although my teammate had sent it multiple times...

When attempting to add a recent build to an External test group, I am receiving the error: This build is using a beta version of Xcode and can’t be submitted. Make sure you’re using the latest version of Xcode or the latest seed release found on the releases tab in News and Updates This build is a macOS app built with Unity, which is then codesigned, packaged with productbuild, and then uploaded with xcrun altool --upload-package. The version of Xcode being used was released about a week ago. Xcode Version 15.4 (15F31d), built of an Intel Mac Mini running macOS 14.4.1 (23E224). I have seen threads in the past about this, but nothing recent. (1,2)

I uploaded a build to testflight and released it to Internal testers, however when the testers tried downloading the app a alert dialog shows the following: Could not install [App] The requested app is not available or doesn't exist. Also tried to submit it via external testers but getting another error.

One of our apps got hit by the ITMS-91065: Missing Signature issue when we attempted to distribute it to externally via TestFlight. The email said FirebaseCore is missing the signature file within our own framework. After investigation, I realized our recent update to the version of Firebase that has the proper signatures and privacy manifest wasn't enough by itself. Similar to Apple's own instructions on embedding static frameworks since Xcode 15, Firebase instructs us to select the Embed & Sign option. After making the appropriate changes though, we're getting the error in Transporter: Asset validation failed (90085): No architectures in the binary Our setup is as follows: We have an analytics dynamic framework, which depends on Firebase's static framework. The Firebase related frameworks are embedded and signed in our analytics framework. Our app depends on the analytics dynamic framework, which now includes Firebase frameworks within its framework. Since the Firebase frameworks are static, only the Info.plist and the resource bundle with privacy manifest and another Info.plist are included. After searching online, some suggest it's because of the Info.plist included. For example, FirebaseCore.framework, which specifies CFBundleExecutable yet it's not included within the framework itself. I don't expect the executable to get included here though. I opened an issue on Firebase's Github, which has more information. I am not sure how to proceed from here. Is there something I am missing? I would appreciate assistance. Thank you.

I have a team member who was deleted. I tried to re-add that team member immediately after deletion but that failed. However, portal still recognizes that user as a member of the team. This results in the following behavior. When trying to re-add the user to the team, I get a message saying they are already on the team. No new invite can be sent because I can't complete the add-user operation. In TestFlight, I do not see this user on the list/roster of possible internal testers. Has anyone seen this behavior before and if so, how did you fix it?

When start app from TestFlight and macos >= 13，has a code signature invalid error '/Applications/mac-ci-appstore.app/Contents/Frameworks/***.framework/Versions/A/***' (code signature invalid in <BED9CDF6-C616-3AB0-819F-7B6FD5896709> '/Applications/mac-ci-appstore.app/Contents/Frameworks/***.framework/Versions/A/***' (errno=1) sliceOffset=0x00004000, codeBlobOffset=0x000A3880, codeBlobSize=0x00006EF0), start it from macos <= 12，no error happen，how to fix it on macos >= 13，I have no idea. all devices add in device lists. codesign verify then app is ok too.

I've been developing a solution that has an embedded USB driver. I can build and run my solution just fine but I cannot pass verification for uploading to App Store Correct and TestFlight The problem is that the provisioning profile I am using (for development) does not have the explicit Vendor ID (idVendor) but is using the development value of asterisk "*". I've created a release version of my entitlements file with the proper Vendor ID and I have a distribution certificate for iOS. Further, I've created a provisioning profile for app-store distribution (not development) and imported it via Xcode. When I select this provisioning profile, I get the following errors from Xcode: Xcode 14 and later requires a DriverKit development profile enabled for iOS and macOS. Visit the developer website to create or download a DriverKit profile. Provisioning profile "MyProvisioningProfile - App Store" doesn't match the entitlements file's value for the com.apple.developer.driverkit.transport.usb entitlement. If I create and use a DriverKit profile, The Xcode UI errors go away on the "Signing & Capabilities" page. However, these profiles seem to be for development only. I then get an error, during compilation, telling me that the app and extension have two different signers, one for development (DEXT) and one for distribution (App). To sum up, using a DriverKit profile fails during the build process and using a distribution profile is a non-starter for Xcode. I can't even build. What do I need to do to get this to work?

Hi all, I’m currently developing an App Clip, and for our first version, I want to exclusively use the default app clip link generated on App Store Connect to invoke the App Clip (of the form https://appclip.apple.com/id?p=<bundle_id>). I've published a build to App Store Connect, and I can see it has generated the link.
 There is good documentation around testing App Clip invocations when using an associated link pre-release, but not so much for testing the default link.
 I've read some things online that would suggest that the default App Clip link is not able to be tested before App Store approval, as the link only becomes active at this point. If that is the case, can we test the default App Clip link invocation via an external beta TestFlight release, or do we need to fully release the app to the App Store to test the link invocation?
 Any insights or experiences you could share would be greatly appreciated.

I've tried uploading a build through xcode, and transporter app with no luck. I have waited hours and it never completes. Also, I have tried using fastlane our main way of uploading builds and have included a verbose flag to see why the build upload never finishes or errors out. The problem is an endless loop of the following error: DEBUG [2024-05-09 16:11:52.04]: [altool]: "LocalUploadTask &lt;EF4ED1D8-1CB0-47F7-876B-C126DF9A3696&gt;.&lt;302624&gt;" DEBUG [2024-05-09 16:11:52.04]: [altool]: ), NSLocalizedDescription=A server with the specified hostname could not be found., NSErrorFailingURLStringKey=https://northamerica-1.object-storage.apple.com/itmspod11-assets-massilia-200001/PurpleSource211%2Fv4%2F22%2F2d%2F17%2F222d1786-e205-57c4-7c62-a8e88503ff18%2FNRkOOpVWKZwGMd9KSYr92VImlIecE45alTBupZzt5Z0_U003d-1715285171894?uploadId=951d5230-0e3f-11ef-be19-783fd2f0b3f1&amp;Signature={REDACTED}&amp;AWSAccessKeyId={REDACTED}&amp;partNumber=1&amp;Expires=1715889972, NSErrorFailingURLKey=https://northamerica-1.object-storage.apple.com/itmspod11-assets-massilia-200001/PurpleSource211%2Fv4%2F22%2F2d%2F17%2F222d1786-e205-57c4-7c62-a8e88503ff18%2FNRkOOpVWKZwGMd9KSYr92VImlIecE45alTBupZzt5Z0_U003d-1715285171894?uploadId={REDACTED}&amp;Signature={REDACTED}&amp;AWSAccessKeyId={REDACTED}&amp;partNumber=1&amp;Expires=1715889972, _kCFStreamErrorDomainKey=12} DEBUG [2024-05-09 16:11:52.04]: [altool]: 2024-05-09 16:11:52.048 DEBUG: [ContentDelivery.Uploader] Created new upload task (0x139d071e0) for part 1. DEBUG [2024-05-09 16:11:52.04]: [altool]: 2024-05-09 16:11:52.048 DEBUG: [ContentDelivery.Uploader] Saving uploader state (CDUploaderStateUploadAssetDescription) for identifier 'com.apple.cds_0C29B49B-B8A0-45FA-BFF3-10A7424FE286'. DEBUG [2024-05-09 16:11:52.04]: [altool]: 2024-05-09 16:11:52.049 DEBUG: [ContentDelivery.Uploader] There are 2 parts remaining to upload. DEBUG [2024-05-09 16:11:52.04]: [altool]: 2024-05-09 16:11:52.049 DEBUG: [ContentDelivery.Uploader] LOST 0 bytes for part 2. DEBUG [2024-05-09 16:11:52.04]: [altool]: 2024-05-09 16:11:52.049 DEBUG: [ContentDelivery.Uploader] Adding upload task 302627 for part 2.