Bug fix v0.49.0
v0.49.0 — Fixes and improvements
A pooled round of fixes to the one text you read at the worst moment — the error message. Fields are named the way you name them rather than by a database column, several messages stopped being code, and an RR invoice now asks for the farmer's details the same way everywhere.
August 16, 2026 Platform
- A form error names the field the way you do. Close to ninety fields had no name of their own, so the message fell back to the technical one — “Pole vat exempt basis type jest wymagane”. Every field you can fill in wrongly now has a proper name.
- Messages that were code. The notice about a failed invoice issue or deletion, the hint in the permission matrix and five headers of the purchase-register sheet showed an internal identifier instead of a sentence. Four notices had no text at all, in any language.
- Company lookup in the registry. With an unrecognised identifier kind, the message showed a code assembled from what you had typed instead of the field's name.
- The sign-in screen. A refused sign-in could reach the form as a technical identifier and a number rather than a sentence.
- The tax-office hint finally appears. The request to pick your tax office before arming automatic filing had never once been shown: the message was attached to a different rule than the one that actually checks that field.
- An RR invoice asks for the farmer's details the same way everywhere. First name, surname and identity document were required on only one issuing path, although art. 116 sec. 2 of the VAT Act requires them always — they now apply on every path, the AI assistant included.
- The AI assistant speaks plainly and no longer drops a mark. Errors returned to the assistant named fields technically, and the “załącznik nr 15” mark disappeared when the assistant edited an invoice, even though issuing one stored it correctly.