I'm working on an app (actually in Test Flight) that has camera and NFC support. So in iPhone is obviously working as expected, but when testers want to try the camera "aspect" of the app on iPads they can't even download the app it says "No compatible hardware" in Test Flight. What I need to do in this case, I already have a UI/UX solution when theres no NFC support or it's disabled (Android can detect this) but here I have no clue if I'm missing something. Thanks in advance

I have got an error response when I have summit app for review. Any one face this issue please kindly help. Thank { "errors": [ { "id": "a9580e9f-103a-4a02-94c0-0a181df057df", "status": "422", "code": "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app.", "detail": "Beta Contract is missing." } ] }

I created a release app and then uploaded a test flight. so after installation and trying to open the app. app crashed. this was created on Xcode 15.2. and also this worked on Xcode 14 properly. please help us to fix this issues. please check this. this is an error log

I am trying to release a beta version of an app for internal TestFlight testing but I keep getting a notification saying it has invalid binary. I have tried looking this up but I can't find anything that helps. Please help! If you need anything in addition to this, let me know. I just wasn't sure what to share.

Hi, Since yesterday (May 11, 2023) I can no longer send an update on TestFlight for the Apple Developer account of a client on which I am admin. It gives me the following error: The last time I sent a version to TestFlight was May 4, 2023 and I had no problem. With other client applications I have no problem sending my updates to TestFlight. I have no problem connecting to Apple Connect with my Apple ID, I can see that I am an admin on the Apple Developer account. My config: macOS 13.3.1 (a) Xcode Version 14.3 (14E222b) Regards Tof

We have an enormous legacy based application which has been ported from Windows. The build system is make and has literally hundreds of .cpp, .c, .h, .m, and .mm files. I've gotten it successfully running on MacOSX and managed to build nice installation packages using the "Packages" package which have been sucessfully signed, notarized and stapled, and install nicely on "clean" Machines. The .app/bundle format has been lovingly laid out to match the app. Now, I'd like to use Testflight to deliver the app, and eventually the Mac App Store. In my first attempt, I tried xcrun altool --validate-app .. to validate the Packages built app. It, not surprisingly, failed spectacularly because I guess it hasn't kept up with however packages need to be build to pass --validate. (It's an amazing tool though) So, I decided to use pkgbuild and productbuild to build the package: pkgbuild --root App_name.app --identifier com.mycompany.myapp --sign "Developer ID Installer: ...." --scripts Scripts --install-location "/Applications/MyApp.app" Distribution.pkg productbuild --synthesize --package Distribution.pkg Distribution.xml productbuild --distribution Distribution.xml --sign "Developer ID Installer..." --package-path . MyApp.productbuild.pkg xcrun altool --validate-app -f MyApp.productbuild.pkg -u username --type macos This fails with: { NSLocalizedDescription = "Could not find the main bundle or the Info.plist is missing a CFBundleIdentifier in \U2018MyApp.productbuild.pkg\U2019."; NSLocalizedFailureReason = "Unable to validate your application."; } I confirmed I have an info.plist and if contains a valid CFBundleIdentifier, and I extracted the package using Pacifist and confirmed it's there, too. I'm at a loss. Converting the package to XCode would be a monumental effort right now, and I'd really like to avoid it. Is there something I'm missing, or should this work? Thanks!

Transaction.updates When testing on TestFlight, Transaction.updates emits payments that occur on the same device (usually within 1min after payment is finished), contradicting the docs: The asynchronous sequence that emits a transaction when the system creates or updates transactions that occur outside of the app or on other devices. Transaction.unfinished When testing on TestFlight, Transaction.unfinished contains finished payments from a different device (same App Store account). Docs: A sequence that emits unfinished transactions for the user. Both issues do not happen when testing with Xcode. Xcode 15.2, iOS 17.3, 17.4

I made the app file in xcode validate the app and then I shared it only in test fligth when I wanted to test it on my iphone 14 Plus device the following message appears try uploading other builds same thing happens with the other two apps I've been two weeks trying to solve this bug or problem, I searched for information on google but what appears is from 2014 how much appstore had the name of itunes Connect, I have asked in other forums and ddicen to wait a while that is normal but I think it takes a long time. If someone has gone through this and put you solve agadeceria you can help me

Got a little app I am trying to build before launch, I've never built a watch only app, and it requires iOS 17 so I'm a bit stuck. When creating a watch only target, it seems that the template is broken. According to this: https://developer.apple.com/documentation/watchos-apps/creating-independent-watchos-apps/ There should be a blank iOS app target, that contains the watch app. The problem is once I go to build and upload the app to test flight, I get a bundle that Xcode has no clue what to do with (Because it only contains the watchkit app, and no containing xcode app.) I'm guessing my only hope might be to create a watch only app targetted at iOS 9 with Xcode 14, then migrating to Xcode 15? I'm trying that now, but I guess I have another radar to file unless I'm missing something.

