I can relate a bit about this article and the Windows Store submission process - I have been using it since the end of July. The requirements mentioned in the post (1.2, 3.2, 3.8, etc.) are part of a big document that tries to clearly outline what an app should and shouldn't do. They are defined rather well, but sometimes will leave you wandering what the hell is going on.
I submitted an HTML app that was accepted, then after some minor changes failed validation the second time I submitted it. The problem was "Requirement 3.2: The app crashes", however, nothing I changed could cause a crash. I resubmitted the app with a bumped version and no other changes and it passed validation the second time.
This led me to believe that MS are either still fixing bugs in the certification process or that my app ended up on a faulty test device that crashed. Still, I would LOVE IT if MS provided actual stack trace or other useful information if a crash occurs.
The biggest problem with the Store right now is the time it takes to pass a new release. In the last couple of days the Microsoft built-in applications (video, finance, sports) have been updated multiple times, but my last submission took 5 days to pass the Content Compliance step. If Microsoft wants more apps in the Store, they need to scale up their review/certification infrastructure and team.
BTW they give you reports, but only if the crash was in an already approved app that is in the Store[1]. My point was that such information should be available during the certification process as well.
Also note that one of the common reasons for failing Requirement 3.2 now includes a reference to using CurrentAppSimulator that wasn't in the one linked in the original article.
I guess the OP just got stung by being an early adopter and the FAQ/requirement pages not being anywhere near complete as not enough people had gone through the certification process for MSFT to find all of the common reasons for rejection.
I submitted an HTML app that was accepted, then after some minor changes failed validation the second time I submitted it. The problem was "Requirement 3.2: The app crashes", however, nothing I changed could cause a crash. I resubmitted the app with a bumped version and no other changes and it passed validation the second time.
This led me to believe that MS are either still fixing bugs in the certification process or that my app ended up on a faulty test device that crashed. Still, I would LOVE IT if MS provided actual stack trace or other useful information if a crash occurs.
The biggest problem with the Store right now is the time it takes to pass a new release. In the last couple of days the Microsoft built-in applications (video, finance, sports) have been updated multiple times, but my last submission took 5 days to pass the Content Compliance step. If Microsoft wants more apps in the Store, they need to scale up their review/certification infrastructure and team.