When I test an internal development build In App purchase subscription durations are greatly reduced according to the table at: http://help.apple.com/itunes-connect/developer/#/dev7e89e149d Actual Duration Test Duration 1 week 3 minutes 1 month 5 minutes 2 months 10 minutes 3 months 15 minutes 6 months 30 minutes 1 year 1 hour In an internal development build when I purchase a 1 month subscription, it actually expires after 5 minutes. **When I submit a build to iTunes Connect to use with Testflight, will my beta testers see the shortened durations (5 minutes) or will they see the actual durations (1 month)?**

I am an iOS/macOS app developer. I have an app that supports macOS 12/13/14. I have a new (November 2023) M3 MacBook Pro running macOS 14.3.1. I have a need to also run macOS 12 and macOS 13 on this same MacBook Pro so I can test the app to ensure all functionality works correctly on all supported versions of macOS. I originally intended to install macOS 12 and 13 in their own partitions and use dual (triple) boot as needed. However, this failed because the new Mac doesn't support anything older than macOS 14.1. See [How to install macOS Ventura on an M3 MacBook Pro?](https://apple.stackexchange.com/questions/469154/how-to-install-macos-ventura-on-an-m3-macbook-pro?noredirect=1#comment697872_469154) for a related post I made about trying to get macOS Ventura installed on the new Mac. Post an answer there if you know of a solution for that. Such a solution would render most of this post moot. Then I moved to virtualization. I downloaded and setup [UTM](https://mac.getutm.app) . I had no issue installing macOS 13.6 after downloading the appropriate ipsw file from Apple. But then the roadblock showed up. It turns out that macOS running in a virtual machine on an Apple Silicon host does not support the ability to log into an AppleID. See https://developer.apple.com/forums/thread/707682 for tons of comments on this. The post by Apple employee "Eskimo" near the top of the thread has the most relevant info: >- Apple silicon macOS virtual machine don’t support Apple ID logins. >- This has been true since the Virtualization framework was introduced in macOS 11. >- It’s still true in macOS 14 (currently in beta). >- This means that a number of important workflows don’t work in such VMs. >- Apple has made no official announcement about whether this will change in the future. This restriction causes the following pain points trying to do app development and testing: - You can't download any software via the App Store app since you can't log into the store. This is easy enough to work around by downloading on the host and copying to the guest VM. - You can't download any TestFlight test apps since you can't log into TestFlight. - You can't test any iCloud functionality in the app since you can't log into iCloud. I've attempted to work around some of these issues. - Running Xcode on the host, I built a development build of the app. I then copied the resulting app to a shared folder available to the guest VM. When I then attempt to run that version of the app from the guest VM, I get a dialog popup that states that "The application XXX can't be opened". - I submitted a build and made it available via TestFlight. I downloaded the app via TestFlight on the host. I then copied the resulting app to a shared folder available to the guest VM. When I then attempt to run that version of the app from the guest VM, I get a dialog popup that states that the app is no longer available due to the provisioning profile being invalid. So I can't run a development build and I can't run a TestFlight build. I did verify that I can download the app from the App Store on the host, copy that to the VM, and then successfully run it from the guest VM. It's only the development and TestFlight builds that fail. If I could run TestFlight in the guest VM then I'm sure that would work. But since you can't log into the AppleID in the guest VM, that's not an option. **How do I build my app on my host Mac in such a way that I can run it in one or more guest VMs?***

I am fairly new to Apple software submissions and wondering what the difference is between the "Beta testing review" and "Submit for approval"? We submitted our app for approval and it was approved. We could release to the App Store if we wanted to. Obviously, we wanted to test the app first. I was not sure about the difference between Internal Testers and External Testers. I chose External testers and submitted to beta for review. The app was rejected as it required access to all screens, etc. I am confused. Can someone explain what Apple reviews in beta that they don't review when I "Submit for approval"? Do they test different things? Is there a list of requirements?

I'm seeing session counts DECREASE over time when I check TestFlight for my app. It has been in TestFlight for an extended period (over a year and half) while we've been creating a new and improved alternative. CLARIFICATION: Because users are using this, after nearly 90 days we create a new build, so they can continue testing the app. I've been checking counts about once a month, and this month most of my users are showing a DECREASE in the sessions column from last month. I'm always (now) using the ALL TESTERS choice. My desire is to start asking the most active users if they are ready to test the NEW app, using the session count as an (imperfect) guide. My question: Under what circumstance can session counts decrease over time?

