WARNING:

- Ensure you know the TPControl Token (License) value for the device.

- Ensure all Settings and UI file(s) relevant for commissioning a new device are available.

Contact your AMX integrator for more details.


Overview

TPControl token values are paired with a 'TPC Device ID' at the time of registration. TPC Device IDs are used to assist in the identification of devices and matching registration information for tokens. If for any reason identifiers used to assist identification change (which is beyond app-Developer control), this can result in the licensing invalidating.


iOS Platform

Apple no longer permit iOS developers to access UDID information, which as developers Touch Panel Control used to positively pair with TPControl tokens, at time of token registration for pre-iOS7 devices.

We now pair tokens with a unique TPC Device ID based on software identifiers that Apple permit us to use. However, as the identifiers are software based, they are prone to change under certain conditions, not limited to the following:

Causes

· Uninstalling and reinstalling TPControl

· Installing TPControl from the AppStore using a different customer Apple ID than when TPControl was originally installed on the device

· Resetting the device to factory default, and not restoring from a backup of the device which included TPControl

· Upgrading from iOS6 or earlier to iOS7 or later prior to running at least TPControl v2.4.2.0 for iOS on the device.
 More details here: http://www.touchpanelcontrol.com/ios7-update


Android Platform

In terms of TPC Device ID retention, Android devices are the “better of the bunch” in comparison to the other platforms. However, Android devices are not immune to changes and so the TPC Device ID may also change under certain conditions, not limited to the following:

Causes:

· Installing a “Custom ROM” on the device.


Windows Platform

Similar to Apple with iOS, Microsoft provide software based identifiers. So, the TPC Device ID may change under certain conditions, not limited to the following:

Causes:

· Installing across multiple user profiles

· Upgrading the operating system which may result in a reinstallation of the application from the Store


Solution

Ensure that a reference to the original Token value is always available. Refer to the WARNING above for more details.

In some cases, even though the Invalid License warning appears, a token value may actually be available on the device. Check by reviewing:

· iOS: ‘Settings -> TPControl -> Version: Token'

· Android: ‘TPControl -> MENU/Settings -> Version: Token'

· Windows: ‘TPControl -> (charm or Windows-key + C) -> Settings -> Advanced -> Version: Token'


Armed with the Token value, to re-register the device first try the on-device 'Token Registration' option, which is available within Settings for TPControl. Only if prompted by that process will the token need to be ‘Deauthorized’ at which point you can use either the 'Token Registration' or 'TPCloud PIN' methods to register the device.


For more details, see My device was lost|stolen|replaced|upgraded. How do I migrate the Token / License to a new device?