Tags

v2.4.4

RVML88S 2.4.4 (2404), post-release hotfix of 2.4.3

Build commit on delivery-test (merge of MR !224).
Content since v2.4.3: #110 jam recovery deferred during payment UI with
monitor safety net (MR !223, 66d8eb3f), #111 libyyyiot logger keeps the
FileWriter open and reopens a deleted file (feae915f, 6ddc82cb).

Refs #109

v2.4.3

Release 2.4.3

Tag on the head of delivery-test (c3310f1c, MR "hotfix/ticket-94-followup-
lowdisk-absolute-4g-6g-only"), set before the build. Moved from the freeze
commit 178e31f4 (MR !161): from there to here delivery-test took 40 hotfix
merges (#92 #93 #94 #97 #98 #99 #100 #101 #102 #103), and no APK of 2.4.3
was ever installed on a field machine from 178e31f4.

Build from THIS commit with a clean working tree. The build stamp in
the field log has to read

  version=2.4.3(2403) commit=c3310f1c...  branch=delivery-test  env=pro

without '+dirty'. If the shipped APK names another commit or a modified
tree, this tag is deleted and set again on the commit that was really
built - that was necessary for 2.3.4 (2d5caf5) and 2.4.1 (585afc7a).

v2.4.2

Release 2.4.2

Tag on the freeze commit of delivery-test (MR !152), set before the
field rollout so the promotion to production carries a matching tag.

The release APK must be built from THIS commit with a clean working
tree. The build stamp in the field log has to read

  version=2.4.2(2402) commit=6c040576...  branch=delivery-test  env=pro

without '+dirty'. If the shipped APK names another commit or a modified
tree, this tag is deleted and set again on the commit that was really
built - that happened with 2.3.4 (2d5caf5) and 2.4.1 (585afc7a).

Content: 37 commits, 33 tickets since 2.4.1. The four EZ-Link field
cases are fixed (#47 TA polling, #69 duplicate sale after success, #70
poll ownership across orders, #79 late success on a foreign REJECTED
row), plus order snapshots across a restart (#82, #66), UPC-A padding
(#86), DM garbled check (#74), scanner ghost fault (#73), single
scanner from SGRVM0426 (#84), backend sticker review (#81, #25), remote
drive parameters (#72, #80, #83) and the low-disk/DB/camera hardening
(#64).

Not in this release: the metal detector baseline reset (report of
2026-09-30) and #78, which was reverted by #82.

v2.4.1

Release 2.4.1

Tag moved on 2026-10-13 from the delivery-test freeze commit 6f525f25 to
the commit the shipped APK was really built from, taken from the field
logs of SGRVM0160, SGRVM0099 and SGRVM0162 (2026-10-12):

  [构建标识] version=2.4.1(2401) commit=585afc7a2533+dirty branch=development env=pro

Two facts this tag has to carry:

- gitDirty: the APK was built from a modified working tree, so it is not
  byte-reproducible from this commit. build.gradle already reads 2401 /
  "2.4.1" / 'pro' here, so the version is not the modification.
- The build predates the merge of #57 (remote door commands, 66ef1c3c).
  The field binary is therefore 2.4.1 minus #57: MainBasicEventHandler,
  Constants, EventType and WebSocketHelper lack those 22 lines. The
  commit tagged before (6f525f25) contains them.

Content: 2.4.0 and 2.4.1 together, because 2.4.0 was withdrawn and never
reached production - approved payment screens (#39/#45), barcode A/B
switch (#41), receipt underline (#48), low-disk 20 % (#49), STS UTC fix
(#51), re-upload amount (#56), retry de-duplication (#54), DM-code reject
photo (#55), bitmap recycling (#53), door throttle (#52).

v2.3.4

Release 2.3.4

The APK that went to the machines was built from this commit on branch
hotfix/ticket-42-metal-npe-baseline. Field log of SGRVM0160, 2026-09-28:

  [构建标识] version=2.3.4(2304) commit=2d5caf591ffb+dirty
             branch=hotfix/ticket-42-metal-npe-baseline env=pro

Two facts this tag has to carry:

- gitDirty: build.gradle was raised to versionCode 2304 / versionName
  "2.3.4" in the working tree without a commit. The commit itself still
  reads 2303 / "2.3.3"; commit 68d4540 does that bump officially. The
  APK is therefore not byte-reproducible from this commit.
- The delivered build differs from the release merge on production
  (6c5a249b) in UserFinishFragment: the field APK uses the old layout
  fragment_user_finish2, production uses fragment_user_finish.

Content: metal hotfix #42 on top of 2.3.3 — null guards in the metal
frequency callback and lasMetalBoardHeatTime refreshed after the idle
baseline reset and the metal self-check.

v2.3.3

Release 2.3.3

versionCode 2303, versionName 2.3.3, environment pro. Frozen on delivery-test. The
release APK is built from this commit and shipped unchanged. Previous version in
the field: 2.3.2.

v2.3.2

Release 2.3.2

versionCode 2302, versionName 2.3.2, environment pro. Frozen on delivery-test
(merge request !51). The release APK is built from this commit and shipped
unchanged.

Contents: payment settling hardened (#16), no home-screen flash on auto restore
(#23), order and hour logs kept for upload (#24), WebSocket remote tare (#22).

v2.3.1

Release 2.3.1 (hotfix)

versionCode 2301, versionName 2.3.1 with the build timestamp of the shipped build
(2.3.1.yyyyMMdd-HHmm). This is the commit the shipped APK was built from; the
build was made from the hotfix branch dev/ticket-20-release-disable-selected-features.

Contents: old UI and receipt without QR code (#20), fishing-line check from right
edge 1500 (#21), taps inside the throttle window dropped (#20).

v2.3.0

Release 2.3.0

versionCode 2300, versionName 2.3.0. This is the commit the shipped APK was
built from: RVML88S-pro-2.3.0.apk, sha256
1a6dbeec54c31ac2371baef41167a602a598e39a08175d6c902acdfc72f0d75d.

The build goes onto machines in the field for the staged rollout, starting with
the pilot machines. The tag is created at build time, not after the rollout is
finished: from the moment the APK is installed on a customer machine, the version
exists and must be identifiable from a field log.

2.1.91

新UI前最后一版

2.1.90

没集合plc夹瓶前的分支，加了老外新ezlink、修复了paylah金额问题

2.2.0

未合并夹瓶恢复前的代码，在89版本基础上修改，修改1500ml以上的容器在第四光眼停，并修改没录入的瓶子的检查，并合并了已知的修复bug后的代码，

2.1.89

2.1.87

2.1.86

2.1.50

2.1.49

2.1.38

2.1.37

doc-synced

documented through v2.1.36 second changeDeposit merge