locked
WACK thows following errors that where new. Need advice RRS feed

  • Question

  • Hi,

    During earlier uploading of app to store, I never encountered these errors. App used to pass successfully and even published. But after minor changes when I run WACK , it reported following errors,  A bit confused as why suddenly this happened ?

    Blocked executables
    Error Found: The blocked executables test has detected the following errors:
    File Microsoft.HockeyApp.Kit.dll contains a reference to a "Launch Process" related API System.Diagnostics.Process.Start
    File Converter.exe contains a blocked executable reference to "CSI".
    File converter.exe contains a blocked executable reference to "reG".
    File Microsoft.AI.WindowsServer.dll contains a blocked executable reference to "MSBuild".
    File converter.resources.dll contains a blocked executable reference to "NTSD".
    Impact if not fixed: Launching executable files is restricted on Windows 10 S systems. Apps that rely on this capability might not run correctly on Windows 10 S systems.
    How to fix: Identify which of the flagged entries represent a call to launch an executable file that is not part of your app and remove those calls. If the flagged files are part of your application, you may ignore the warning. 

    HockeyApp and AI.WindowsServer are MSFT libraries , How do I resolved ?

    What is CSI, reG, NTSD ?

    Any guidance/advice  ?

    Regards

    Thursday, May 31, 2018 2:19 PM

All replies

  • Hi,

    I am getting following errors while WACK validates the .appx file.  The list of errors are too long, I am copy-pasting few lines. There errors where not existing earlier when we had published pervious versions of our app to store.  We have done cosmetics changes in the app, but this time we got long list of errors.   What has changed in between two version was many VS2017 and windows updates.

    Current version:  WPF |  VS2017 15.7.2 | .NET Framework 4.7.03056.
    Target Framework : 4.6.2
    DesktopBridge Convert : Manual Approach. 

    Type name correctness
    Error Found: The type name correctness test detected the following errors:

    he Windows.ApplicationModel.StartupTaskState type in the Windows.winmd file is in the Windows namespace.
    The Windows.ApplicationModel.PackageSignatureKind type in the Windows.winmd file is in the Windows namespace.
    The Windows.ApplicationModel.PackageVersion type in the Windows.winmd file is in the Windows namespace.
    The Windows.ApplicationModel.IFullTrustProcessLauncherStatics type in the Windows.winmd file is in the Windows namespace.
    The Windows.ApplicationModel.IStartupTask type in the Windows.winmd file is in the Windows namespace.
    The Windows.ApplicationModel.IStartupTaskStatics type in the Windows.winmd file is in the Windows namespace.

    General metadata correctness
    Error Found: The general metadata correctness test detected the following errors:

    The type Windows.Foundation.IAsyncInfo in file Windows.winmd has the same GUID as the following types: Windows.Foundation.IAsyncInfo. All GUIDs must be unique.
    The type Windows.Devices.SmartCards.ISmartCardCryptogramStorageKeyInfo2 in file Windows.winmd has the same GUID as the following types: Windows.Devices.SmartCards.ISmartCardCryptogramStorageKeyInfo2. All GUIDs must be unique.
    The type Windows.Graphics.Printing3D.IPrinting3DColorMaterialGroup in file Windows.winmd has the same GUID as the following types: Windows.Graphics.Printing3D.IPrinting3DColorMaterialGroup. All GUIDs must be unique.
    The type Windows.Media.IMusicDisplayProperties2 in file Windows.winmd has the same GUID as the following types: Windows.Media.IMusicDisplayProperties2. All GUIDs must be unique.
    The type Windows.Media.Ocr.IOcrLine in file Windows.winmd has the same GUID as the following types: Windows.Media.Ocr.IOcrLine. All GUIDs must be unique.
    The type Windows.ApplicationModel.Core.ICoreApplicationViewTitleBar in file Windows.winmd has the same GUID as the following types: Windows.ApplicationModel.Core.ICoreApplicationViewTitleBar. All GUIDs must be unique.

    Any help Please ?

    Regards

    Thursday, May 31, 2018 3:19 PM
  • Hi Richard,

    WACK tool will run several test for the desktop bridge apps. Some are optional and others are required. Please check the different tests here: https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/windows-desktop-bridge-app-tests

    You could find your errors and the Corrective actions as well from that link.

    Best regards,

    Roy



    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, June 1, 2018 7:52 AM