Cobranding functionality fails when an SPK is created via the command-line interface in Spotfire
Article ID: KB0137966
Updated On:
| Products | Versions |
|---|---|
| Spotfire Developer | All |
Description
When a cobranding SPK is created using the command line instead of the package builder UI, particularly for Linux deployments (or universal package), the resulting package may not properly enable co-branding.
Even if the package is successfully created and deployed, the co-branding changes will not be visible.
The Server.log file may display an error similar to this:
INFO 2025-09-01T20:19:00,722+0530 [save-deployment-area-79077935-ac9c-4cc9-8f8e-4c8d094e6979] server.cobranding.CobrandingManager: cobranding not enabled, missing cobranding.config
This error indicates that the cobranding.config file, although present, is not being correctly recognized due to a missing "publicresource". This often occurs because a critical ResourceIdentifier tag is absent from the pkdesc file.
Environment
All
Resolution
To resolve this issue, we need to modify the pkdesc file to include the ResourceIdentifier tag for the cobranding.config file.
Here's an example of how the modified section in your pkdesc file should appear:
<File SourceFile="<some path>/cobranding.config" TargetFilename="cobranding.config" Type="File">
<ResourceIdentifier Name="cobranding.config" />
</File>After making this modification to the pkdesc file, rebuild the co-branding SPK and redeploy it to your server. The co-branding functionality should then be enabled, and the applied changes should be visible.
Issue/Introduction
This article addresses an issue where cobranding functionality does not work after creating a successful cobranding SPK via the command line.
Additional Information
Doc: Package Description File
Doc: Creating and deploying a cobranding package
