How can the integrity of an Appcelerator mobile app backup be verified before restoring it to a device or emulator while preserving the original app state?

To check that an Appcelerator mobile app backup is intact and safe to restore, follow these general steps. The process is designed to leave the original backup file unchanged and to work for both iOS and Android targets.

1. Create a working copy – Copy the backup archive (e.g., myapp.backup.zip) to a temporary directory. This ensures the original file remains untouched.
2. Extract the manifest without modifying the archive – Use a read‑only extraction tool such as unzip -l (list) or 7z l to view the contents, then extract only the manifest file (often named tiapp.xml or manifest.json) with unzip -j myapp.backup.zip manifest.json -d ./tmp. The -j flag strips paths, preventing accidental overwrites.
3. Inspect the manifest – Open the extracted manifest in a text editor or XML/JSON viewer and verify that it contains expected fields such as appid, version, platforms, and a list of bundled resources. Look for any obvious corruption (truncated syntax, missing tags).
4. Compute a checksum of the whole backup – Run a hash algorithm (e.g., SHA‑256) on the original backup file: sha256sum myapp.backup.zip. Record the output.
5. Compare with the manifest‑recorded checksum – Many Appcelerator backup manifests include a checksum or hash attribute. If present, compare the computed value with the manifest value. A mismatch indicates archive corruption.
6. Launch a test instance in an emulator –
   • For Android: use an Android Virtual Device (AVD) that matches the target API level and screen density noted in the manifest.
   • For iOS: use the Xcode Simulator with a device model and iOS version that aligns with the manifest’s deploy-type settings.
   Install the app from the backup (e.g., via adb install -r for Android or xcrun simctl install for iOS) without altering the backup file.
7. Run a basic sanity check – Start the app and verify that it launches to its main screen, that no immediate crash logs appear, and that core functionality (e.g., a known API call) responds as expected.
8. Rollback if needed – If any step fails, discard the temporary working copy and retain the original backup unchanged. No further action is required on the source backup.

By keeping the original archive untouched, using a read‑only manifest extraction, verifying checksums, and testing in a matched emulator, you can gain confidence that the backup is valid before performing a real restoration.