Is there a way to promote a version from testflight to production using the Apple Store API?

When creating a new version on App Store Connect, I cannot select an existing build from test flight. I see as an option but I cannot select it.

Today, on Dec 14, when I look for units or sales, all that occurred after December 3rd is ignored. Tens were downloaded since dec 3rd, and I could see them when connecting earlier today. When I want to set the time period, I see that any date beyond Dec 3rd is greyed (see attached screenshot). It used to work a few hours ago. This occurred immediately after updating MacOS to 14.2, but I tested on a Mac running 12.6 with the same result. Is it only me or does anyone see the same issue ? I filed a bug report: FB13468285

** I am having this issue when publishing my app in appstore and this issue does not appear in any simulator or on a real device when doing internal testing with test flight. But when testing with public link some times it shows the blank screen and after kill and re open the app for few times it works. Do any one have solution for this? I tried so many options but not worked. ** Guideline 2.1 - Performance - App Completeness We discovered one or more bugs in your app. Specifically, your app landed on a blank screen. No content was loading. Please review the details below and complete the next steps. Steps to reproduce: Launch Review device details: Device type: iPad OS version: iOS 17.1.2 Next Steps Please run your app on a device to reproduce the issues, then revise and submit your app for review. If at first you're unable to reproduce the issue, try the following: For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce. For app updates, install the new version as an update to the previous version, then follow the steps to reproduce. If we misunderstood the intended behavior of your app, please reply to this message in App Store Connect to provide information on how these features were intended to work. Resources For information about testing apps and preparing them for review, see Testing a Release Build. To learn about troubleshooting networking issues, see About Networking. Watch a video from App Store Review with tips for preventing common rejections. Please see attached screenshot for details.

Using App Store Connect, the following message is displayed when trying add an app to review: Unable to Add for Review The items below are required to start the review process: There are still attachment uploads in progress.

Hello, I'm wondering how the Small Business Program decides if an app should stay in. I read it's about crossing $1M in proceeds for the year. Just a quick check: Is this based on the App Store Connect analytics number, or do they look at other stuff? In simple terms, if I see less than $1 million in proceeds from January to December in the App Store Connect during a year, does my app stay in the Small Business Program? Thanks!

This seems like an age-old error that I've never found the answer to. I created a simple app with a button that changes a text field for a demonstration of the TestFlight app and have never gotten the internal test to work. Created another simple app. Still can't download the app in TF. I've tried just about everything, but when I choose install in the TF app I get the error. I'm the only person listed in App Store Connect as a developer, so I chose myself as the only internal tester in the group. I've tried various builds also. In TF under app details it shows that my test apps will work on my phone. Everything seems in order when I push my archived apps from XCode to the App store. Showing up as Ready to test in the TestFlight section of the App store. I have no clue what to try next, other than moving on to external testers - which looks even more complicated to configure.

According to analytics, I should have at least one sale since Dec. 3, but the Trends page won't let me see any date after Dec. 3 (if I edit the end date, dates after Dec. 3 are greyed out) and it is currently Dec. 17. Is this just me? Who do I contact if not these forums to get this fixed?

I have a problem updating an app, the upload process is normal, the problem is that it does not appear in the compilations. I upload other apps and they appear without problems but that specific one when updating appears momentarily and disappears, can you help

I currently possess administrative rights within ASC and have accepted an invitation to join a group with administrative privileges. Subsequently, there were no issues accessing ASC. However, when attempting to modify Certificates, Identifiers & Profiles and accessing (developer.apple.com), the associated account is not displayed. I'm curious whether the permission granting access to Certificates, Identifiers & Profiles is exclusive to the account owner.

Hi, just uploaded App to Test Flight and it is appear in status Testing, I need it to be Ready for submitting in order to upload it to App Store. When uploaded this builds from Archive I noticed that upload widget has been changed, it showed me two options: Upload to test and production, upload to test/ I choose the upload to test, may be this is a reason? Should I upload again with "upload to test and production"? Is there a way to move from status "Testing" to "Ready for submission"? Thanks

I would like to get the same information as on the AppStoreConnect Web UI regarding the apps installed on a testers device: When I listen to the network traffic on the web ui I see that the "/metrics/betaTesterUsages" API endpoint is called. But the same request on the official API host does not work and I don't find a way to get the same attributes on the betaTester object, e.g. betaTesterState and devices. Any help is appreciated

