Skip to main content
Version: ACAP version 4

Extend compatibility to future AXIS OS major versions

This guide describes how to make an application built with Native SDK 1.15.1 compatible with AXIS OS 12. Upgrading a device from AXIS OS 11.11 to 12.x introduces breaking changes that may break your application or even trigger a rollback upon application installation during AXIS OS upgrade. Follow the steps below to update your application.

info

Note that this guide is just as relevant when using earlier versions of the SDK.

  1. Review breaking changes: Ensure your ACAP application does not use any functionality or permissions that are not supported in AXIS OS 12, listed in Breaking changes in AXIS OS 12.
  2. Rebuild application if needed: If your application depends on any of the listed breaking changes, update it to align with the new requirements.
  3. Reinstall the application: Install the updated application on the device. This is treated as an application upgrade, preserving state and data.
  4. Test application on AXIS OS 12: Upgrade the device to AXIS OS 12 and test that the application works as expected.

Breaking changes in AXIS OS 12​

info

This section only lists breaking changes relevant for application developers. For a full list of breaking changes, see AXIS OS 12 breaking changes.

Removed root privileges​

Applications are not allowed to run as root in AXIS OS 12, i.e., the username or group field in manifest.json must not be set to root. It's recommended to Migrate to a dynamic user, and manually specify which permissions you need through the manifest.json. See which permissions are supported to use by applications in the ACAP version 12 documentation, Adding permissions to dynamic user.

Breaking changes in the APIs​

Supported APIs might have breaking changes, such as removed deprecated methods. Consult the individual API reference pages linked to from Supported APIs to identify planned breaking changes.

Extend compatibility to AXIS OS 13​

To extend the compatibility into AXIS OS 13, follow the corresponding list in the ACAP version 12 documentation, Extend compatibility to future AXIS OS versions.

AXIS OS 13 requires the application signature to be stored on the device. This only occurs during installation on AXIS OS 12.8 or later. Before updating to AXIS OS 13, reinstall the application from the .eap file while running AXIS OS 12.8 or later.