# fix: read the live Network/Cookies jar, and don't let a double-click abort an import · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/9ca0e4afdb5cca0e8fc7baaeaa1af6c1f602dbe6)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 9ca0e4afdb5cca0e8fc7baaeaa1af6c1f602dbe6

Requested commit: 9ca0e4afdb5cca0e8fc7baaeaa1af6c1f602dbe6

Commit: 9ca0e4afdb5cca0e8fc7baaeaa1af6c1f602dbe6

Tree: 48e8d1cbb078c9519635bc95748eaa4ce4314dc5

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix: read the live Network/Cookies jar, and don't let a double-click abort an import

Two review findings. Chromium 96 moved the cookie database to
`Network/Cookies`, but the reader only ever looked at `{profile}/Cookies` —
so an install carrying a leftover root jar imported a stale or empty
database while the real sessions lived under `Network/`, and a fresh install
with only the `Network/` jar read as not installed and was hidden. Discovery,
counts, the installed check and the importer now resolve the first candidate
that is a regular file, most-current first.

And a second Import click before React left the configure screen started a
second run; the parent refused it, and the wizard applied that refusal as a
read failure — dropping out of the importing step mid-write and showing a
false error over a successful import. A synchronous in-flight ref now makes
the second click a no-op.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

```

## Parents

- [014e15989c2b6961164b4d872533a76b2cd92e7f](https://git.cafe/pingdotgg/t3code/commit/014e15989c2b6961164b4d872533a76b2cd92e7f?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/9ca0e4afdb5cca0e8fc7baaeaa1af6c1f602dbe6?format=markdown)