I'm an admin on my team's account on App Store Connect. I'm added as a tester, but I can't access builds on TestFlight on my phone, so I want to remove and re-add myself so I get the invitation again. I'm worried that this will mess something up, that I won't be able to log in and push new build to TestFlight or something. Will anything like this happen? Or can I safely remove and re-add myself as a tester?

I'm logged into App Store Connect and have two apps. If I go into one of them, is there a place where it shows the bundle ID? When I open the app in XCode I can see the bundle ID, but I'm wondering how XCode knows which app to upload to on App Store Connect.

I uploaded a build of my app to App Store Connect and submitted it to a group of external testers in TestFlight (without submitting to App Store). The build status goes from "waiting for review" to "rejected": The problem is that I didn't received the "Unresolved issues" or reviews. I searched in every page and can't find it. How can I see "Unresolved issues" of a build in TestFlight only?

I'm an admin for my team on App Store Connect, and we have several users testing our app on TestFlight. I'm added as an Internal Tester for the app, but when I open TestFlight I don't see the app (I see other apps I'm a tester for, but not this one). I went to the Internal Testers list on App Store Connect and removed and re-added myself, and immediately got an email saying "build X is read to test on iOS. To test this app, open TestFlight", which I clicked, it took me to TestFlight, and said "this build is no longer available. This build is the one I just pushed out and is available to all other testers. Does anyone know how I can approach this?

I have a small app that accepts user signups (name, email, phone, etc.), and I have logic to store a user ID on their device, after the signup process stores their data in Firebase. The ID allows the user to bypass the sign up process if they close the app and reopen it. In Expo Go, the logic works as intended; a new user is transitioned from the splash screen to the signup screen if they've never signed up before. And if they've signed up before, the app will check for the stored user ID, and they're sent to a different screen. In TestFlight, the user is always sent to the signup screen even if they've already signed up. This is my first time using TestFlight, so I'm wondering if TestFlight deletes that kind of stored data once a user closes the app. I've tried a couple different ways of writing the code, and I've been trying to find any official information on TestFlight around this scenario, but I haven't had any luck. Any insight would be greatly appreciated.

I am a developer on our Apple Developer account. I added myself to testflight as an internal tester and redeemed my code. I then switched Apple ID on my device and installed a different app for a completely different developer account. I then switched back to my first Apple ID. Now when I go into the testflight app, it says I have no apps installed. I don't have my original redeem code either (but I think that is one time use anyways). When I go to app store connect, and navigate to the app testflight page, it shows my account as "Installed" even though it is not. Some internal testers have "resend invite" option next to their name, but there is not that option next to my account. I can remove my account as a tester, and then add it again, but it makes no difference. As soon as I add myself back, it immediately goes back to showing "installed" again. I have tried reinstalling testflight and that made no difference. How do I get myself a new redeem code for this app?

I have a React Native app on TestFlight. In the past I've always had to wait about 12 hours for the TestFlight build to be approved, and then its status shows as Testing or Approved. With the app I'm working on now, its status is just Ready To Submit and it was available for Internal Testers immediately. Does anyone know what the difference between these two scenarios is? The reason I'm wondering is that the build available to internal testers now is behaving differently than I expected it too, and in order to troubleshoot this I want to know if this immediately-available Ready To Submit type of build is expected to behave differently than other builds.

I have an app on TestFlight, and I added an individual tester to version 0.1.3. I then pushed versions 0.1.4 and 0.1.5, and although this tester automatically appears under "Individual testers" for these last two builds, they didn't receive any notifications about them, so they still have only version 0.1.3. They have auto-update set to ON. Does anyone know how I can resolve this?

I have uploaded the first build of my react-native app to AppStore connect testFlight. The invitations to App Store Connect Users are sent and they have received the email. But the individual testers that I add with their email address, not receiving. any email and in the console I see the No build is available. What is going wrong here. *I am totally new to the app store connect environment*

