Testing with a License Override

To test your game with a license override you will first need to submit and prop the initial version of your game to the Marketplace in your sandbox. After that you can to download your game, retrieve the necessary values to configure a locally deployed loose-file build and successfully call marketplace APIs.

Get values from the package

Get the ProductID, ContentID, EKBID and package name values from the package on the Marketplace. This should only have to be done once as these values should remain constant.

  1. From an Xbox One XDK Command Prompt issue the xbApp list command as follows:
    xbapp list /d /nosystem
    
  2. Record the ContentID, ProductID, and EKBID shown for your game’s package.

  3. Uninstall the package from the console with the XDK command prompt
    xbapp uninstall [Package Name]  
    

Temporarily add a license override file to the loose-file build of your game.

  1. Create a new file called debug_licensing_overrides.xml which includes the package’s ProductID, ContentID, and EKBIDs values formatted as follows:
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- This file is used to enable the Windows Service Store API. -->
    <LicenseOverrides>
        <ContentId>{7cd28a16-7375-4421-b02c-45150349453b}</ContentId>
        <ProductId>{d232bafa-1247-4f65-beb9-abc92f268612}</ProductId>
        <EKBID>{B2FCD6BA-21CE-4EB5-A2D6-C3124CCF5C49}</EKBID>
    </LicenseOverrides>
    
  2. Save the debug_licensing_overrides.xml file in the root of your game’s folder structure (i.e., the same place where your appmanifest.xml is located).

  3. Build, deploy, and debug the loose-file version of your game as you would normally. Calls to the Windows Store API will utilize the values from your debug_licensing_overrides.xml file and should authenticate and function normally.

The presence of a debug_licensing_overrides.xml file will only affect the behavior of a loose-file game registered on an XDK developer kit. That said, because the file contains sensitive identifiers specific to your title you should not include the debug_licensing_overrides.xml file in packaged builds of your game. In fact, the submission validator feature in MakePkg.exe will flag the presence of this file in a package, and its presence will result in failure of a package to pass retail certification.

If the contents of the debug_licensing_overrides.xml file are changed, or the file is removed, after the game is registered then the previously applied license override values will remain in effect until the next time the game is registered. Upon re-registration, new values from the file will be applied. Once a license override is applied for your game, the override will remain in effect across reboots of the console. To remove the licensing override, simply remove the debug_licensing_overrides.xml file and re-register the game. Doing so will remove the licensing override and cause default licensing behavior to be applied to your game.