none
Basic Hello World app does not pass Windows App Certification Kit

    Question

  • I created a new Blank App (Universal Windows). In the MainPage.XAML I have added a text block with "Hello World". In the Package.appxmanifest I made sure to "generate" all the visual assets.  Also I have linked the app the Microsoft Store app name.

    Compiled a Release x86 making sure I can see the "Hello World".

    From right click Project/Store/Create App Packages and opted the default option (I want to create packages to upload to Microsoft store as ************ by cmoice)

    Went through the selection process Release X86 only (for faster build time). I opted for all the default tests.

    This failed with a lot of errors for fundamentally a blank app, what can I do to fix this?

    Windows App Certification Kit - Test Results

    App name:

    cmoice_test_uwp_win2d

    App publisher:

    cmoice

    App version:

    1.0.1.0

    App Architecture:

    x86

    Kit Version:

    10.0.17763.132

    OS Version:

    Microsoft Windows 10 Pro (10.0.17763.0)

    OS Architecture:

    x64

    Report time:

    3/28/2019 4:56:47 PM

     

    Overall result: FAILED

     

     

    Deployment and launch tests

     

    FAILED

    Bytecode generation

    • Error Found: The bytecode generation test detected the following errors:
      • System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Windows.SoftwareLogo.Tests.Utility.IsPackageWWA(AppXPackage package) at Microsoft.Windows.SoftwareLogo.Tests.BytecodeGenerationCheck.BytecodeGenerationCheck.ExecuteSharedValidation(String manifestFilePath, String packageFullName) at Microsoft.Windows.SoftwareLogo.TestBase.TestBase.ExecuteTest()
    • Impact if not fixed: As a performance optimization to accelerate JavaScript execution time, JavaScript files ending in the ".js" extension generate bytecode when the app is deployed. This optimization significantly improves start-up and ongoing execution times for JavaScript.
    • How to fix: You may need consider one or more of these steps to fix the issue: - Avoid deploying the app by pressing F5 in Visual Studio, create an app package instead - Ensure that event logging is enabled - All JavaScript files are syntactically valid; otherwise exclude the respective files from the package - Please note that you should uninstall all previous versions of the app before deploying Otherwise exclude the respective files from the package.

    FAILED

    Background tasks cancelation handler

    • Error Found: The background tasks cancelation handler validation detected the following errors:
      • System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Windows.SoftwareLogo.Tests.CancelationHandlerValidation.CancelationHandlerValidation.ExecuteSharedValidation(String manifestFilePath, String packageFullName) at Microsoft.Windows.SoftwareLogo.TestBase.TestBase.ExecuteTest()
    • Impact if not fixed: An app that fails to handle cancelation request to background tasks, which will result in being force terminated.
    • How to fix: Background tasks need to implement cancelation event handler.

    FAILED

    Platform version launch

    • Error Found: The high OS version validation detected the following errors:
      • System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Windows.SoftwareLogo.Tests.Utility.LaunchAppTest(String packageFullName, String manifestFilePath, String testName) at Microsoft.Windows.SoftwareLogo.Tests.HighOSVersionLaunchCheck.HighOSVersionLaunchCheck.Test(UapApp uapApp) at Microsoft.Windows.SoftwareLogo.TestBase.TestBase.ExecuteTest()
    • Impact if not fixed: The app should not use version information to provide functionality that is specific to the OS.
    • How to fix: Please use recommended methods to check for available functionality in the OS. See the link below for more information. Operating System Version

    FAILED

    App launch

    • Error Found: The app launch test detected the following errors:
      • System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Windows.SoftwareLogo.Tests.Utility.LaunchAppTest(String packageFullName, String manifestFilePath, String testName) at Microsoft.Windows.SoftwareLogo.Tests.LaunchAppCheck.LaunchAppCheck.Test(UapApp uapApp) at Microsoft.Windows.SoftwareLogo.TestBase.TestBase.ExecuteTest()
    • Impact if not fixed: An app that fails to launch presents a poor user experience, and will not be accepted by the Microsoft Store.
    • How to fix: Investigate and debug the app to identify and fix the problem. Troubleshooting App launch

    FAILED

    Crashes and hangs

    • Error Found: The crashes and hangs test detected the following errors:
      • System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Windows.SoftwareLogo.Tests.WindowsErrorReporting.WindowsErrorReporting.ExecutePostTest(TaskData taskData) at Microsoft.Windows.SoftwareLogo.Tests.WindowsErrorReporting.WindowsErrorReporting.ExecuteTest()
    • Impact if not fixed: An app that stops responding or crashes can cause data loss and is a poor user experience.
    • How to fix: Investigate and debug the app to identify and fix the problem. Debugging Store apps

     

     

    Package compliance test

     

    FAILED

    Application count

    • Error Found: The app count test detected the following errors:
      • System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Windows.SoftwareLogo.Tests.ApplicationCount.ApplicationCount.ExecuteSharedTests(EnumApplicationType appType, String manifestFilePath) at Microsoft.Windows.SoftwareLogo.TestBase.TestBase.ExecuteTest()
    • Impact if not fixed: The Microsoft Store does not allow a package containing more than one app defined in the manifest.
    • How to fix: The App Manifest must define only one app per package. See link below for more information: Certification requirements

    FAILED

    App manifest

    • Error Found: The app manifest test detected the following errors:
      • Package 59672cmoice.cmoicetestuwpwin2d_1.0.1.0_x86__rmtskzcmyxk82 could not be found
    • Impact if not fixed: Apps that violate the Microsoft Store certification requirements can’t be submitted to the Microsoft Store.
    • How to fix: App manifest must include valid entries for all required fields, please modify the manifest entries listed above. See link below for more information: Certification requirements

    PASSED

    Package size

    PASSED

    Resource Packages

    FAILED

    Restricted namespace

    • Error Found: The restricted namespace test detected the following errors:
    • Impact if not fixed: The Microsoft Store does not allow an app manifest to reference restricted namespaces.
    • How to fix: Remove the restricted namespaces from your app manifest.

     

     

    Windows security features test

     

    FAILED

    Binary analyzer

    • Error Found: The binary analyzer test detected the following errors:
    • Impact if not fixed: If the app doesn’t use the available Windows protections, it can increase the vulnerability of the customer's computer to malware.
    • How to fix: Apply the required linker options - SAFESEH, DYNAMICBASE, NXCOMPAT, and APPCONTAINER - when you link the app. See links below for more information: Fixing Binary Analyzer Errors

    PASSED

    Banned file analyzer

    PASSED

    Private code signing

     

     

    Supported API test

     

    FAILED

    Supported APIs

    • Error Found: The supported APIs test detected the following errors:
      • The version specified by OSMinVersion attribute is not valid.
      • An error occurred in the SupportedApis test.
    • Impact if not fixed: Using an API that is not part of the Windows SDK for Microsoft Store apps violates the Microsoft Store certification requirements.
    • How to fix: Review the error messages to identify the API that is not part of the Windows SDK for Microsoft Store apps. Please note, apps that are built in a debug configuration or without .NET Native enabled (where applicable) can fail this test as these environments may pull in unsupported APIs. Retest your app in a release configuration, and with .NET Native enabled if applicable. See the link below for more information: Alternatives to Windows APIs in Microsoft Store apps.

     

     

    App manifest resources tests

     

    FAILED

    App resources

    • Error Found: The app resources validation test detected the following errors:
      • The "C:\Program Files\windowsapps\59672xxxx.cmoicetestuwpwin2d_1.0.1.0_x86__rmtskzcmyxk82\AppXManifest.xml" file is missing or invalid.
      • Manifest Resource Validation Test encountered error: hr = 0x80070003.
    • Impact if not fixed: The app might not install if the strings or images declared in your app’s manifest are incorrect. If the app does install with these errors, your app’s logo or other images used by your app might not display correctly.
    • How to fix: Fix the problem indicated by the error message. See the link below for more information: App Package Resource Validation

    FAILED

    Branding

    • Error Found: The branding validation test encountered the following errors:
      • System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Program Files\windowsapps\59672xxxx.cmoicetestuwpwin2d_1.0.1.0_x86__rmtskzcmyxk82\AppXManifest.xml'. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize) at System.Xml.XmlDownloadManager.GetStream(Uri uri, ICredentials credentials, IWebProxy proxy, RequestCachePolicy cachePolicy) at System.Xml.XmlUrlResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn) at System.Xml.XmlTextReaderImpl.FinishInitUriString() at System.Xml.XmlReaderSettings.CreateReader(String inputUri, XmlParserContext inputContext) at System.Xml.Linq.XDocument.Load(String uri, LoadOptions options) at Microsoft.Windows.SoftwareLogo.Shared.AppxProgramInventoryHelper.GetAllImagesFromManifestFile(String appxManifestFile, String packageFullName) at Microsoft.Windows.SoftwareLogo.Tests.BrandingValidation.BrandingValidation.ExecuteSharedTests(String packageFullName, String manifestFilePath) at Microsoft.Windows.SoftwareLogo.TestBase.TestBase.ExecuteTest()
    • Impact if not fixed: Microsoft Store apps are expected to be complete and fully functional. Apps using the default images e.g. from templates or SDK samples present a poor user experience and cannot be easily identified in the store catalog.
    • How to fix: Replace default images with something more distinct and representative of your app.

     

     

    Debug configuration test

     

    PASSED

    Debug configuration

     

     

    File encoding test

     

    FAILED

    UTF-8 file encoding

    • Error Found: The UTF-8 file encoding test detected the following errors:
      • System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Windows.SoftwareLogo.Tests.Utility.IsPackageWWA(AppXPackage package) at Microsoft.Windows.SoftwareLogo.Tests.FileEncodingCheck.FileEncodingCheck.ExecuteSharedTests(String packageFullName, String manifestFilePath) at Microsoft.Windows.SoftwareLogo.TestBase.TestBase.ExecuteTest()
    • Impact if not fixed: HTML, CSS, and JavaScript files must be encoded in UTF-8 form with a corresponding byte-order mark (BOM) in order to benefit from bytecode caching and to avoid other runtime error conditions.
    • How to fix: Open the affected file, and select "Save As..." option from the File menu in Visual Studio. Select the drop-down control next to the Save button and select "Save with Encoding..." option. From the Advanced save options dialog, choose the "Unicode (UTF-8 with signature)" option and click the OK button.

     

     

    App Capabilities test

     

    PASSED

    Special use capabilities

     

     

    Windows Runtime metadata validation

     

    FAILED

    ExclusiveTo attribute

    • Error Found: The ExclusiveTo attribute test detected the following errors:
    • Impact if not fixed: Microsoft store doesn't allow apps that don't pass Windows Runtime Metadata Validation.
    • How to fix: Please ensure that Windows Runtime classes don't implement interfaces that are marked as ExclusiveTo another class.

    FAILED

    Type location

    • Error Found: The type location test detected the following errors:
    • Impact if not fixed: Microsoft store doesn't allow apps that don't pass Windows Runtime Metadata Validation.
    • How to fix: Please ensure that the metadata for all Windows Runtime types is located in the winmd file that has the longest namespace-matching name in the app package.

    FAILED

    Type name case-sensitivity

    • Error Found: The type name case-sensitivity test detected the following errors:
    • Impact if not fixed: Microsoft store doesn't allow apps that don't pass Windows Runtime Metadata Validation.
    • How to fix: Please ensure that all Windows Runtime types have unique, case-insensitive names within your app package. Please ensure that no Windows Runtime type name is also used as a namespace name within your app package.

    FAILED

    Type name correctness

    • Error Found: The type name correctness test detected the following errors:
    • Impact if not fixed: Microsoft store doesn't allow apps that don't pass Windows Runtime Metadata Validation.
    • How to fix: Please ensure there are no Windows Runtime types in the global namespace or in the Windows top-level namespace.

    FAILED

    General metadata correctness

    • Error Found: The general metadata correctness test detected the following errors:
    • Impact if not fixed: Microsoft store doesn't allow apps that don't pass Windows Runtime Metadata Validation.
    • How to fix: Please ensure that the compiler you are using to generate your Windows Runtime types is up to date with with the Windows Runtime specifications.

    FAILED

    Properties

    • Error Found: The property test detected the following errors:
    • Impact if not fixed: Microsoft store doesn't allow apps that don't pass Windows Runtime Metadata Validation.
    • How to fix: Please ensure that all properties on a Windows Runtime class have a get method (set methods are optional). Please ensure that the type of the get method return value matches the type of the set method input parameter, for all properties on Windows Runtime types.

     

     

    Package sanity test

     

    FAILED

    Platform appropriate files

    • Error Found: The platform appropriate files test detected the following errors:
      • System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Program Files\windowsapps\59672xxxx.cmoicetestuwpwin2d_1.0.1.0_x86__rmtskzcmyxk82\AppXManifest.xml'. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize) at System.Xml.XmlDownloadManager.GetStream(Uri uri, ICredentials credentials, IWebProxy proxy, RequestCachePolicy cachePolicy) at System.Xml.XmlUrlResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn) at System.Xml.XmlTextReaderImpl.FinishInitUriString() at System.Xml.XmlReaderSettings.CreateReader(String inputUri, XmlParserContext inputContext) at System.Xml.Linq.XDocument.Load(String uri, LoadOptions options) at Microsoft.Windows.SoftwareLogo.Tests.PlatformAppropriateFiles.PlatformAppropriateFiles.ExecuteSharedTests(String manifestFilePath) at Microsoft.Windows.SoftwareLogo.TestBase.TestBase.ExecuteTest()
    • Impact if not fixed: Including files in the app package that are incompatible with the target processor architecture may cause your app to fail at runtime.
    • How to fix: Ensure that binary file architecture is compatible with the ProcessorArchitecture attribute specified within the app package manifest. Platform Appropriate Files

    FAILED

    Supported directory structure check

    • Error Found: The supported directory structure test encountered the following errors:
      • System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Program Files\windowsapps\59672xxxx.cmoicetestuwpwin2d_1.0.1.0_x86__rmtskzcmyxk82'. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileSystemEnumerableIterator`1.CommonInit() at System.IO.FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler, Boolean checkHost) at System.IO.Directory.GetFiles(String path, String searchPattern, SearchOption searchOption) at Microsoft.Windows.SoftwareLogo.Tests.SupportedDirectoryStructure.SupportedDirectoryStructure.AnalyzeAllFiles(String filePath) at Microsoft.Windows.SoftwareLogo.Tests.SupportedDirectoryStructure.SupportedDirectoryStructure.ExecuteSharedTests(String manifestFilePath) at Microsoft.Windows.SoftwareLogo.TestBase.TestBase.ExecuteTest()
    • Impact if not fixed: Exceeding the supported MAX_PATH will cause the app to fail at runtime.
    • How to fix: Use a shorter directory structure or a shorter file name.

     

     

    Resource Usage Test

     

    FAILED

    WinJS background task

    • Error Found: The WinJS background tasks test encountered the following errors:
      • System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Windows.SoftwareLogo.Tests.Utility.IsPackageWWA(AppXPackage package) at Microsoft.Windows.SoftwareLogo.Tests.CloseBackgroundTasksCheck.CloseBackgroundTasksCheck.ExecuteSharedTests(String packageFullName, String manifestFilePath) at Microsoft.Windows.SoftwareLogo.TestBase.TestBase.ExecuteTest()
    • Impact if not fixed: Apps with background tasks that do not call close() can result in draining the battery.
    • How to fix: Update the background task to call close(). WinJS Background Tasks

     


    • Edited by cmoice Friday, March 29, 2019 2:27 AM
    Friday, March 29, 2019 12:13 AM