As the Product Manager, I want to have more control over the testing our company does before releasing an app update. Currently, I'm able to set up only one group of testors in TestFlight. But I want to be able to do a more controlled release, with more rounds of testing. Something like this: testing by only me testing by key stakeholders internal to our company testing by interested parties of our parent company testing by power users publish to app store Is there any way I can do this, given Apple's tools and constraints for app testing?

I'd like to build an enterprise "white label" iOS app - that is, apply different branding to identical templates. Guidelines 4.2.6 and 4.3 seem to prohibit this as spam. However, I found these apps which clearly share the same template: ADM Farmview Valero Cornnow Scoular View Purefield Ingredients Graincraft Grower Connect Townsend Grain ...etc There are dozens more. To see them all search: site:apps.apple.com "developed by the industry-leading Bushel platform". They have identical screenshots, description text, even version number. How can I do this, without being rejected for spam?

I got a strange App Store review rejection saying I am using this not in compliance with the developer program license agreement. "Your app is accessing and using the content of Apple Dictionary in a manner that is not in compliance with the Apple Developer Program License Agreement. It would be appropriate to include your own dictionary content rather than using the data obtained from UIReferenceLibraryViewController." But there is no where in our app uses Apple Dictionary and we have not add anything remotely near any UI code since the last release. We did move to use Xcode 15 for build and submission, how do I find out why Apple flag this as the rejection reason?

I am an SDK developer, and I provide SDKs for customers to use. I need to add the SDK to the Apple Store whitelist to prevent customer apps from being judged as fake apps and failing the Apple Store review process. But I haven't found any documentation or information about how to add the SDK to the Apple Store whitelist. Does anyone know how to operate it? Thank you！

Received 'REFUND' notification from server for 'App Store Server Notification V1'. Among the 'responseBodyV1' properties, the 'original_transaction_id' value and Should I find and process transactions that match 'unified_receipt' > 'latest_receipt_info' > 'original_transaction_id'? Sometimes there are no transactions in the history of 'latest_receipt_info' that match 'original_transaction_id'.

① Regarding the conditions for adding the privacy manifest file We publish iOS apps on the AppStore that incorporate privacy manifests and SDKs (Alamofire, etc.) that are subject to signatures. NEWS Regarding "Requirements for third-party SDKs that will be applied soon", we have already released the SDK with the target SDK installed, so "Even if the app itself is updated, the privacy manifest will not be included in the target SDK. I understand that it is possible to publish it to the AppStore without any problems without including it, but is this correct? We believe that this app's update does not fall under the "submit new apps" or "submit an app update that adds one of the listed SDKs as part of the update" and is therefore not subject to the update. Based on the above, please answer which of the following is correct? Answer A: There is no need to add a privacy manifest to the target SDK if it has been published with the target SDK incorporated. Answer B: A privacy manifest needs to be added to the target SDK even if it has been published with the target SDK incorporated. ②-1 About SDK signature Regarding the statement "Any version of a listed SDK, as well as any SDKs that repackage those on the list, are included in the requirement", unless the SDK distributor repackages and incorporates it, there is no SDK signature. But I wonder if it will be rejected by the AppStore? Based on the above, please answer which of the following is correct? Answer A: A repackaged SDK will not be rejected by the App Store even if it does not have an SDK signature unless it is included. Answer B: If you do not include the repackaged SDK, it will be rejected by the AppStore. ②-2 About SDK signature Only .xcframework is recognized as the SDK format that requires a signature, but is this correct? In other words, if you are using a binary format such as .framework, .a, or .b, or if you are using an SDK but are not using a binary format and are writing the source code directly as the application source code. In this case, there is no need for an SDK signature and there is no recognition difference. Based on the above, please answer which of the following is correct? Answer A: The only SDK format that requires a signature is .xcframework. Answer B: Apps using binary formats such as .framework, .a, and .b cannot be signed, so apps using those frameworks will not be accepted on the App Store. ③ Regarding SDKs other than “SDKs subject to privacy manifest and signature” NEWS For SDKs that are not listed in "Requirements for third-party SDKs that will be applied soon", it is my understanding that adding a privacy manifest file and signing an SDK are not required (= publishing to the App Store is possible even if they are not done). Isn't there a difference? (The above is interpreted from the wording of the relevant page, ``From Spring 2024 onward, regarding the SDKs listed below.'') Based on the above, please answer which of the following is correct? Answer A: For SDKs that are not listed, adding a privacy manifest file and signing the SDK is optional (even if it is not supported, it can be published on the AppStore) Answer B: Even for SDKs not listed, adding a privacy manifest file and signing the SDK is required. ④-1 APIs that require a reason If it is not necessary to add the target SDK manifest file for reasons such as ① above (the target SDK is already installed and does not fall under "submit an app update that adds one of the listed SDKs as part of the update" case), is it possible to publish the SDK to the AppStore in a state where there is no description of the API that requires a reason? Based on the above, please answer which of the following is correct? Answer A: If the additional requirements of the privacy manifest do not apply, there is no need to describe the API that requires a reason for the applicable SDK. Answer B: Even if the additional requirements of the privacy manifest do not apply, APIs for which a reason is required for the applicable SDK must also be described. ④-2 APIs that require a reason Is it possible to publish to the AppStore even if I write the contents of "API requiring a reason" in the privacy manifest of the target SDK as part of the app itself? (Because the repository becomes read-only due to AFNetworking, etc., it is not expected that a version with a manifest file added will be released) Based on the above, please answer which of the following is correct? Answer A: It is possible to publish to the AppStore even if the contents of "API that requires a reason", which should be written in the privacy manifest in the target SDK, are written in the app itself. Answer B: If you include the content of "API requiring a reason" in the privacy manifest of the target SDK as part of the app itself, it will be rejected. ⑤ Regarding SDKs used by third-party SDKs If an SDK listed in the list is used inside a third-party SDK, it will not be subject to AppStore rejection even if the third-party SDK does not have a privacy manifest or is not signed. But isn't there a difference? (Only the third-party SDK vendor can know about the SDK used inside the third-party SDK, and it is not something that can be guaranteed by the developer of the application that incorporates it.) Based on the above, please answer which of the following is correct? Answer A: The developer of the application that incorporates the SDK used internally by a third-party SDK does not have to guarantee it. Answer B: The SDK used internally by a third-party SDK must be guaranteed by the developer of the application that incorporates it.

