Skip to content

Releases

v1.6.1

Choose a tag to compare

@SK360 SK360 released this 21 Nov 14:32

Fixed

  • No more screen full of "MuPDF error: format error: cannot find object in xref" lines while Check approvals
    reads Form 1s still in process. They were harmless messages about the PDFs eForms sends, printed while each one was
    cut down to its first page. They're switched off now, the page is copied in a way that works on those PDFs, and if
    a PDF can't be cut down it's kept whole.

Tested

  • Check approvals' in-process search (1.6.0) worked live: a user's forms filed by hand were found and recorded as
    filed. The fix above is tested on a PDF with the same kind of broken references.

v1.6.0

Choose a tag to compare

@SK360 SK360 released this 21 Nov 11:58

Form 1s filed by hand show up before they're approved.

Fixed

  • Check approvals now finds Form 1s still in process, not only approved ones. Before, a suppressor you filed
    yourself on eForms (outside this helper) wasn't seen until ATF approved it. Check approvals now also looks at
    eForms' "Submitted/In Process" list. Any suppressor there that your records don't have as filed is shown and can be
    recorded as filed, with the filed date and eForm ID taken from the form (eForms doesn't list the application
    number). It then waits for approval like any other filing.
  • No more filing a suppressor twice by accident. If a serial is already in process on eForms but queued in the
    helper (say you added it to have it in your inventory), Check approvals warns that filing it would file it twice
    and offers to record it as filed. A pending row that eForms shows in process gets a reminder to resolve it as filed,
    and a serial on more than one in-process form gets a warning.
  • Only the first page of each in-process form is kept (out/in-process/), and each form is opened only once.
    The page is removed once the form leaves the list. Forms this helper filed itself aren't opened again.

Inventory server

  • Server API 4 (new operation record_in_process). If your inventory lives on the server, update the server too.
    Until you do, the helper says so instead of recording these forms.

Tested

  • Tested against a fake eForms dashboard and the real server in a temp folder. Not yet run against live eForms: it
    uses the same search and View PDF steps as the CLEO-copy fetch, which has worked live on submitted forms.

v1.5.2

Choose a tag to compare

@SK360 SK360 released this 21 Nov 00:13

Race/ethnicity matches eForms' list.

