Unable to download a form with the triple underscore as a version after the blank version

Open
#2,278 2 comments 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
backend

Research direction

Start by reviewing the changes in #2251 and the linked comment, then trace how Central accepts and publishes form versions. Reproduce with a form that has no version followed by a version of ___, and check the behavior across the blank form update modes in Collect. Done means Central rejects ___ as a form version rather than allowing a version that Collect cannot download.

Written by the indexing model from the issue text.

Description

backend needs testing
Problem description

After changes in #2251 there's an edge case in not being able to download a new form version in Collect if a form doesn't contain a version and the following version is a triple underscore (check the comment in the issue. )
The issue occurs in all "Blank form update modes" in Collect.

Steps to reproduce the problem
  1. Publish a form without a form version e.g.
    fromwithoutvers.xlsx.txt
  2. Create and app user and add access to the form.
  3. In Collect scan the QR code.
  4. In Central publish the form again with the triple underscore as the form version.
  5. Try to download the form to Collect (in the manual update mode the ___ version is visible in the list of updates to download but the new version doesn't get downloaded).
Expected behavior

Not allowing the triple underscore as the form version.

Central version shown in version.txt

https://staging.getodk.cloud
versions:
3e852f511b0ac1fe10ce78765bf57888ae2237a3 (v2026.3.1-7-g3e852f5)
f8254e144016f3f4c42a87613bd0ba869a511fb8 client (v2026.3.0-29-gf8254e144)
9fbf7c60740444d532e3dede1d7cf4885510f4b2 server (v2026.3.0-13-g9fbf7c60)

Dominant language
JavaScript
Stars
233
Forks
241
Avg merge
1d 22h
Merged PRs (30d)
13

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getodk/central

All issues in getodk/central

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.