Windows App Certification Kit - Test Results
App name:
QuickForecast
App publisher:
Digia Plc
App version:
1.0.16.0
OS Version:
Microsoft Windows 10 Pro (10.0.10586.0)
Kit Version:
10.0
Architecture:
x64
Report time:
1/5/2016 1:09:49 PM

Overall result: FAILED


Deployment and launch tests

PASSED
Bytecode generation

PASSED
Background tasks cancelation handler

PASSED
Platform version launch

PASSED
App launch

FAILED
App prelaunch
  • Error Found: The app prelaunch validation detected the following errors:
    • The app failed prelaunch test - 2237e973-ecf9-4194-a52a-f2b08bdad452_1.0.16.0_x86__ay9qrcg7qw9bw.
  • Impact if not fixed: The app will take a longer time to launch, even when prelaunch is enabled.
  • How to fix: In the OnLaunched method implementation of the app, ensure you handle the LaunchActivatedEventArgs.PreLaunch option to be prelaunch event aware.

PASSED
Crashes and hangs



Package compliance test

PASSED
Application count

PASSED
App manifest

PASSED
Bundle manifest

PASSED
Package size

PASSED
Restricted namespace



Windows security features test

PASSED
Binary analyzer

PASSED
Banned file analyzer

PASSED
Private code signing



Supported API test

FAILED
Supported APIs
  • Error Found: The supported APIs test detected the following errors:
    • API TlsAlloc in api-ms-win-core-processthreads-l1-1-2.dll is not supported for this application type. Qt5Core.dll calls this API.
    • API TlsFree in api-ms-win-core-processthreads-l1-1-2.dll is not supported for this application type. Qt5Core.dll calls this API.
    • API TlsGetValue in api-ms-win-core-processthreads-l1-1-2.dll is not supported for this application type. Qt5Core.dll calls this API.
    • API TlsSetValue in api-ms-win-core-processthreads-l1-1-2.dll is not supported for this application type. Qt5Core.dll calls this API.
  • Impact if not fixed: Using an API that is not part of the Windows SDK for Windows Store apps violates the Windows Store certification requirements.
  • How to fix: Review the error messages to identify the API that is not part of the Windows SDK for Windows Store apps. Please note, C++ apps that are built in a debug configuration will fail this test even if it only uses APIs from the Windows SDK for Windows Store apps. See the link below for more information:
    Alternatives to Windows APIs in Windows Store apps.



App manifest resources tests

PASSED
App resources

PASSED
Branding



Debug configuration test

PASSED
Debug configuration



File encoding test

PASSED
UTF-8 file encoding



Direct3D Feature Test

PASSED
Direct3D feature level support

FAILED
Direct3D trim after suspend
  • Error Found: The Direct3D Trim after Suspend test detected the following errors:
    • Application App was not running at the end of the test. It likely crashed or was terminated for having become unresponsive.
  • Impact if not fixed: If the app does not call Trim on its Direct3D device, the app will not release memory allocated for its earlier 3D work. This increases the risk of apps being terminated due to system memory pressure.
  • How to fix: The app should call the Trim API on its IDXGIDevice3 interface anytime it is about to be suspended.
    More Information



App Capabilities test

PASSED
Special use capabilities



Windows Runtime metadata validation

PASSED
ExclusiveTo attribute

PASSED
Type location

PASSED
Type name case-sensitivity

PASSED
Type name correctness

PASSED
General metadata correctness

PASSED
Properties



Package sanity test

PASSED
Platform appropriate files

PASSED
Supported directory structure check



Resource Usage Test

PASSED
WinJS background task