Local Testing vs Direct Upload: Safe Rollback After Schema Change

The objective is to ensure that a schema change in an internal mobile app’s test configuration can be rolled back without re‑uploading the entire .ipa or .apk binary.

While Local Testing provides a secure tunnel that isolates the host environment, it raises uncertainty whether historic build artifacts remain accessible for rollback. Direct upload offers faster iteration but requires a fresh upload for each binary modification, complicating rollback after schema updates.

Does Local Testing retain historic build artifacts for schema change rollback? Can direct upload be made version‑aware to enable safe rollback? Which approach minimizes re‑upload frequency while guaranteeing rollback safety?