How to remove assembly from itunes connect?

I want to remove one of my application collections from the new itunes connect site. But I could not find the delete / delete button. Any ideas?

enter image description here

+112
itunesconnect
Sep 10 '14 at 14:16
source share
7 answers

UPDATE:

Time has changed, now you can remove TestFlight Builds, as in this answer

OLD:

I asked an apple, and here is their answer:

I understand that you want to remove the assembly from iTunes Connect as shown in the screenshot.

Please note that this is the expected behavior, since you can remove the assembly from the current assembly, but you cannot delete it from iTunes Connection. For more information, see iTunes Connect Developer Guide: https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/

So I just can't.

+115
Sep 15 '14 at 13:15
source share

Wait! You can actually complete the assembly! :)

Solution after 2017:

  1. On the main page, click My Applications, select your application, then on the toolbar click TestFlight.

  2. In the left column, select the platform (iOS or tvOS) for your application in the "Assemblies" section.

  3. In the table on the right, click the assembly number for the assembly.

  4. In the upper right corner, click "Build validity."

remove a build from App Store (iTunes) Connect Expire Build iTunes Connect

TA-dah! The build has expired on the App Store Connect. Means: internal testers and external testers will no longer be able to install this assembly

Required Role: Account Owner , Administrator, or Application Manager . See Role permissions .

For more information visit .

+57
May 15 '17 at 9:06
source share

I had this problem. I will share my ride on the learning curve.

Firstly, I could not find how to reject the binary, but I remembered seeing it earlier today in the iTunesConnect App. Therefore, using the application, I rejected the binary.

If you hover over the rejected binary information in the Build section, you will notice that a red circle appears with a button (for example, a delete button). Click on it, and then click the save button at the top of the screen. The submitted binary has already disappeared.

You should now receive all notifications that the application is in the "Preparing for download" state (email, notification of the application, etc.).

The Xcode organizer was still giving me the "Redundant Binary". After a little research, I now understand the difference between Version and Build. The version is what iTunes displays and the user sees. An assembly is only an internal tracking number. I had both in 2.3.0, I changed the assembly to 2.3.0.1 and re-archived. Now it checks and I can upload a new binary and resubmit. Hope this helps others!

+34
Sep 25 '14 at 5:32
source share

Choose assembly

The answer is that you hover over the icon for your assembly, and at the end of the line you will see a small colored minus in a circle. This will delete the assembly, and now you can click the + sign and select a new assembly to send.

This is an incredibly complex webpage with tricks and gizmos to do what you want. I'm sure Steve never saw this page or tried to use it.

Of course, it is better to design a screen so that you can see the parameters all the time, and not change the screen depending on whether you have an application in the review or not!

+6
Mar 04 '16 at 20:21
source share

As I understand the new iTunesConnect philosophy:

  • you can download multiple multiple "suitable" collections in iTunesConnect on the "pre release" tab
  • Let some other testers test a specific assembly through TestFlight (and declared by iTunesConnect users).
  • when you come to the stable version, select the correct version of the assembly, from the "Versions" tab, to send to the AppStore in the usual way.

For me, you can have 150 collections for pre-release, it does not matter.

+4
Sep 10 '14 at 14:26
source share

In our case, uninstallation was impossible due to the fact that the application was already in the preliminary version. The correction was not to delete, but to edit each section, including the version number that needed to be changed for the new candidate.

0
Apr 30 '18 at 21:33
source share

Damn, this is complicated. Here is what I did to reject / remove / replace my ios assembly before it was released. The application was approved as soon as I found a bug that I wanted to fix before release

  1. I set the release to “manual” and saved
  2. I tried to create and release an application
  3. I got an error like "you can only have one issue at a time"
  4. where there was a save button, there was no way to cancel the release
  5. the version of the application is not marked as “rejected by the developer” with a red dot

To replace the poor build I did the following

  1. if you click "+ version or platform" to create a new version, you cannot create a new version of iOS
  2. you need to load a new assembly
  3. in the rejected application, select a new assembly
  4. save
  5. send for review
0
Aug 15 '18 at 18:17
source share



All Articles