All replies

  • Hi cmoice,

    The local Windows Application Certification Kit test is optional for the app submission, there is an online WACK test for each app to be published to the Microsoft Store.I used the same version of OS and WACK, however I can't reproduce your error. Could you re-install your Windows Application Certification Kit to try again or test the same package with other device to figure out whether it is the package issue or the WACK tool issue?

    Best regards

    Daisy  Tian


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, March 29, 2019 3:24 AM
    Moderator
  • Hi Daisy,

    I have reinstalled the local Window Software Development Kit - the version you linked to required that uninstall and install Window Software Development Kit version 10.0.16299.15.  I don't have access to another machine at this time to try a different system. After reinstallation I ran the local tests, I get the same results. 

    Is it possible to submit online my test app for validation without having to publish it to the store?

    According to https://docs.microsoft.com/en-us/windows/uwp/publish/app-submissions online submittal would occur  after I have completed the app. However, it would not be wise to spend a month building the app just to find out that what I'm trying to do is not possible or allowed after I put all the work in it.

    Thank you for your help!

    Cornel

    Friday, March 29, 2019 12:27 PM
  • Hi Daisy,

    I have figured out how to go about the online process for app submittal and certification.  At this point I'm giving up on the local WACK test, there are too many false negatives to be of any practical use.

    Thanks again for your help!

    Cornel

    Friday, March 29, 2019 10:54 PM
  • Hi Cornel,

    How's your app submission going? Did it pass the online Windows Application certification kit test? If you still encounter the errors for the online WACK test, please post here with the details(Do not include the personal information) for us to analyze.

    Best regards

    Daisy  Tian


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, April 1, 2019 5:53 AM
    Moderator
  • Hi Daisy,

    The online Windows Application certification kit works fine. The only issues I have experienced are with the certification test kit when running it locally on my machine (as I have outlined at the beginning of this thread). But for now I have a good baseline to ensure certification works when starting with a blank project. I'll resubmit my app for online certification as I incrementally add features to it. 

    Thank you for your help!

    Cornel


    Monday, April 1, 2019 7:37 PM