MantisBT - Issues

0009515: QR code for PoS setup

Mon, 20 Apr 2026 21:54:32 +0200

In the "Access token" page, create the possibility to generate a QR code with all necessary information for activation of the PoS application just by scanning this QR.

0011351: Input field for payment not usable

Mon, 20 Apr 2026 21:40:28 +0200

This field is only usable if no text was entered when the template was created

0010817: Customer might need possibility to let edit the full text of a summary; multi-line scenario

Mon, 20 Apr 2026 21:40:20 +0200

When you have a template with multiple lines / many chars, you don't see it all before you create the order ("Auftrag anlegen") on your phone, but you just see the first line; also you cannot reach the other lines.

0010667: need paivana reverse proxy [8d]

Mon, 20 Apr 2026 20:22:20 +0200

See DD76.

0009177: guide the merchant trought the bank account activation

Mon, 20 Apr 2026 19:51:21 +0200

after adding the bank account information in the merchant backend using the backoffice SPA the merchant needs to check if there are KYB requirements pending in the supported exchanges.

SPA must use the https://docs.taler.net/core/api-merchant.html#get--instances-$INSTANCE-private-kyc API to check pending kyc

0011044: Can't import exported database, file not selectable

Mon, 20 Apr 2026 19:46:15 +0200

Using the developer menu, I exported the database, deleted the apps storage and tried to import the database again. All files where not selectable (grayed out). I tried with renaming the exported file and with out and from different directories - no change.

0010420: Variables should not be translated on Weblate

Mon, 20 Apr 2026 19:23:36 +0200

For the Android wallet app, we find the two variables %1$s × %2$s in a string to translate on Weblate (see https://weblate.gnunet.org/translate/gnu-taler/wallet-android/en/?checksum=3f0518f73d0b67ba). The result is going to get stored in the translation files under wallet/src/main/res/values-*/strings.xml as string 167. Normally, those variables should not be internationalised as they are not meant to be translated. They stay the same in any language, right? So, please take down the tags in the code-base that indicate for translation - before some over-eager translators try to find their own interpretations of what to translate here for %1$s × %2$s and do a mess out of the app.

Only if there are alt texts or explanatations of variables like e.g. the source string description (here: × ) that need to be translated an i18n would make sense.

0011350: The lists of order statuses are inconsistent

Mon, 20 Apr 2026 11:41:46 +0200

In the app, the paid orders haven't been processed even though the payment was received.

It's not a screen refresh issue

0011257: Necessary adaptations for iOS 26 (Liquid Glass)

Sun, 19 Apr 2026 11:11:18 +0200

We are still using SDK 18 to get a pre- Liquid Glass appearance.
Starting end of April Apple demands that AppStore submissions are built with SDK 26 and support Liquid Glass.
All views need to be checked and adapted.

0011174: User must have possibility to have MFA codes resent