Is there any policy change by Apple Connect while pushing to testflight. I tried pushing two build none of it showing in either in testflight or activity tab. Any help here ? I normally build app with distribution certificate and upload it to App Store. Problem is, that it won’t appear in testflight tab. I can see that build in Activity tab and App Store tab, but not in testflight. Any one faced this recently ? Screenshot show what am getting while uploading same build number means build is uploaded but not showing. I didn't get any mail from apple about error.

[These are the official directions](https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnectInAppPurchase_Guide/Chapters/TestingInAppPurchases.html) for testing with sandbox accounts: 1. Set up test user accounts within Users and Roles in iTunes Connect 2. Clear any account information stored on your test device. In settings, go to the Store settings. Click the Sign Out button. *(Note that iOS 11 does not have a section named "Store" in the settings. I go into **iTunes & App Store** and sign out from there)* 3. Connect the test device to your Mac. 4. In Xcode, set your test device as your scheme's destination 5. Open your app, and perform your in-app purchase product testing 6. Use your test account credentials to test the purchase. I have tried following these instructions, but I'm not able to complete step 6. When I launch the app after signing my Apple ID out of the App Store, it asks me to enter the password for my Apple ID. It does not give me the option of entering a different account. I don't see any way to use a sandbox account. Are Apple's instructions out of date? Should I be doing something differently? **Followup note:** It turned out that for whatever reason, trying to use sandbox accounts on my iPod Touch is a lost cause. However, I am able to use sandbox accounts on my iPad Air 2. But another team member is *not* able to use sandbox accounts on *any* of his devices, experiencing the same issue I outlined.

I am working on an iOS app, written in SwiftUI. I am already sharing builds with external testers using TestFlight, and it all works pretty much without problems. Today I enabled macOS support as well using the "magic checkbox" in Xcode. I've tested the app on my Mac, and it's good enough that I'd like to distribute this to my testers as well. Of course there is no TestFlight for macOS apps, so how do I share my build? I created an archive, but when I try to distribute using my Developer ID and sending it to Apple's notary service I get the following errors: So.. because my app uses Sign In with Apple I can't distribute it using a Developer ID? Does that mean I am required to send it to the Mac App Store? But it's not ready to be published to the wide open world yet! 😰 It seems like a rather silly situation that I can find very little information about. --- Edit: Some additional information. First of all, it all works fine on iOS. I have created a Key for Sign In with Apple. I have also created a "Developer ID Application" Profile, and it has all the needed bits: But yet when I try to manually select this Profile during the distribution process (instead of letting Xcode do it automatically) I see the following:

I am aware of this link: - https://stackoverflow.com/questions/12468180/simulating-app-upgrade-in-ios Here is my scenario: 1. I uploaded the 2.38.0 version in TestFlight. 2. I installed the app via TestFlight app. 3. I put the newer version 3.2.0 in TestFlight. 4. TestFlight signal an update for my app. 5. I updated the app. 6. All app data from 2.38.0 was deleted. My questions: 1. Is this normal? (to erase all data from the older app when updating from TestFlight) 2. How can I simulate app update?

All the beta services I've looked into (TestFlight, HockeyApp, Fabric beta, Test, DeloyGate, ...) seem to only allow one "active" build per app, or one per version (the actual x.x.x version and nothing else). For QA purposes, I would like to be able to publish builds **per branch** of my github repo. Ideally, testers would have an interface where they could install the last build of branch feature/money or feature/coins, with everything else that is already offered by regular services (push notifications, UDID handling if not using enterprise certificates, ...) Does this exist?

In a couple of weeks I plan to submit my App to Apple. I have seen the new guidelines that came out a few days ago and I'm not entirely sure that I am compliant. How can I get early feedback from Apple leaving at the same time the official submission untarnished? Can I publish my App as BETA to **TestFlight** for this purpose? Will Apple use the same examination criteria or is it more shallow? Beta submission ready via AppCenter..

I am trying to get my app into testflight for testing with "external" beta testers. The app is nowhere near complete, it is totally non-functional, and is intended as a starting point for my team to discuss UI elements. Is my app ineligible for test flight until it constitutes a certain level of "completeness" by Apple's standards? Does anyone know what those standards are? Do they differ from the requirements of completeness for an app on the store?