Prevent capture failures from corrupting the BlueStacks instance
All checks were successful
build / build-test (push) Successful in 1m52s
All checks were successful
build / build-test (push) Successful in 1m52s
This commit is contained in:
parent
75589d2383
commit
077b4c9067
2 changed files with 61 additions and 4 deletions
|
|
@ -20,6 +20,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|||
- Dedup check in `update_best_car` now considers `normalized_config` to prevent same car+config duplicates
|
||||
|
||||
### Changed
|
||||
- `capture run` aborts with a clear error when the game package is missing on the device, before any proxy/CA state is set up — a missing package was the launch failure that previously triggered the proxy leak
|
||||
- BlueStacks shutdown is now graceful: `adb reboot -p` first (clean ext4 unmount), with `taskkill /F` only as a 30 s fallback — force-killing the emulator corrupted `Data.vhdx` and BlueStacks' boot repair then discarded `packages.xml` and `accounts.db` as corrupt files, which took the installed game and the Google account with it (2026-10-02)
|
||||
- `CarCounts.by_rid` key changed from `String` to `(String, String)` for per-config tracking
|
||||
- `CarCounts.guid_to_rid` changed from `HashMap<String, String>` to `HashMap<String, HashSet<(String, String)>>`
|
||||
- `compute_car_counts()` now accepts `owned_configs` parameter
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue