MerginMaps / MerginMaps/mobile

Error banners are not localized for non-English device languages

Open
#4,136 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug translation
Dominant language
C++
Stars
388
Forks
87
Avg merge
2d 7h
Merged PRs (30d)
20

Description

Description

When device/system language is set to a non-English language (e.g. Slovak), the error banner shown after attempting to log in with an invalid credentials is displayed in English, e.g. "Invalid username or password". This suggests the string is hard-coded or missing from the translation resources.

Environment
PROD

Application (+ app version, build, operating system)

  • Actual Android app version: 2025.6.0
  • Actual iOS app version: 2025.6.0
  • iOS 18.5

Steps to reproduce

  1. Set device system language to Slovak (or any supported non-English language).
  2. Launch Mergin Maps mobile app (ensure logged out).
  3. Navigate to the Login screen.
  4. Enter a valid existing username.
  5. Enter an incorrect password.
  6. Tap Sign in.
  7. Observe the error banner text.
  8. Enter valid email and leave the password empty -> error banner is in ENG

Actual results
Error banner text is shown in English despite device language being non-English.

Expected results
The banner should display the translated string for the current device/app language. If the translation key is missing, a fallback/missing key log should appear and the key should be added to localization files. English should not appear silently when a translation is expected to exist.

Screenshots or logs

Conclusion
Created by GitHub Copilot and supervised by a human test analyst.

Contributor guide

Open the 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.

Research direction

No files, tests, or entry points are named; start by locating the login error-banner handling and the localization resources used by the Android and iOS apps. Reproduce the invalid-password and empty-password cases with a supported non-English device language, then verify that both banners use translated strings rather than silently displaying English.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, ios
Domain
localization, mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.