Fixed

  • "American Indian or Alaskan Native" is now spelled the way eForms spells it. Thanks to @ruinz89 for finding and
    fixing it (#4). Before, filing stopped at the race step for anyone who had picked it. Settings saved with the old spelling
    are corrected automatically; nothing to redo.

New

  • All of eForms' race/ethnicity options, and more than one at a time. Settings now lists the eight options eForms
    shows (Hispanic or Latino, Middle Eastern/North African and Unknown were missing) as a checklist, the same for
    every responsible person. Each ticked one is ticked on eForms. Settings with one race are unchanged.

Tested

  • With a fake eForms popup. The option names come from eForms' own list (seen 2026-11-20); not yet filed live with
    more than one race or with the new options.

v1.5.1

Choose a tag to compare

@SK360 SK360 released this 19 Nov 14:50

Disapproved forms can be filed again.

New

  • Check approvals finds disapproved and returned Form 1s. While any suppressor is filed and waiting, it also
    searches eForms for Form 1s that are disapproved or returned without action, saves their PDFs to
    out/not-approved/, and marks those suppressors disapproved (the home screen says how many). Returned for
    correction is reported, not marked. Only a serial's current filing counts: an old disapproved form of a serial
    that was filed again since is left alone.
  • Advanced > Re-file lists disapproved suppressors first, with a reminder to fix what ATF disapproved them for
    (eForms has the letter) before filing again. Each re-filing is a new application. Until now a disapproved form
    stayed "filed", and deleting rows from the Excel export or the filing log didn't change that.

Tested

  • With a fake eForms dashboard, and against a real inventory server. Not yet seen live: a real disapproved or
    returned form in eForms (its PDF is expected to have the same item 4 as an approved one).

v1.5.0

Choose a tag to compare

@SK360 SK360 released this 17 Nov 18:45

Backups, and installing no longer needs Python.

New

  • Backups. On each day your records change, a small ZIP of them (inventory, settings, filing log) is kept in
    out/backups/, the last 60 days. For a copy that survives the computer, Settings > Backups takes a folder on a
    USB drive or in a cloud folder: everything is copied there (records, settings, templates, approval PDFs, CLEO
    copies, your fingerprint/photo/trust files), then only what's new or changed, whenever the menu is open and the
    folder is there. The home screen warns if it hasn't been reachable for a week. Check my setup shows it too.
    The server pairing key is never copied. ./atf backup does it from the command line.

Changed

  • New installs don't need Python installed first. The installer downloads a pinned, checksum-verified copy of
    uv and uses it to put a private Python 3.13 in the folder's .uv folder (the .venv is made from it). Nothing is
    installed system-wide.
  • If uv can't be downloaded (offline, blocked, an unsupported computer), the installer says why and uses a Python
    3.9 to 3.14 already on the computer, as before. A checksum that doesn't match stops the install instead.
  • Existing installs: nothing to do. Re-running the installer keeps a .venv that already works, and updates from
    the menu behave as before (they never run the installer, and never touch .uv).
  • Delete .venv and .uv together to reinstall from scratch.
  • Tried live: a fresh install on a Windows PC (it got its own Python 3.13 although 3.11 was installed). Linux and the
    fallback only by the automated tests, which now install with no Python on Windows, Linux and macOS.
  • Backups: only by the automated tests so far.

v1.4.2

Choose a tag to compare

@SK360 SK360 released this 17 Nov 03:43

Find your forms on eForms by serial.

Updating: from the menu (⬆ Update to version 1.4.2). No new packages. The inventory server doesn't need
updating.

New

  • The serial goes in each Form 1's Internal Control Number. That box is the filer's own reference on eForms; with
    the serial in it, the eForms home page's Internal Control Number search finds a form by serial, and its results
    list shows which suppressor each form is (it only showed eForm IDs). It's read back before going on, like
    everything else filled. Only forms filed from now on have it. Don't want it (you number your forms your own way)?
    Settings > Internal control number on eForms > Leave it empty.
  • The CLEO's copies still never show the serial: eForms doesn't print the internal control number on the CLEO copy,
    and if it ever did, the saved copy would have it blanked out (and say so).

Tested

  • Live: a real trust filing (the number read back, shown in the eForms dashboard's column, and absent from the
    Form 1 CLEO copy). The Form 1 CLEO copy saved at the end of a real batch also worked live for the first time.

v1.4.1

Choose a tag to compare

@SK360 SK360 released this 17 Nov 02:14

A fix for filing as an individual with a UPIN.

Updating: from the menu (⬆ Update to version 1.4.1). No new packages. The inventory server doesn't need
updating.

Fixed

  • Filing as an individual stopped at the UPIN (item 13) with "'#14answer' is not a valid selector" whenever a
    UPIN was set in Settings. The step now finds the field.
  • "N/A" at the UPIN question means no UPIN. N/A, NA, none and the like used to be saved as a UPIN and would have
    been typed into ATF's UPIN box; now the box is left empty, as with no answer. Settings saved before this are read
    the same way, so nothing needs changing.

Tested

  • In tests (the UPIN step, N/A and other blanks, and a check that no portal step uses that kind of selector again).
    Not yet on the live portal: a practice run as an individual with a real UPIN.

v1.4.0

Choose a tag to compare

@SK360 SK360 released this 15 Nov 20:48

A clearer message for a CLEO address the portal doesn't know, a safer updater, and a status screen, one-file backup
and update command for the inventory server.

Updating: from the menu (⬆ Update to version 1.4.0), the first update done that way. No new packages. The
inventory server is optional to update (the helper works with the one you have); its new Server screen, backup and
update command need it. This once by hand: cd /opt/atf-inventory && git pull && systemctl restart atf-inventory
(Docker: rebuild the image, see DOCKER.md). From then on: atf-server update.

Fixed

  • A CLEO city, county or state the portal doesn't offer stopped filing after 30 seconds with only "Timeout". The
    portal fills those dropdowns from the ZIP, so a misspelled county (or a city the ZIP doesn't cover) can't be
    picked. Now it stops within a few seconds, names the choices the page offers and says to check that setting and
    the ZIP in Settings > All settings. The county is the one CLEO question the 5320.23 template can't fill in,
    so it's the one to check first. Every other dropdown also says what it offers instead of timing out.
  • Updates: when a new version needs new Python packages, they are installed before any program file is
    replaced. A failed install used to leave the new program with the old packages; now the folder stays on the old
    version and the update is offered again.
  • Inventory server: uploads accept only proper checksums for PDF names (a paired device could otherwise name a
    file outside the server's upload folder).

Inventory server

  • Server screen on the server's page (footer: Server) and in Check my setup: its version and whether a newer
    one is out, the last backups, disk space, when its certificate runs out, and anything that needs attention (no
    backup for two days, a nearly full disk, a certificate about to expire, approval PDFs missing). The server now
    reports the same version number as the helper.
  • One backup file with everything: the database and every approval PDF in one ZIP, from the Server screen or
    from the helper (Settings > Where your inventory lives > Save a backup of the server on this computer, keeps
    the newest 5). atf-server restore <file> takes it back, checking every PDF first. No certificates or keys in it.
  • atf-server update (plain installs, as root): backs up, installs packages, moves to the newest release and
    restarts the service. --check only says whether one is out. There's no update button on the page on purpose:
    the server can't change its own program, and neither can a paired phone.

Tested

  • Live: a real trust filing with the new dropdown picking (CLEO city, county and state included). The new "isn't one
    of the choices" message only in tests so far.
  • The server's status screen, backup file and restore in tests. Not yet live: atf-server update on a real server
    and the first update from the menu to a real release on Windows (macOS updates were tried with 1.3.0).

v1.3.0

Choose a tag to compare

@SK360 SK360 released this 09 Nov 04:09

Updates from the menu.

Updating: this once still by hand (git pull, or the new ZIP with your data, forms and out folders copied
in). No new packages. The inventory server doesn't need updating.

  • The helper tells you when a new version is out: once a day it asks GitHub for the newest release (nothing
    personal is sent; offline, nothing happens) and the home screen says so.
  • ⬆ Update to version … in the menu shows what's new and, on your yes, updates the folder: with Git it moves to
    the released version (never unreleased changes); without Git it downloads the release and replaces the program
    files, keeping the old ones in .update-backup. Your data, forms and out folders are never touched. New
    Python packages and Chromium are installed when the new version needs them, then the menu starts again (Windows:
    start .\atf.cmd again). Not offered while a row is pending or a filing result waits for your inventory server.
  • Settings > New versions turns the daily check off; Advanced > Check for a new version now and
    ./atf update (--check only says) work either way.
  • Tested on fake releases (a ZIP install, a git checkout, failures that put every file back); not yet tried on a real
    release, since the first one it can update to is the one after this.

v1.2.4

Choose a tag to compare

@SK360 SK360 released this 06 Nov 19:00

CLEO notification packets.

Updating: git pull, then run the installer again (./install.sh, Windows .\install.cmd). No new packages, and
your settings, inventory and files carry over unchanged. The inventory server doesn't need updating. For the 5320.23
CLEO copies (trusts), download the generator's CLEO copy of your template and add it in Settings.

  • One PDF to mail to your CLEO after each batch: a cover page (your CLEO's address for a #10 window envelope, how
    many applications, the date filed), then each application's Form 1 copy and 5320.23 copy. Neither shows the serial:
    ATF leaves it off the CLEO's copies.
  • The Form 1 copy comes from eForms: every submitted form's PDF ends with "CLEO Copy" pages. After a batch the
    helper opens the forms it just filed (read-only) and keeps those pages.
  • The 5320.23 copy is optional (trusts): add the generator's CLEO copy in Settings > CLEO copies of the
    5320.23
    ; it's stamped like the ATF copy (caliber, date, current CLEO official). Each other responsible person can
    add theirs and gets their own packet for their CLEO.
  • Advanced > Make CLEO packets for forms filed earlier, while they're still in process. It ticks every filed form
    that isn't in a packet yet, so several batches can go out as one: turn off Settings > CLEO packet after each
    batch
    (the copies are still saved after each batch).
  • Check my setup says whether each 5320.23 CLEO copy is set and stamps correctly. A CLEO copy picked as the ATF
    template (or the other way round) is now refused.

Tested live: Advanced > Make CLEO packets for 15 forms in process (a trust; Form 1 copies fetched from eForms,
5320.23 CLEO copies stamped, one packet). Not yet tried live: the automatic fetch at the end of a real batch, and an
individual's submitted form.