Apple TestFlight: "this version is no longer available for testing" [closed] - ios

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
I've been using TestFlight for my internal beta testings, everything was set and it was working for a while. after one of the submitted binaries got rejected from AppStore review, there seems to be a problem.
On any new uploaded binaries and turning on the Beta testing switch in iTunes Connect, I get the notification from testflight app that the new version is ready to be downloaded but on the app it says "UNAVAILABLE Expires in 30 days" and when I click on the beta app in TestFlight, on top it says "This version is no longer available for testing" even though the expire date is in a month from now.
Any workarounds for this?

So I solved this issue, not once but twice, apparently it's a bug.
what you have to do is turn off all the beta testings and then turn on the one you want to test, and then it works :)

Related

App disappeared from AppStore [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 6 years ago.
Improve this question
I published my first App a few days ago (actually: two Apps; one Ad-free Version for Pricetier 1 and a free Version with Ads), and after the initial ~24 hours to show up in the AppStore it could be found by searching for "Dotoro" (the name of the App).
That was until yesterday afternoon. Since then, the App is nowhere to be found when searching from an iOS-Device:
I have not made any changes to the App after the initial release and iTunes Connect lists it as "ready for sale".
However, the direct Links on a Mac/PC do still work:
https://itunes.apple.com/app/id1104775660
https://itunes.apple.com/app/id1107224494
https://itunes.apple.com/us/developer/jan-udo/id1104775659
Is there anything i can do about this? What's the reason an App can't be found by the search anymore?
EDIT: The Apple support status website is now showing an issue for the app store, starting at 11 AM. The issue seems to be fixed at 7:30 AM
You can check Apple servers issues on this website.Today seems to be a normal day.
I advise you to open a support ticket. I check your apps on my Ipad and can not get them too. However, the autocomplete form shows me your two app names.
Hope it will help !

Upload new iOS binary without a release [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
I just submitted a new version of my application (version 2.0) to Apple and it is Waiting For Review in the App Store. I set it to release manually as we are strategically planning a release.
We have a more feature filled version of the app (2.1) ready but we want to make sure the first version passes Apple review first.
My question is, once Apple accepts 2.0 are we going to be able to upload 2.1 without releasing 2.0 live into the app store?
You cannot have two unreleased versions at the same time.
When you have only a version that's live on the app store, the iTunes Connect UI shows these buttons:
When you have a version pending developer release (or waiting for review, or otherwise not on the store), the iTunes Connect UI shows these buttons:
As a result, you do not have the option to create a new 2.1 version without pushing 2.0 live on the store.
You will see two statuses - one for 2.0 that will be green once it is approved and on the store, and one for 2.1 that will be yellow - waiting for review. You can always have a live binary and one waiting for review :)
Yup, you will be fine. No need to release 2.0 :)

iOS TestFlight build notification e-mails repeatedly not being received [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
We're building an iOS app in iOS 8 using Apple's version of TestFlight (integrated with iTunes Connect, of course). However, the system regularly refuses to send the "new build" notification e-mails to internal testers. In order to get build notification e-mails, I have to remove users from the internal testers group and re-invite them. Even when I have done this, the build notification e-mail (although it lists the desired version of the app) doesn't actually trigger an update in my TestFlight iOS app.
Points to note:
I have the Connect and TestFlight apps installed on my phone.
This has worked in the past with earlier versions of the app.
I have found other similar questions on Stack Overflow such as this and this one, but none of them seem to deal with the "this happens to me repeatedly" problem. Besides, most of them seem to suggest "remove all internal testers, disable beta testing on the app, then re-add them all" which is not a sustainable solution when we'd like to release multiple new builds per day through our continuous integration system.
Does anyone have any ideas?
ETA: I found an Apple Developer Forums thread on the subject. Not much help but it might be in future.
I had the same issue, Making changes to the "What to Test" field in the Build page and saving caused notifications to go out instantly for me.
When you upload a new build wait for a bit (I wait an hour) for all the processing to finish, then add the What to Test info and hit save. This seems to work for me quite well.
Using Edit, I removed the testers and saved. It says you can't test without testers. I added existing testers to the new build and saved. When I refreshed the page, it said they were notified with the current date.

iTunes Connect Submit For Beta App Review no option to disclose IDFA usage [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
Today I uploaded a new build from Xcode to try the new TestFlight external testing program. After I submitted the beta app for review it was rejected because of "Undeclared Use of Advertising Identifier [IDFA].
I know I'm using the IDFA for ad tracking, and I have no problem declaring that, but the TestFlight submission process has no place to declare this. When I've submitted to the real app store there were questions I answered about the IDFA, but it seems the External Testing review flow does not have the same questions. It only asked about Export Compliance then I submitted.
Tried uploaded a new build and had the same problem again. Something I'm doing wrong or bug in Apple's new flow? Anybody else seeing the same problem or worked around this?

iphone app rejected but with not notification email [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I've recently had my app rejected, but they have not sent over the "explanation" email yet. has anyone experienced a rejection without a tandem explanation or reasoning from app review?
When your app is rejected without a letter, it usually means it crashed. Check it out again and resubmit.
Could be the app not being compatible with OS 3.0.
Check this: techradar.com - New iPhone Apps Must Be 3.0 Compatible
same thing happened to me, my app was rejected sometime last night, but I got no notification. It would suck if it was the 3.0 compatible issue because my app was submitted almost a week before that email came out.
Relax, we've got an app rejected in March, now it's July and we never got any explanation: sometimes they just don't send anything

Resources