Major releases will be patched as bugs are resolved. These are called “patch” or “point” releases.
Patch releases never include new functionality or major changes.
Patch releases are always explicitly bug fixes. NOT a new functionality.
Reinstalling a major release will automatically install the latest patch release.
Patch releases frequently contain preemptive bug fixes for issues that were found in newer releases.
Note: the decision to back-port to older versions via patch releases is made by GENERAL BYTES based on the severity of the issue (and other factors).
We strongly encourage operators to routinely upgrade to the newest patch release (weekly), and to upgrade to the latest full release at least every two months. This is for security purposes. |
Upgrading your server or terminal to the same installed version results in the installation of the latest patch release for that particular version. For example: Note: the version must not contain a dot (or the patch level after the dot)! |
Select your release below:
CF-434 BNR BATM2 - Application Crashes |
BATM-3581 - Server - send sentry crash log first and then save to file system |
BATM-3546 - Face capture sometimes fails with selfie camera on BATM3/4 |
BATM-3524 - Bitgo call to create an ETH wallet failes |
BATM-3474 - When cashbox is out before starting the app, error screen is not shown. |
BATM-3613 - BNR with router - Can't find BNR if the whole ATM including router is powercycled |
BPUB-1842 - Do not change awaiting registration state when user try to register again |
CF-424 - BNR bug : Stacker full does not clear after acceptor cashbox is full then emptied |
CF-405 - Bug - ticketless sell flow on Terminal asks twice for phone number |
CF-403 - Ukraine embassy addresses should be excluded from limits attached to the crypto address |
BATM-3443 - Terminal should not show blacklisted address note to customer. |
BATM-3409 - Terminal occasionally was creating a new keystore and thus unpair was needed. Terminal showed message certificate mismatch. |
BPUB-1822 - It wasn’t possible to use verification(Onfido/Veriff) service together with identity custom fields. |
BATM-3338 - The notification corresponding acceptance banknotes problem contains invalid amount attempt of inserting the banknotes. |
BATM-3329 - Fixed Approval link ends with Houston error in new version. |
BATM-3266 - Wrong translation of the new button in german language |
BATM-3392 - Limit buttons on terminal screen are not displayed and terminal configuration sent from server is not parsed when location on server has timezone that is not supported by Android OS. |
LC-136 - Back-ported fix Crypto low transaction webhook notification description not accurate. |
BATM-3338 - The notification corresponding acceptance banknotes problem contains invalid amount attempt of inserting the banknotes. |
BATM-3392 - Limit buttons on terminal screen are not displayed and terminal configuration sent from server is not parsed when location on server has timezone that is not supported by Android OS. |
LC-136 - Back-ported fix Crypto low transaction webhook notification description not accurate. |
BATM-3338 - The notification corresponding acceptance banknotes problem contains invalid amount attempt of inserting the banknotes. |
BATM-3241 - Kraken+queues: No operations allowed after connection closed BATM-3056 - BTC Transaction Using Queue Failed to send but panel shows as complete |
BATM-3108 - Update Morphis extension to be compatible with the current batm version BATM-3099 - SMS sell ticket - escape QR url & use correct phone number from unregistered tier |