I recently ran into this issue. One of our iPads, which had worked with TestFlight apps before, was now giving an error: “TestFlight is currently unavailable.”
Suffice it to say, this was a blocker to testing our customer’s app.
Looking at Apple’s support forums and StackOverflow, this is a common issue, and I saw no posts with solutions. Just people saying “this happens from time to time” or simply giving up because it worked on another device with another account.
So how do you solve it? A coworker, Jeff, had a suggestion – had we added the user to our Apple account?
I hadn’t thought about this. Normally, you just invite people via TestFlight in App Store Connect and it just works. But the difference here was the iPad was a corporate managed device, via Intune, and the user was a managed user, using single sign-on, aka SSO. It wasn’t a normal personal Apple account.
Click the + to add the Apple account to the list of users. Set their access level to Developer. (I didn’t try this WITHOUT that, feel free to try and update me on success)
Make sure they accept the invite, otherwise this won’t work. Apple’s invites can sometimes be quarantined/flagged as spam, so be on the lookout.
Now go to TestFlight and invite that same account to the app and ensure they have access to the necessary builds. I’m assuming you already know how to do this part, so I’m leaving those screenshots out.
Problem solved. “TestFlight Unavailable” error went away.
The “Users and Access” option.The “New User” dialog, with Developer option checked.
Other Solutions to Try
Has the app build expired?
Are there pending Apple agreements that need to be signed?
Has a certificate expired?
Did you invite the user to the right tester list?
Are Apple’s servers down? Maybe wait a day…
Do you have Internet access?
If you can’t install TestFlight (different problem, really), and it’s a managed device, have you talked with IT to have it added as an allowed / auto-installed app?
Finally… my bourbon, whiskey, tequila, mezcal, wine, whatever you want to drink + taste + collect app… Liq… is now available for both mobile platforms. What an adventure!
Originally, Liq was a website – https://liq.live. It was the easiest place to start, and start figuring out what people want. Plus, any updates I push would be immediately available to everyone. No waiting on app updates, supporting older versions, writing an API and more advanced caching infrastructure… And no app store reviews to get through, which can be troublesome in some cases.
But my users have spoken! “We want an app!” So I got to work a couple months ago and started building. Thankfully, most of the code was reusable. I found out quickly, the mobile app was the way to go. I could guarantee the experience. I could code for phones vs. tablets. And I could make it insanely simple to have such a useful tasting + collection tool anywhere users went.
Once it was done and tested – thanks Club Marzipan! – I was ready to submit. I’ve done this countless times. Every time, you cross your fingers… Let the story begin.
The iOS Story
Usually, Apple App Review is the tough part. Who knows what unknown rule you might break when submitting your first app release. Once you’re past that, the untrusting eyes are mostly off you. But still… you have to get over that first hurdle.
My initial submission was rejected. Apple found a bug I had never tested for, and they rightfully rejected the app. But not only did they reject it for the bug, they rejected it saying it’s nothing better than a website and I should add native features.
Well, that wasn’t fair, but I could see their point. Because of the bug, you couldn’t use the app. So, you wouldn’t see any of the features. I thanked them for reporting the bug, and that I disagreed about the “native” part. When working properly, Liq uses many native features. Native camera. Native photo access. Native sharing. Plus it’s, well, a native compiled app. Basically, every native feature Facebook uses except Location and Video, neither of which I need. Apple wrote back it doesn’t matter, but I ignored that – I told them “you’ll see in my next upload.”
I fixed the bug – again, thanks Apple, that was a good catch! – and re-uploaded. They came back about a day later with a new rejection reason. The bug was resolved, so that issue was removed, as was the “native” issue – phew! – that would have been an unnecessary rewrite. This time they pointed out I had no way to request account deletion. Fair point. I got to work.
I had the accout deletion fixed within a few hours. I tested the heck out of it. It worked great. I resubmitted and hoped for the best.
Two days later is was approved. w00t!
I did have some additional fixes. I let the original version get out there – it was only going to be out for a day – while I fixed some more bugs and tightened things up. Apple Reviews go much faster when you already a published verison of the app. I submitted the update and it was reviewed and approved the same day. Boom, proof.
Now, on to Android…
The Android Story
Usually, Google Play – the Android store – submission is a slam dunk. Google appears to use AI and another automated code-analysis system. I recall it being named something like The Bouncer. I don’t recall the exact name – it’s been a long time and I imagine things have changed. Anyway, given Apple’s issues were largely just Apple requirements, I figured I’d be reviewed within a day. You never know though!
I started to worry when the review had taken more than 2 days. A status of In Review for more than a few hours is uncommon. I was concerned. Alas, the rejection email came in. And it wasn’t what I expected:
First, I don’t know what “all parts of the metadata” means. I think it’s telling me my provided app screenshots and what’s in the app don’t match its description. Specifically, “track your bottles” and “see what you’ve tasted.” Let’s look at their screenshot:
So that’s their “proof” my app is misleading. But what’s this? Their screenshots show exactly what my app description details. Tastings and Collection. It’s all right there.
I’m guessing this is just a case of AI making a mistake judging my app. I don’t blame Google – they probably get a lot of submissions, and have minimal resources to look at them. Remember all those layoffs?
I submitted an appeal. They said it would take 2 days.
I received an email saying it might take longer than 2 days. OK, let’s be patient.
One week later, I finally received a notice that my appeal was accepted. All I had to do – though it wasn’t entirely clear in the email – was resubmit my app. I did that and started to wait.
Two days later, it still was In Review. “Oh, no…” I was thinking to myself… Not this again… Don’t reject me again, AI.
Thankfully, a few days after, my app was finally approved. Wow, unexpected. But I’m happy 😀🎉
Auri's Blog 