Install Apk

Install and identify the candidate APK

Installation is the transition from build evidence to runtime evidence. It should start with the file you intend to test, not whichever app-debug.apk happens to be easiest to find. EdgeORE previously had multiple candidates with similar filenames and different source stamps. Checking identity before recording avoids attaching a wallet session to the wrong source revision.

Inspect the artifact

Calculate the APK's full SHA-256 and compare it with its manifest. If Android build tools are available, inspect package metadata and signing information with the matching tools. Record versionName, versionCode, package name and certificate fingerprint. A truncated hash is convenient for conversation but insufficient for a release checksum. Copy the full value into a checksum file associated with the actual asset.

sha256sum app/build/outputs/apk/debug/app-debug.apk
adb devices
adb install -r app/build/outputs/apk/debug/app-debug.apk
adb shell am start -n com.edgeore.app/.MainActivity

These commands assume one intended device is selected. If more than one appears, use an explicit serial with adb -s for every command. Otherwise a script can capture one device and install another. Treat a failed installation as a result to investigate; do not move directly to screenshots from an older installed package. Package-signature conflicts and insufficient storage need different remedies.

Confirm after launch

Open About and compare the stamp with the source manifest. Check the installed package's version and device Android version. Capture the launch screen with its environment label. If the app crashes, preserve the crash buffer and the action that triggered it. Clearing logs before a controlled attempt can make diagnosis easier, but do not erase the only existing crash evidence before saving it.

adb shell dumpsys package com.edgeore.app
adb shell getprop ro.build.version.release
adb logcat -d -b crash > crash.txt
adb exec-out screencap -p > cold-launch.png

An empty crash buffer is not a proof that no failure occurred; it is only the state of that buffer when read. Combine it with the observed action and relevant logs. A populated buffer might contain an unrelated app's crash, so identify the package and timestamp before attributing it to EdgeORE. Evidence collection needs interpretation, even when the command itself is simple.

Protect existing data

Do not recommend uninstalling an existing EdgeORE installation as a default upgrade path. Uninstall removes its app data and may make device-bound ciphertext impossible to decrypt. If the debug certificate changes, a replacement installation may not be allowed. A separate emulator or test profile is often safer than destroying a working installation. Document any deliberate reset in the session note because it affects restart and recovery claims.

Finish the installation gate

The acceptance criteria are that the intended artifact installed, launched and reported the expected identity. Opening all five destinations can close a separate navigation gate. Wallet authorization remains separate, and a device's ability to show a review screen is separate from signing and sending. The manifest should name exactly which of these observations occurred. That creates a reliable starting point for every later runtime test.

---

Wiki home · Qualification updates · Sources and credits