Application certification issue in Content compliance step

Question

I have submitted our app to the store, however it failed the "Content Compliance" test. I got the following email back:

* Your app doesn't meet requirement 3.2. Learn more

The application works with no issues in our environment, how do we go about figuring out this issue? what does this mean?

Answer 1

Hi Marwan,

Have you already run tests on all platforms your app supports, on other computers, or alternate configurations?  This might help you locate the issue.

Joe-

Answer 2

Thank Joe:

well, I could't test the app on the ARM architetcture, as I don't have a device and there are no ARM emulators.

The application was tested on fresh W8 machines. (using x86 architecture)

---

Marwan

Answer 3

So I am not getting any further with this issue.

I submitted x86 and x64 version of the application to the store (not a neutral version of the application) and still getting rejected on 3.2. I asked for more feedback when I submitted the app, but I don't get anything beyond 3.2.

Any recommendations? I wish there was a bit more info provided with the rejection....

---

Marwan

Answer 4

Hi Marwan,

Have you tried reaching out to your or MS contact?  They may be able to assist you with the issue.  You can also request Metro apps dashboard support.  Please sign with your developer credentials prior to submitting.

Have you checked over the following? http://msdn.microsoft.com/en-us/library/windows/apps/hh921583.aspx

Thanks-

Answer 5

thanks Joe:

I have tried all the above, with not much progress.

Also I have profiled the application, and ran it through all the code paths, and the maximum CP usage is 37% (one spike) rest of the performance is between 0 and 20% of CPU performance....

this is running a 2 year old laptop....an average laptop....

---

Marwan

Answer 6

Attached is the performance profile, I went through all the application.

Hot path is in the ATI dll, which I think is the XAML rendering part.

---

Marwan

Answer 7

Hi Marwan,

It looks like this is going to be a coding issue.  Can you let us know what programing language your writing in?

Answer 8

using C# and XAML. However, running the app on my dev box and a few fresh w8 machines we are not getting any errors with the application.

---

Marwan

Answer 9

I am just surprised how little information (no information)  is provided when an app is rejected. Maybe some comments from the tester that can help me figure it out. 

---

Marwan

Answer 10

Hi Marwan,

Thank you for the feedback about your view on the certification pages. Please keep in mind that as the page here states: [This documentation is preliminary and is subject to change.] We appreciate any and all feedback.

Answer 11

thanks John-P for taking the time to reply and taking my feedback into consideration.

Answer 12

Hi Joe:

Is there any more information we can get how the store certifies/tests the app? Especially for failing point 3.2

I have exhausted all my resources trying to figure out my issue with no luck.

thanks

---

Marwan

Answer 13

I can hear you, Marwan. The feeback after a failed cert is a disaster right now. It starts with little things like the link they post does not even contain a jump anchor and you have to scroll down all the way to the requirement point yourself. Thats basic HTML URL building stuff.

Then, the most annoying thing about the feedback is... there is no feedback. You get back a list of general points and have to guess what exactly the problem was. Without a direct contact to a MS representative there is no way you can find out what exactly went wrong (in the eyes of the testers). And even if you have a contact it takes days... weeks to get the exact reason why "your app did not meet requirement 3.2". I really wonder how the cert UI on the testers side looks like and why the testers are not forced to give a detailed descriptions of the error. We as app developers have to give sub-details about the apps after all.

This non-feedback policy is hopefully just because the whole store is still "Beta" (or "Preview" in new-speak as MS calls it). Lets see how it works out once a GA version is ready.

Answer 14

I have the same problem, and there are still no more details about the problem. No crash log or anything? How should we find the problem?

Answer 15

It is unacceptable for Microsoft to remain vigilant against problems they refuse to describe.

Answer 16

Anyone get any information about all of this, I am facing the exact same problem with the 3.2 failure although all my testing, profiling and tests on other machines passes with flying colors including multiple WACK test. They tell you absolutely nothing, just the app crashed. I haven't been able to get my app to crash even once on multiple machines. I even left if running for 48 hours straight and it still worked perfectly the multiple times I went back to the app in that 48 hour time span.

Based on the info provided by the tester they have a computer problem for all I know.

This is the reason why Windows 8 and Windows 8 phone are never going to gain market share like other platforms. This is exactly the kind of stuff that turns developers off to these platforms and they move on to other stuff.

Since my app is free and they refuse to provide any real details to their supposed failure of my app I will abandon it right here and not waste my time with anymore Windows 8 apps. I am not going to spend days or hours trying to guess at why they say it failed when It never does in any of my test and I can not get any real feed back from the supposed tester.

What a total waste of time. Bye windows 8.

Answer 17

The most common reasons for an app crashing are if an unhandled exception occurs, such as no sound or internet connection and your app does not know what to do in that situation.

You should use the Application.UnhandledException event to account for this.

If you have any questions please contact developer support.

-Eric