In some instances Metadata is added to items to provide additional features, however, this Metadata may not be transferred when the App is delivered as a standard Fileset. Where this occurs, the Metadata may be re-injected using a script. An example of this is highlighted in our KB on Deploying Folders with Icons.
Teamviewer is another example of this. The Quick Support version of the App has the option to include customisation, as per their guidelines. In fact, the Tool: FileWave QS App implements this to provide branding, user name and a personalised design.
When customisation is configured on this App, the App receives additional Metadata. If the Metadata were not restored, the customisation would be lost and the App would appear as the basic, standard looking App.
To ensure the Metadata is re-applied after installation as a standard Fileset, the following should be followed:
Use a command line tool to read the Metadata prior to making the Fileset
Create an Activation or Postflight Script, to re-insert the Metadata, as part of the Fileset
To read the Metadata, open Terminal and run the following command, editing the path to match the required location. Using FileWave QS App as an example: