r-zakarya
afc6119cf8
Two defects, one feature made useless. The cache did seal under the code, but nothing on the home screen asked for it: opening without one failed, the failure was read as corruption, and the device offered to download a vault it held perfectly well. And the next refresh rewrote the cache in the old shape, so the code was undone seconds after being set, silently. The code now lives on the home screen, not among the server settings: it seals this device's cache, while the other three fields describe the shared remote. Always visible - hiding it when none is set would remove the only place to set one - the hint saying which case you are in. An absent code is no longer attempted, a wrong one is no longer corruption, and a sealed cache is never rewritten without its code. The two panels each got an arrow, and only one opens at a time. Measured end to end on the device: version byte 1, code typed, open, byte 4; cold start says "Unlock code required" and open without the code leaves the byte at 4; correct code opens the vault, and the refresh that follows leaves it at 4.
