To use Sencha Desktop Packager, you must obtain a license. There are two types of licenses:
Both forms of the license require a valid Sencha Forum account. If you do not already have an account, you can register at the link below:
An evaluation license entitles you to use Sencha Desktop Packager for 30 days to see if it meets your needs. Applications packaged with an evaluation license are fully functional, but will only work for 14 days from when they are packaged, and will have the text, [built using a trial of Sencha Desktop Packager, expiring on MM/DD/YYYY] added to the window title indicating that they were created with an evaluation license.
At any time during the evaluation period, you can upgrade to full license by following the instructions in the section Full License below.
Once you have a Sencha Forum account, you can obtain an Evaluation License for Sencha Desktop Packager by running ionpackage from the command line.
The first time you run ionpackage it will not find a license, and so it will print a message and prompt for user name and password:
Welcome to the Sencha Desktop Packager! Since you are running the Desktop Packager for the first time, we need to retrieve your license information. You will need to supply your Sencha credentials. If you do not have a Sencha account yet, please register at http://www.sencha.com/forum/register.php. Username: johndoe Password: If you have received the activation code, please type the code and press Enter. Otherwise, press Enter to begin your 30 day evaluation. Activation Code:
As the instructions say, just hit enter when it prompts for an activation code and you will receive an evaluation license.
You will not have to resubmit your credentials every time you use Sencha Desktop Packager with an Evaluation License, but you will see a reminder message each time you run it:
NOTE: You are currently evaluating Sencha Desktop Packager 1.1. Your evaluation period will end in 26 days. Applications packaged using this evaluation edition will function for 14 days from the date it was packaged. Visit http://www.sencha.com/contact for more information.
If you continue using ionpackage after the evaluation period is ended, you will see a message similar to the one below, and will no longer be able to use ionpackage to package applications.
NOTE: You are currently evaluating Sencha Desktop Packager 1.1. Your evaluation has expired. This evaluation expired 11 days ago. Visit http://www.sencha.com/contact for more information.
NOTE: The license file is stored in the following location:
- Microsoft Windows:
- Mac OS X:
~/Library/Application Support/Sencha/Desktop Packager/
Once you have received your activation key, you can run ionpackage with the argument --activate, and you will be prompted for your user name, password and the activation key.
> ionpackage --activate
You can also enter your activation code directly on the command line as shown below:
> ionpackage --activate=ACTIVATION-KEY-FROM-EMAIL
where ACTIVATION-KEY-FROM-EMAIL should be replaced with the activation key from the email you recieved.
You only have to enter the activation credentials one time.
Using Sencha Desktop Packager With Unattended Build Systems
A Sencha Desktop Packager license is tied to a Forum user account, but the generated license file can only be used on the machine where it was created. In other words, once you activate a full license with your Sencha Forum credentials, you can use that license on any machine, but you need to regenerate the license file for each machine.
This means that if you have a build environment where builds are run on multiple machines (real or virtual) each machine needs to have its own license file generated.
In some systems, the entire build environment is generated each time a build is run. For these environments, we provide the --username and --password command line parameters:
> ionpackage --firstname.lastname@example.org --password=secret --activate=12345 ...
When used with these options, ionpackage will generate a new license file. Note that a network connection will be required to validate the credentials.