No Builds Available internal testing

Seeing the same issue... I have done many TestFlight internal testing releases in the past... this is infuriating... work all day to get a build ready for a client and I can't release it for testing. Under TestFlight > App Store Connect Users > Builds it shows a green dot and says "Testing Expires in 89 Days".

Me too - exact same issue

I've got the same issue

Me too - exact same issue

We have got exactly the same issue. Added new builds for internal testing today, but nothing gets released.

This is exactly describing the problem we are having, too.

Can confirm. Same problem exactly.

Having the same issue... when Apple fixes it (assuming it's on their side), will I have to upload a new build, or will the one I'm having problems with now be available on TestFlight automatically? I got my developer account today, so this is all new to me.

I have a support case in with Developer Support... I'll post here if they get me a resolution.

I'm having the same issue. I have added additional builds, added additional versions, expired all builds and re-added, removed testers and readded. No test invitations are being sent out, and the testflight app still shows my builds as they were 3 days ago even though all of the builds that are listed on the testflight app have now been expired. Every build I upload goes through perfectly. They are all marked as "Testing" for App Store Connect users, but they are not available to be installed. I contacted Apple Developer support this morning and they were no help at all. I have unhappy customers. This is quite frustrating.

I'm having the same issue, can't get new builds on tesftlight, I even created a new app on app store connect, and the "no builds available" message is shown.

Same here. Existing builds show in TestFlight, new builds don't (despite having export compliance and otherwise showing up as "Testing" for "App Store Connect Users".

Filed ticket

Update: a new build I just submitted went through & is available in TestFlight. The only things that have changed since my previous attempts are:

1. I went through the steps to automate the "Export Compliance", bumped my version & re-built+re-submitted
2. I filed a ticket with Apple

I'm guessing either the export compliance automation fixed it (perhaps the manual export compliance tooling is broken right now?) or else someone at Apple fixed something.

This method worked for me Thank you 🙂

stup, thanks.

I just want to confirm

a) As of now (Feb 11 8:30 AM GMT), the providing export complaince in app store connect still DOES NOT WORK

b) adding the export complaince to info.plist works 😉

As soon as I addded the key and uploaded a new build, the app came though on TestFlight.

I can confirm that setting "App Uses Non-Exempt Encryption" setting in the info.plist and then re-uploading fixed it for me.

Can confirm. I set "App Uses Non-Exempt Encryption" appropriately (to NO for me), incremented the build number, archived, uploaded and Bob's your uncle.

Bonus - didn't even know that flag existed. Very nice.

Boo to apple for not responding to my or anyone elses support case in a timely manner. Plus some meaningful feedbaack in Testflight would have been awesome.

I also have the same issue .

<key>ITSAppUsesNonExemptEncryption</key>

<false/>

added this key in the info.plist

and is fixed now

I had the same problem, but it was my first build ever being uploaded to App Store Connect / TestFlight. I had added all the company members as testers and the build was showing as "Testing, Expires in 89 days", but each tester's status showed 'No build available'. Nothing I tried over the course of a day seemed to help, including doing a new build, enabling/disabling testing, etc. Infuriating.

What did fix it eventually was completely removing all testers, and then re-adding them. Voila, invitations sent. WTH Apple?

None of the above methods are working for me. Removed all users then added, created new build but to no avail. What else can I do?

Hmm. We already have the export compliance plist key, but have two out of many users with "no builds available."

Had the same issues. Deleted all testers from both internal development groups, and individually added under the build. Worked 🙄