Skip to main content
Version: ACAP version 12

FAQ

Questions

General​

1. Can frequent writes to internal storage affect the device lifespan?"

Yes. Axis devices use flash memory for persistent storage, which has a finite number of write and erase cycles per memory cell. Each write or erase operation contributes incrementally to wear on the underlying storage media.

ACAP applications that frequently write data to internal flash storage, particularly in high-frequency or continuous write patterns, can significantly increase the number of write/erase cycles over time. If such usage is not carefully controlled, it may accelerate flash wear beyond what is expected under normal operating conditions.

Excessive or unnecessary write operations, such as continuously storing data from an ACAP application, can accelerate memory wear over time and progressively reduce the memory's integrity. This may shorten the expected operational lifespan of the device. Once the flash memory reaches its designed endurance limits, reliable storage operation cannot be guaranteed, potentially impacting the device's ability to store configuration data, logs, or application state.

To ensure long-term reliability and predictable device behavior, ACAP applications should:

  • Minimize write frequency to internal flash storage.
  • Avoid using flash memory for high-rate or continuously updated data.
  • Prefer volatile memory, external storage, or supported mechanisms designed for frequent data updates.

Developers should understand their application requirements and evaluate which storage solution best fits their specific use case.

Efficient data handling strategies, such as buffering, batching, or using alternative storage options when appropriate, help maintain optimal device performance and longevity.

By following these guidelines, application developers help preserve storage endurance and ensure that Axis devices continue to operate within their intended design parameters throughout their lifecycle.

2. How should TIP partners sign their ACAP applications?

For information on how TIP partners should sign ACAP applications, see the ACAP application signing page. If you're not a TIP partner, a signing tool will be available starting with AXIS OS 13.

3. Where can developers find ACAP application examples?

Developers can find ACAP application examples in ACAP application examples.

Manifest schema​

1. Where can developers find the manifest schema reference and upgrade guidance?

Developers can find the manifest schema reference and upgrade guidance in the manifest schema page. This section provides an overview of the manifest schema versions and provides specific guidance for migrating and upgrading the manifest.

2. How can developers migrate their ACAP application from package.conf to manifest.json?

For guidance on how to migrate your ACAP application from package.conf to manifest.json, see Migrating from package.conf to manifest.json.

3. How can developers use a newer manifest schema in an older SDK?

For guidance on how to use a newer manifest schema in an older SDK, see the Use newer manifest schema in old SDK page.

Compatibility​

1. How do developers make an application compatible with AXIS OS 11, 12, and 13?

Developers can make applications compatible with newer AXIS OS major versions by following the Extend compatibility to future AXIS OS major versions guide available for ACAP Native SDK version 4 and version 12. These guides describe the required updates and breaking changes introduced when migrating applications from AXIS OS 11 to 12 and from AXIS OS 12 to 13, helping ensure that applications continue to install and run correctly after device upgrades.

2. Where can developers find the API reference and the API compatibility guide?

Detailed technical specifications for the supported APIs are available on the Supported APIs page, while AXIS OS support details are available in the API compatibility guide.

Not finding what you are looking for? Head over to GitHub Discussions and search for the answer there.