Friday, September 21, 2012 10:21 PM
Has there been any progress toward a work around on the 30 day "proofs" freeze problem? For people with only one proof on their app-store account where that proof is defunct or erroneous it is a show stopping situation. Those who ran into it more than 30 days ago are already outside of the freeze, but for those going into it right now it is happening at an inopportune time.
There are several defunct threads in which various Microsoft people said they were looking into the problem, but the problem persists with no meaningful work around offered. All suggested solutions involve going to the proofs management page and changing or adding proofs, but any such changes just kick of the 30 day timer that is the core of the problem.
It seems the only solution for beating the 30 day clock would be paying for a second developer account and using that instead of the original account.
The best solution, the obvious solution, would be for Microsoft to authorize someone within the corporation to unlock these accounts if common sense proofs that a human can understand can establish ownership of the account. This is what happens in every IT department in the world for similar situations. Has anyone at Microsoft considered opening a desk for this purpose?
To minimize the traffic to this helpdesk, Microsoft could add a warning about relying on only one proof, and verify any proof before accepting it in the first place.