TestFlight

RSS for tag

TestFlight within App Store Connect allows you to invite and manage testers who can install and beta test your iOS, iPadOS, tvOS, and watchOS apps using the TestFlight app on the App Store.

TestFlight Documentation

Pinned Posts

Posts under TestFlight tag

451 Posts
Sort by:
Post not yet marked as solved
1 Replies
2.5k Views
Hi all. My app was rejected because of this Multiline Guideline 2.3.10 - Performance - Accurate Metadata We noticed that your app or its metadata includes irrelevant references to your app’s development process. Specifically, your app includes Back to TestFlight buttons in the screenshots. Since apps on the App Store should be ready for consumers, including references to the development process in your app or metadata is not permitted. Next Steps To resolve this issue, please remove all references to the developer process from your app and its metadata, including the app description, promotional text, What's New info, previews, and screenshots. Please see attached screenshot for details. Since your App Store Connect status is Metadata Rejected, we do NOT require a new binary. To revise the metadata, visit App Store Connect to select your app and revise the desired metadata values. Once you’ve completed all changes, reply to this message in Resolution Center and we will continue the review. Bug Fix Submissions If this is a bug fix submission and you'd like to have it approved at this time, reply to this message in Resolution Center to let us know. You do not need to resubmit your app for us to proceed. Alternatively, if you'd like to resolve these issues now, please feel free to resubmit. Let us know if you have any questions about the issues we found in our review. You may appeal your app rejection if you believe this decision was made incorrectly. We also invite you to provide feedback on our review guidelines. BlockQuote And this is a screenshot As far as I understand this button appears if the app started right from the TestFlight. If you start the app by clicking on the app icon this button doesn't show up. What shoud I do in this situation? Thanks
Posted
by
Post not yet marked as solved
3 Replies
1.9k Views
TestFlight automatic updates are not working as I would expect. I have an existing TestFlight installed app on device - say version 1. I've also configured that app for Automatic Updates. I then submit an update to TestFlight, say version 1.1.0. But on device, 1.1.0 does not get installed. Instead it only says Update available and I still need to manually update. Is my understanding incorrect or is this a bug?
Posted
by
Post not yet marked as solved
8 Replies
5.2k Views
Hi team, recently after apple made TestFlight available for Mac. We want to test our mac App using testFlight for Mac. So we uploaded a new build and it got approved by Apple, But when we go to TestFlight section of it, We see status as "Not Available for Testing". The screenshot is attached below. The current state of the build is "Pending Developer Release" Please advise what could be causing the issue? Also, Is there any minimum requirement of Xcode version for a build to be test-flight ready for Mac. Example: It should be build using Xcode13 only and Xcode12 builds will not be supported for testFlight Beta Mac?
Posted
by
Post not yet marked as solved
2 Replies
1k Views
I've been trying to upload a test build using Xcode 13 to TestFlight but keep getting the following error after build is uploaded successfully: ITMS-90755: Invalid Binary - The following binaries in your app contains prohibited instructions: /Volumes/data01/app_data/awf/SWImportWorker-pv50p00ce-swpr152.cse.apple.com-400203/ff08-SoftwareImportWorker-PV_.0/VWBGHTOVAUPPUUZ65REE64UUN4/eqbyjijjamvooymq/exddmvmbsqjsrxwj/Payload/[App Name].app/[App Name]. Remove the instructions from the binaries, rebuild and resubmit. What does this error mean? What are those prohibited instructions? Where to fine them in the app binary? Any guidance is appreciated. Thanks.
Posted
by
Post not yet marked as solved
4 Replies
1.3k Views
On iOS 15.1, downloaded a new TestFlight build, and whatever I do I cannot get the feedback sharing options after taking a screenshot... This is being reported to us by some of our testers, and I have confirmed this happens for at least another developer working in a different company... Anyone else run into this?
Posted
by
Post not yet marked as solved
17 Replies
14k Views
I'm using TestFlight to test an app with payment/subscription functionality. I created sandbox accounts in AppStore Connect accordingly to be able to test the subscriptions. I'm logged in with the sandbox account. When I try to subscribe in the App the wrong account (this is my actual real AppleID) is used for the subscription although it is recognized that this is just a sandbox subscription. I tried: logging off/on into the sandbox account creating a totally new sandbox account trying to trigger the payment with no logged in sandbox account The result is always: in the payment popup it is stated that the purchase account will be my original AppleID and not a sandbox account. How can I switch the accounts? Is this a bug at Apple's side somehow?
Posted
by
Post not yet marked as solved
1 Replies
1.2k Views
So we're trying to distribute an app to one of our investors. He was previously in our internal testing group, and we have since switched to distributing the app using external testing via public link, so we've taken him out of our internal testing group and started to distribute the app that way. However, when he tries to download the app, he sees this on the app page inside of testflight: Tester Removed The developer removed you from the test program So it seems like somehow his status as a former internal tester is overriding the public link. How can we solve this? It's extremely important to get him access to the app.
Posted
by
Post not yet marked as solved
2 Replies
1.1k Views
I currently use this hack to determine a TestFlight build on iOS: https://stackoverflow.com/a/32238344/784615 Now that TestFlight also supports macOS, I wonder two things: Is there a standard API to detect a TestFlight build? In general, a TestFlight framework would be HIGHLY desirable If not, anyone knows a hack like the above that would work for macOS? I ask because the in-app receipt is called "receipt" even for TestFlight builds on macOS. Thanks in advance
Posted
by
Post marked as solved
6 Replies
1.9k Views
Hi guys, I am getting the following error when trying to upload for macOS. The same code works fine for iOS. Dear Developer, We identified one or more issues with a recent delivery for your app. Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public symbols in Contents/MacOS/***: _CMTimebaseCreateWithMasterClock. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ Best regards, The App Store Team Just FYI: I am not using CMTimebaseCreateWithMasterClock at all, but rather the preferred variant CMTimebaseCreateWithSourceClock. Neither of these are private API. Both are available. Looks like a bug in AppStore Connect? Filed FB9752311 if anybody at Apple is listening.
Posted
by
Post not yet marked as solved
2 Replies
1.3k Views
We're getting this error on all TestFlight versions currently. It's happening when anyone tries to subscribe to our in-app subscription. However, we are not making any changes to the subscription and haven't in weeks. Anyone else getting this? Any work around? Any update on a fix?
Posted
by
Post marked as solved
11 Replies
6.3k Views
Suddenly, I'm having this problem where my app crashes when I install it over testflight. I initially thought it was the CI infrastructure using Xcode 13.0 but moving it to Xcode 13.1 had the same result. Also, the problem persists when distributing from my local development machine. Building directly to my device works perfectly. It's the testflight build that fails. This is the crash Report crashlog.crash The good thing is that the App we are developing is completely Open Source and the code can be found here https://github.com/zcash/secant-ios-wallet/releases/tag/0.0.1-7 We are not using any crash reporter. The only external code we are using is the TCA dependency.
Posted
by
Post marked as solved
5 Replies
5.3k Views
We're having some strange issue with our app and/or Testflight since a few days ago: our app runs fine on simulator and devices (iOS 12, iOS 14 & iOS 15) when run from Xcode, but it crashed at launch when we archive and distribute it via Testflight for iOS 14 and below, but NOT for iOS 15 (we haven't tried to actually release to the AppStore). The app was working perfectly fine on iOS 12+ until then, on Testflight or otherwise. No crash log is ever generated by these crashes (either on Crashlytics, or Organizer, or even in the device crash logs), and what's more mysterious is that when re-archiving past versions of the code that had no issues 3 weeks ago and are live on the app store, we are now getting the crashes. We've dug into the device logs to try and get some more info, and we could find com.apple.stability.crash {"appVersion":"3.3.1","bundleID":"com.cobble.ios","exceptionCodes":"0x0000000000000000, 0x0000000000000000","incidentID":"B47DF725-343B-4D8E-A1C4-8F52EB5766C1","logwritten":1,"process":"Cobble Production","terminationReasonExceptionCode":"0x1","terminationReasonNamespace":"DYLD"} for iOS 14, and Process exited: <FBApplicationProcess: 0x10a2dd110; Cobble Producti (com.cobble.ios); pid: -1> -> <FBApplicationProcessExitContext: 0x28331a100; exitReason: (none); terminationReason: (none)> { stateAtExit = <FBProcessState: 0x283cd8cc0; pid: 4156; taskState: Not Running; visibility: Unknown>; } for iOS 12. We haven't had any luck so far figuring out what the issue(s) can be, but we've tried a lot of things from building on different computers, playing around in the build settings, updating our pods, to fully uninstalling/reinstalling Xcode and the project from Github.. It might be worth noting that we're using automatic signing from Xcode (changing that is our next test) Any help would be greatly appreciated!! We've also posted this question on StackOverflow (https://stackoverflow.com/questions/70316323/ios-app-crashes-at-launch-on-testflight-for-ios-14-and-below-but-not-ios-15)
Posted
by
Post not yet marked as solved
4 Replies
2.6k Views
I'm attempting to run the "symbolicatecrash" script on a crashlog I received from Apple, however I'm getting the following error "No crash report version in ./mycrashlog.crash at .../symbolicatecrash line 1365". Can anyone point me to a reason for this error?
Posted
by
Post not yet marked as solved
24 Replies
18k Views
I try adding people as Sandbox Testers to my App, but Apple keeps saying that they already exist on the team, even though they're not. It always show "A user with this email address already exists on the team" It keeps happening with every address I try.
Posted
by
Post not yet marked as solved
1 Replies
532 Views
Any ideas, why macOS build in TestFlight are not available for testing. I follow all requirements, but still they are not avaiable. App is builded with Xcode 13.2.1, macOS SDK 12.1. Provisioning and certificate are totally new and all needed entitlements are there?
Posted
by
Post marked as Apple Recommended
64k Views
Hi, I created an application for a client. The client put me as a developer in his team on AppStore Connect. For that I use Xcode 13.2.1. It's a UIKit application in Swift with Storyboards. I built the app => no problem I tested it on my iPhone => no problem From Xcode I made an archive and uploaded it to TestFlight => no problem The archive has been received by Apple. It was then processed by Apple => no problem And finally I received a notification that it was available on TestFlight => no problem TestFlight offers me to install it but when I try it does not install it. If I try to click on the icon of the application it shows me the message "This app cannot be installed because its integrity could not be verified." I have tried installing other apps from TestFlight and have no issues. I checked on my mac for the various certificates for this client and they are all good and valid. I don't understand why for this application I have this behavior. Someone would have any idea ? Regards Tof
Posted
by
Post not yet marked as solved
17 Replies
6.6k Views
Whenever I try to install a new build from testflight I get this error "Could not install [appname]. Your request couldn't be completed. Try again". Deleted the whole app and started again but nothing seems to work. No occured when compiling the app during development locally.
Posted
by
Post not yet marked as solved
1 Replies
410 Views
I am facing an issue when i release my application and upload it to test flight. Some of the pods are not loading their assets, others are not working properly. When I install the application through Xcode on my device it works fine for both release and debug config. I am using xCode 13.2.1 I tested the app on iOS version 12 and iOS version 15 and I always facing the same issue. Is there anybody who faced this issue please?
Posted
by