Migration

Migrate from 3.3 to 4.0

• Make sure to set the required permissions for your application when using the new AR.context.hardware.flashlight API.
• Starting with Wikitude SDK 4.0 a valid license key is mandatory for starting the SDK. An empty license key will block the SDK. A free trial key can be generated on the license page (free account required).
• The Wikitude SDK 4.0 introduces a new file format for target collections (wtc). In order to unleash the full power of the new Wikitude SDK 4.0 read this section and re-generate your targets.

Migrate from 3.2 to 3.3

The SDK is compatible with Android 4.4, so we recommend to update ADT to the latest version and set the target SDK version to '19' in your Android Manifest XML file.

Migrate from 3.1 to 3.2

ArchitectUrlListener and SensorAccuracyChangeListener are now inner interfaces of the ArchitectView class. Update your imports in your Android code accordingly to get rid of compile time errors (ArchitectUrlListener becomes ArchitectView.ArchitectUrlListener).

Migrate from 3.0 to 3.1

Image Recognition and Tracking

The image recognition engine of Wikitude SDK 3.1 has been updated resulting in shorter time interval to successfully recognize a target image. As a consequence the format of the digital footprint of target image has changed. The format is backward compatible. Developers still can use target collections (.wtc) generated with Wikitude SDK 3.0 (prior to 27th August 2013) together with the SDK 3.1 and vice versa.

However we recommend to generate your target collections again in the Target Manager Tool and update the files when you are using Wikitude SDK 3.1

HTML Drawables

Developers using HTML Drawables in projects prior to Wikitude SDK 3.1 and like to upgrade to 3.1 need to define the viewportHeight similar to the already defined viewportWidth. In addition HTML Drawables do not have to be created as static or dynamic anymore. All are created as dynamic ones.

Migrate from 2.0 to 3.0

Wikitude SDK version 3.0 introduces Wikitude's own image recognition and tracking solution and removes support for the Vuforia Plugin.

If you are not using image recognition features in your app you only need to update the jar file and are good to go.

In case you are making use of image recognition features and want to switch from 2.0 to 3.x version remove any Qualcomm/Vuforia related assets (QCAR.so, QCAR.lib) from your project. Also the READ_PHONE_STATE permission is no longer required in your AndroidManifest.xml.

Find a step-by-step guide about how to convert your existing target collection from Vuforia to Wikitude here.