Hi, We have an app live on the App Store since August 2020. We have made some 50+ updates on the app with minor & major changes throughout these 3+ years. A few months ago we submitted an update as usual with some minor changes and a new feature but got 'Design Spam, 4.3' rejection saying: We noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. 1st question, how does an app that has been doing the same things for 3+ years suddenly gets 'Design Spam' ???? Then we sent a message to App Review with some screenshots of our app's update history taken from App Store Connect console and a message stating the same question as above. We got a reply: Hello, Thank you for your reply. During our review, we found that this app duplicates the content and functionality and icon of other apps submitted to the App Store, which is considered a form of spam and is not appropriate for the App Store. Now they mentioned 'Icon' as well. So after some searching we found that another App was using our app's icon and it went live in 2023. We have had this app icon since January 2021 and instead of taking action against the other developer Apple rejected our app. Upon further communication with App Review, their replies got robotic and only copy pasted the previous response of 4.3, 4.3, 4.3... Anyways we scheduled a call with someone from App Review board and meanwhile we started the process of getting copyrights for our app's icon. The call was, as expected, unfruitful and the person on the other side of the call stated the same things as in the messages from App Review. This person was not fluent in English which communication even more difficult and hence ended without any progress. We got copyrights for our app's icon and filed a claim with Apple and their reply was quite shocking and disappointing. Apple basically said that we have contacted the other developer and this process can take a lot time so meanwhile you should try to resolve this issue on your own(I tried but was unable to attach screenshots of this communication). A trillion dollar company and this is their response to a copyrights claim. Highly disappointing. Anyways, after a few weeks the other developer changed their app icon and Apple told us so. So we made another update attempt Yesterday and once again got the design spam rejection. Hello, The issues we previously identified still need your attention. If you have any questions, we are here to help. Reply to this message in App Store Connect and let us know. Guideline 4.3 - Design We noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. We have the urge to compile a list of hundreds of apps on the App Store that do not even make an effort to be unique and simply copy exact designs of other app but we know that any further effort is useless. We have no way forward, so if anyone has any suggestions please do let us know. This post was to inform and educate on the dictatorial behaviour of a trillion dollar company. Thank you for reading.

I want to connect with teams creating and programming tools for platforms for Apple inc developers where they creating models, textures, Riggings, and Animating the model and then I also want to in connect with teams providing a dedicated servicing by live controlling for Lending the Pages and E-drafting the functionality of Operating Systems RUN on Macintosh Platform for Apple Inc. I want them to add me in their group or team as student, I learn more. Thank you Mr. Tanbeer Singh Brar [Personal Information Edited by Moderator]