First we need to configure the Packaging information for the Release Build Configuration.

Click Packaging and the Packaging navigation will unfold, then click Release

Sample app more empty packaging

Configure the Release packaging information

  • Shared name : The Apps Pajamas More
  • Shared identifier : com.theappspajamas.more
  • Shared version number : 1
  • Shared version text : 1
Sample app more packaging release

Next we will setup the Packaging arrangement for the Debug Build Configuration.

We will Override the apps Name and Identifier. The Identifier is used when generating the info.plist and AndroidManifest.xml for iOS and Droid.

It's common that the Identifier is the same across iOS and Droid apps, however if your project needs different Identifiers simply select the appropriate TheAppsPajajamas.More.Droid or TheAppsPajamas.More.iOS tab and override the Identifier for the required platform.


Using a different Identifier for the Release and Debug Build Configurations is crucial so that both Binaries can be installed on the same phone. Experience has shown that it's important to be able to test both Debug and Release App Binaries on multiple devices before shipping it to a customer, so it's helpful to be able to install both binaries to the same phone, and be able to tell them apart with a different App Name.

For the More Sample App we will leave the Version Number and Version Text the same across the Release and Debug Build Configurations, however as your app progresses through it's release cycle you may need to provide different version number overrides.

Click Packaging and the Packaging navigation will unfold, then click Debug

To update the Shared name field select Overridden from the Parent Project dropdown.

Sample app more packaging parent project

Configure the Debug packaging information

  • Name : The Apps Pajamas More Debug
  • Identifier : com.theappspajamas.more.debug
Sample app more packaging result