Hi guys, need some help on this issue when I submit my testing app to TestFlight using GitHub Actions and Fastlane, I get this warning from App Store Connect: We noticed one or more issues with a recent delivery for the following app: Although delivery was successful, you may want to correct the following issues in your next delivery. Once you've corrected the issues, upload a new binary to App Store Connect. ITMS-90725: SDK version issue - This app was built with the iOS 16.2 SDK. Starting April 29, 2024, all iOS and iPadOS apps must be built with the iOS 17 SDK or later, included in Xcode 15 or later, in order to be uploaded to App Store Connect or submitted for distribution. I am using React Native CLI, and Fastlane to run and build my app through Github Actions. After scouring around, from what I understood was that all I needed to do was just to update my Xcode and iOS SDK to the latest, which I did. Currently my Xcode is 15.2 and iOS SDK is on 17 already. However, I still receive this warning whenever I submit my app. Is it something that I need to resolve on my end or?

So I have an app live in the app store all good, however I am now developing an update to it that adds the ability to allow photos to be used and that requires that the app gets an additional access to the camera roll. Now on upload to testflight I get this error emailed to me, not in the interface: ITMS-90109: This bundle is invalid - The key UIRequiredDeviceCapabilities in the Info.plist may not contain values that would prevent this application from running on devices that were supported by previous versions. To me that is saying that I cant add new features to an app that requires additional permissions. Is that correct? How can I get around this, will my app get rejected when I submit it due to this, or is it just an information item?

My iOS Testflight App is crashing immediately after download/start (on all physical devices) iOS Console says: SwiftData/DataUtilities.swift:1093: Fatal error: Unable to parse keypath for non-PersistentModel Type The code is probably it is during self.modelContainer = try ModelContainer( for: Model1.self, Model2.self, Model3.self, Model4.self, configurations: ModelConfiguration(isStoredInMemoryOnly: isPreview)) modelContainer.mainContext.autosaveEnabled = true The app runs fine on physical devices in run scheme (debug or release) I have no clue how to solve this. Any ideas?

Hi, I would love to disable app sandbox completely, because my music application requires extended filesystem permissions. Like reading configuration files from $HOME and enabling services through sockets. The UI toolkit I am using endorses IPC mechanism. cheers, Joël

I had everything working with Revenue Cat. Then my app got rejected for not loading subscriptions, which was odd because a previous built was rejected for wording on that same paywall. I checked, and realised I suddenly can't fetch products in testFlight either. I can only see products in Xcode using the store kit configuration file. I've found many issues like this online and everybody point to the same solutions (that seem to work for most), but here's what I tried so far: Checked that all my agreements in App Store Connect are active Checked that ids match between Xcode / revenue cat / App Store connect Store kit config file is syncing with App Store Connect correctly I removed revenue cat and used the store kit api directly to fetch products. The array of products is empty in all environments that don't have access to store kit config file. Checked status of all subscriptions (all waiting for review -- as they were when the paywall worked) Nothing seems to work... Any suggestions? Many thanks

We have an iOS app which is currently available in AppStore. Now we are enabling Mac Catalyst support for the Mac users. As our app is contains In App purchases and it is working fine in iOS devices. But when we try to purchase subscriptions from Mac Catalyst app using TestFlight, it gives the error “Your account is not valid for use in the U.S. store. You must switch to the Japan store before purchasing.” Then after we have checked an AppStore region and the region is already Japan. Any assistance would be appreciated.

I've been getting an error when I try to install an app uploaded to Testflight that says "Could not install AppName, the requested app is not available or does not exist", two weeks ago I uploaded an app and all fine, but uploaded again several and in different ways and still gives the same error, check everything and nothing has worked, I do not know if it is the xcode or operating system (I have mac os sonoma 14. 3.1), but everything is validated well and uploaded, the problem is that it does not install, I need help, I have tried everything and I do not know what to do.

Hey everyone, I'm aware that subscriptions purchased via TestFlight expire more quickly according to schedule dictated by the sandbox environment. But what about non-consumables? Can non-consumable purchases via TestFlight be refunded in any way? I've been looking around and can't find that information.

Anyone else having issues with uploading apps into Appstore Connect? I will upload them and everything will show successful. It will show on Testflight briefly, then disappear about 30-60seconds later. I know there was an issue last week for 3days but shows corrected. I have tried uploading with transport and also xcode directly.

Users on TestFlight have started seeing this crash. Any suggestions?

Hi, I am acting as a tester for an app being developed by an external contractor and have run into an issue recently. The contractor originally sent me a test flight invite to my corporate email. At the time I didn't have a corporate phone or Apple ID tied to my corporate email so I redeemed the test flight invite on my personal phone which is logged in with my personal Apple ID even though it was sent to my corporate email. This setup worked fine. I have since received a corporate phone and am trying to switch over and we are running into some issues. Because I didn't want to log into my corporate phone with my personal credentials at setup time, I created a new Apple ID with my corporate email address. This is the same address that was used above when testing on my personal phone. I had the developer send me a new invite as the original one was months old and no longer value, but every time I attempt to redeem it, I always received an "invalid or revoked" error. We have tried several things. They confirmed that they removed the original tester account (not sure if that's the right term) that was used with my personal phone before inviting me again and have since tried multiple times to invite me. So far none of the invites seem to work on either phone now. Appreciate any advice. Thanks. Mike