How to correctly deactivate Testflight for App transfer

Hello!


I would like to initiate an App transfer for one of my Apps. When I click the "Transfer App" button I get a message telling me that one criteria is not met: “You must turn off TestFlight beta testing for the app that you want to transfer”. I turned off Testflight by checking the checkbox "Not Available for Testing" for Internal and External testers. Unfortunately I still get the same critertia not met message.

After a google search I found out that I might have encountered this bug:


http://stackoverflow.com/questions/32906771/itunesconnect-cannot-transfer-app-because-of-you-must-turn-off-testflight-beta/32909981#32909981


Does anybody have a solution for this? Since the discussion was started already on Oct 2nd and there is still no real workaround/answer for it I am not sure if I didn't miss something else when turning off Testflight.


Is there anything else to do besides setting Internal and External testing to "Not Available for Testing" or is this indeed a bug in iTunes Connect which hasn't been fixed for over 2 months now?


Thanks!

Hello,
I'm too facing same issue of Testflight beta testing as

-> TestFlight Beta Testing
You must turn off TestFlight Beta Testing for the app that you want to transfer.


I have tried with Stop Testing from TestFlight app(I'm the only tester), but no success. So I deleted all build which shows under test-flight but still, it's same. Please let me know anyone finds a solution for this.

Thanks

Hello,


Im having the same issue.
Could you solve it?

Hi, the same problem too.

Did you find solution?

I am also facing same problem.Any solution?

I am facing the same issue.

Sent an contact to Apple some days ago, but Apple support didn't give me an answer yet.

We are currently experiencing the same issue. Sent out support to apple and are waiting the reply. If anyone comes across a resolution it would be appreciated if they post it here.

Same here

Same here...


After contact Apple, problem is apple side and i have to wait until this issue is fixed.

After one and a half weeks no changes. 😕


This post does't really help me!

http://stackoverflow.com/questions/32906771/itunesconnect-cannot-transfer-app-because-of-you-must-turn-off-testflight-beta/32909981#32909981


Any solutions? Workarounds?

I got a response from Apple that engineers are working to solve the problem, but they don't know when the issue will be corrected.


The only workaround for this problem is delete the app from your account and create it direct inside the account of the other person.

But you will lost all the app stats, like reviews and some other things.

I wouldn't even call that a work around. We also received the same response.

I am having the same problem. No response to my ticket either. Really fustrating. If I delete and publish under the new account - will people who have the app downloaded have to download from the new account or will it recognize that it is the same app?

The only way existing users can maintain continuity is when the app retains it's original bundleID, sku, etc.


Also note that if you delete an app, you lose access to it's name as it goes back into the general pool for everyone but you. I'd not delete casually...make sure that's what you want.


>No response to my ticket either.


Call em' up ...and don't let them get you off the call by sending you back to the forums 😉

The strange thing for me is that I have 4 apps that I'm transferring. I am using Fabric for beta testing, so not even using test flight. All apps have test flight settings that are identical (original settings - unconfigured). Two of the apps I am able to transfer successfully (no 'You must turn off TestFlight Beta Testing for the app that you want to transfer.' non-compliance error). The other two have this error. There appears to be no rhyme or reason to this.

Well, I spent 40 minutes with apple dev support, and like fabiobh says, they at least acknowledge they have a problem and say they are working to fix it. A couple of years ago there was a bug with MacOS where the new build stopped recognizing super drives. For 3 months Apple refused to acknowledge that there was a problem, and told everyone to buy new super drives. Finally after showing them that the super drive was working fine when I booted the MBP device into Windows, they acknowledged the problem. And 3 months later, they released a fix. So hopefully this fix comes faster than that.

The problem appears to affect randomly apps. I publish my apps using fastlane, some apps has this problem, other don't. All apps use the same config.

I am also encountering this problem and it seems like this problem has been unsolved for more than a year.

Is there anyone have solved this problem? Or having substitute workaround?

I've been waiting 6 weeks for a resolution to this. It's effecting 12 of my apps—all of which the App Review board is forcing me to transfer into individual accounts, but which I can't transfer because of this defect.


I'm constantly amazed by the utter contempt Apple holds for its developers. We're like gum stuck to the bottom of their shoe. One of the most difficult aspects of my work is dealing with the capricious and uneven assessments of the Review Board, pushing against their mandate to reject as many apps as possible, and then having to deal with the total inability of this huge organization to execute on their one single product line.

Same here, forced to transfer to individual accounts, but having test flight beta shutdown bug.


Our clients are not happy!

Ok, I have some good news. I was stuck because Apple wasn't approving my apps any more because apparently they are now requiring branded apps to be submitted from a developer account whose entity reflects the brand of the app being submitted (how dumb is that - 3rd party developers can no longer submit apps for the companies they are developing the apps for?). So they were denying my updates with critical bug fixes. This combined with the fact that I could not transfer the apps to the new developer account for the company the app was developed for due to this app transfer bug left me dead in the water.


As a last ditch effort, I submitted an expedited app review request (https://developer.apple.com/contact/app-store/?topic=expedite). Less than 24 hours later, the App Review dept called my cell phone and after explaining the problem, they granted me an approval. Once the app was approved and I released the app for sale, the test flight beta error was gone from the transfer process and I was able to successfully transfer the app.


App Review also kindly gave me a phone number to call them back. So I will surely abuse access to that number in the future 🙂.

As a followup to that last post, I have another app that was approved a couple of months ago, but I never released it for sale. Yesterday I tried to transfer it prior to releasing it for sale, and got the 'test flight beta' bug. So I released it for sale, and upon trying to transfer it, it still had the test flight beta bug. So my success transfering the app mentioned above doesn't appear to be a function of its 'approved' or 'ready for sale' status - unfortunately it seems like I'm back to my 'no rhyme or reason' assessment of the problem.

Same problem here, has anyone had this fixed?

Hi all!


I have nearly the same problem (Testflight mode BUG), but I did not ever activate testflight mode in one of two of my apps that I need to transfer.


What is going on with itunes developers? They perform poorly! They cant even fix this BUG for so long! That is awful! Will switch to android all my devices soon.


Sure, this will give no effect, but, nevertheless, did anyone find the resolution?

Same problem here. What is worng with apple? I think they are pushing every app on a single Developer account to get more money. It is completely NUTS!

Same problem here. I could transfer any of my apps before and as of today none. So angry at Apple.

Same problem 😟


Still no one was able to solve it ?

How to correctly deactivate Testflight for App transfer
 
 
Q