Upgrade, support, and integrity

Upgrade safely#

1. Close Avellio and InDesign.
2. Back up the existing release package if your organization requires rollback.
3. Replace the Loader and Engine together with the matched new release.
4. Do not leave a legacy Engine beside a new Loader.
5. Restart InDesign, activate if requested, and run Health.
6. Pilot the release on a representative backed-up document before broad deployment.

Report a reproducible problem#

Send support@avellio.app:

• Avellio version and release;
• InDesign version and operating system;
• active profile, locale, and scope;
• the exact sequence that reproduces the issue;
• expected and actual behavior;
• avellio_crash.log when relevant;
• a sanitized sample only when the document owner authorizes it.

Never send a full license key in an ordinary support message. Mask it and provide only the minimum identifier needed to locate the purchase.

Verify package integrity#

Use a checksum or signature only when it is supplied through an official Avellio distribution channel for the exact release. Do not rely on checksum values copied from an older package. If the release does not include a published verification artifact, reacquire it from the original authorized source rather than inventing or reusing a legacy value.