I've been having similar issues with one of our apps, the reviewer can't seem to log in and keeps getting network error messages. No customers have had any issues, I've tried logging in to multiple accounts including the apple reviewer account on multiple networks and I have no issues whatsoever. It's really frustrating.
I had the same issue once and was convinced that I must have pointed the reviewer account to the wrong server. I spent 2 days debugging before I finally asked the reviewer to check their network connection, I was approved the next day. They did send a nice response admitting the issue was on their end, lesson learned.
Yep, I've been hearing a lot of issues like this for the past week. It's definitely an issue with their internal test servers, and even though hundreds of different apps are having the exact same issue, they keep insisting it's the devs fault...
I don't think the problem here is with the QA workers. This is clearly a bug in the underlying internal test framework, which the QA workers have very little info about. And the likelihood of a given worker seeing enough of these errors for them to realize it's an issue with the system and not the app is fairly low.
The real issue is that the engineering team who maintains the internal app checking system 1. needs to have infrastructure to detect abnormal amount of a given error and 2. need to notify the QA team so the QA team can communicate it with the devs, rather than just blaming the apps.
You'd think people would look at the initial healthcare.gov mess and make some conclusions.
One of which should maybe be "Don't strictly isolate teams, with unowned space between their output and the next team's input, and no method by which post-delivery failure reflects back on them."
1,000 - 2,000 dedicated quality assurances workers could review between 1 to 2.5 app per hour each week. Adding more personnel cuts this number down drastically.
It certainly can be done. Besides, this is a problem Apple has decided it can handle, since it decided that its customers can't benefit from competition between app stores with different approval processes.
In my opinion, legitimate competition between App Stores would make the iPhone strictly worse for myself and for everyone I know that owns an iOS device. For me, the mandatory app review process is the big differentiator between the iPhone and Android and is the main reason why I have not switched.
There are over 4 million of software engineers in the United States alone, and I'd wager that many of them are capable of doing QA. Apple is a company that is able to pay competitive wages for their talent.
I'm a software engineer, and I would never want this job. It's got to be incredibly boring and tedious.
Most reviews are for minor app updates. "Bug fixes and performance improvements." Ho hum. Twitter and many other companies release app updates every week, just because they can.
I suspect the job of app reviewer has a pretty high turnover.
> I'm a software engineer, and I would never want this job. It's got to be incredibly boring and tedious.
That's cool, but testing roles exist throughout the industry and some people choose QA as a career.
I wouldn't want to be an IT support specialist, it sounds like a boring job to me, but that doesn't mean that there aren't a million career support specialists employed by trillion dollar companies like Apple.
I'm sure people would line up to be paid well to work on Apple's QA even if you wouldn't.
But, you're a software developer. As a developer testing isn't the exciting part of your work.
I'm also a dev and have had the chance to work with top notch QA testers. A good QA engineer is a blessing. Unfortunately that is not what an apple app reviewer does. Their work is much more boring.
Some software engineers are in it for the pay. If you offer them a relatively easy (even if repetitive) job for the same pay, they will jump on it. You can't judge these types of thing based on your personal preferences, you have to take a step back and look back at all the people you knew in college, I think you'll remember some who would be perfectly fine with this line of work.
As a consumer, I'd rather Apple sometimes do a bad job and sometimes piss off developers than do nothing. I'm certainly not saying that Apple is doing a good job, but for most end users, the alternative is strictly worse.
If it can help you, you should know that they test everything over a VPN that doesn’t support UDP. So if your app makes use of UDP you’ll need a fallback method.
UDP is fine. We have apps on the App Store that use UDP. This is likely a NAT related issue. That is not going to be an issue just for App Store review, but also for tons of other networks out there. As of lately, carrier-grade NAT deployments are very common.
It's usually impossible to establish a two-way UDP
"connection" between two peers that are both behind NAT.
This varies depending on the type of NAT. If just one peer is behind NAT you can typically establish the "connection" using NAT hole punching. If both peers are behind NAT you may need to proxy the UDP packets using an intermediary server.
There are protocols for hole punching, such as ICE (https://tools.ietf.org/html/rfc8445), but you can also roll your own - if you control all endpoints.
"Connection" in quotation marks because UDP is a connection-less protocol, but the NAT port mappings that are established are sometimes referred to as a connection.
